Modern applications require dynamic infrastructures. If operations teams aren’t managing Day 2 operations in a repeatable way, they are probably introducing variation to the software development and delivery process. What if there was a more manageable way to allow individual systems to continue to refine, add, and change their behavior after they were provisioned?

What is “Orchestration as Code?”

While Orchestration sets up a trigger to run on its own without human intervention, Orchestration as Code adds modular, reusable and versioned components.  This enables you to define triggers, timers, and event responses in a systematic and collaborative way that is easily reused across your organization and sites. Ultimately, orchestration makes it easier to understand the state of the system and its components while the automation makes decisions based on inputs and events – with no human interaction.

Sometimes admins try to anticipate what information a pipeline needs, and hard code those inputs into tools that aren’t built to deliver complete Orchestration as Code. Instead of being able to continuously manage their operations pipelines, they end up with brittle scripts that can’t handle changes. Hard coding usually impacts the ability for pipelines to deliver Continuous Delivery.