When working with orchestration in automated systems, how do you find the right balance between things that are event driven and things that are workflow driven, or more linear?
We go through some of the history of where we went from linear orchestration (Ansible) to timed orchestration (Chef or Puppet). We also discussed SaltStack, which had an event driven system into it, but didn’t gain the traction that we might have expected as we look at the amount of orchestration systems that are now coming to light.
In this conversation, we address the balance between when you orchestrate and when you want to do workflow and linear transactions, and how to find that sweet spot.
One of the things that we’ve determined is, there aren’t a lot of tools that hit that sweet spot. And I think if you listen carefully, you’ll see why.
Transcript: otter.ai/u/ynb8KndfUhKsTvQG6965ktepv-Y
Image: www.pexels.com/photo/a-choir-sin…a-flower-7569413/
Rob’s Hot Take:
In the August 16th orchestration discussion on Cloud 2030, Rob Hirschfeld emphasizes the importance of striking a balance between orchestrated systems and event-driven operations. He highlights the challenge of comprehending the consequences of operations in complex systems and emphasizes the need for a blend of orchestration and event-driven approaches while ensuring that automation workflows remain understandable to users. Hirschfeld encourages listeners to explore the full episode at the2030.cloud, where the discussion delves into various tools, techniques, and considerations for building effective systems.