A workflow is a logical flow of events, data, and actions to achieve a particular output, whether it's an insight, a compliance check, a report, remediation, or some form of action. The goal with workflows is to componentize the cloud management process. As your infrastructure grows in complexity, the management becomes harder. You require increased manpower, additional planning, scaling existing services to match rising demands, and more.
You are advised to approach these demands by breaking them down into smaller components to tackle. However, it doesn’t stop there. When it comes to cloud management of a large infrastructure, your tools and scripts must be scalable and able to respond to any form of constraints. So, after you’ve componentized the problem, it’s only natural your solution is derived from the same. This is where workflows assist your cloud management greatly.
The workflows are created using simple nodes. Each node has a specific function and serves to contextualize the ones coming after it. For example, the trigger node will ascertain how and when the workflow will be launched. The resource node determines which resource data will be fetched for modification. The resource node then acts as the base for the filter node and the custom node that comes after it. Adding up these nodes and their simple functions, you get to create complex workflows.
Hence, workflows are able to act as the building blocks of your cloud infrastructure and you’re given the power to restructure it the way it fits. It’s not any particular function that matters here, it’s the power of the underlying componentized platform, that is practically giving you complete control of how you want to handle your infrastructure. The idea isn’t to eliminate code in its entirety but to use its best functionality, which is its ability to provide flexibility and customization, to give you the best of both worlds.