Cross-Functional Architecture And Tools For Cloud-Based Operating Models
Now that we have discussed the main architectural aspects, the following table will show how each of the defined use cases is addressed by specific aspects of the Agile Cloud Manager.
| Use Cases | Elements that fulfill Use Case |
|---|---|
| Upgrade multiple applications in parallel to accelerate customer value creation, increasing the speed with which new features can be implemented | Appliances and reusable system templates with Agile Cloud Manager’s DSL controlled efficiently by the Agile Cloud Manager’s CLI. Smaller number of reusable basic building blocks. Simplified application-level deployment experience. Enterprise-level pipelines. |
| Failover and Failback between different cloud providers | ACM CLI enables pipelines to run the same command regardless of the underlying infrastructure. Vendor-specific implementations of each system-template and of each basic building block created for each cloud vendor that you want to support. |
| Reduce redundant engineering efforts | Reusable system templates, reusable basic building blocks, and standardized pipelines. |
| Encapsulate security components | Reusable system templates, reusable basic building blocks, and standardized pipelines |
| Create cloned environments quickly | Change values in keys.yaml and in config.yaml |
| Manage business-level components more easily | Custom types of systems and of services enable your code to be encapsulated within units that have meaning for your business. Custom controllers that you can create can enable specialized behavior. CLI commands enable you to perform operations on your custom system types, custom service types, and individual service instances. |
| Integrate all engineering work into a single enterprise pipeline | CLI and DSL enable operations to be performed on units that have specific meaning to the business. Reusable system configurations and building blocks mean that differences between implementations are mainly in simple configuration so that less work is required to prove out new ideas. |
| Put infrastructure-as-code and configuration-as-code under agile project management | Software definition of every element with architectural diagrams makes it easy to integrate with project management tools. Enterprise-level pipelines make every element accountable for project management. |
| Simplify governance, security, and compliance | Rules are baked-into reusable building blocks. Pipelines control the use of each building block. Everything is modeled as a custom type relevant to your unique business. |
| Integrate any pipeline tool with infrastructure-as-code and with configuration-as-code | Simple CLI moves complexity out of pipeline scripts and into portable configuration files that can be used with any pipeline tool. |
| Reduce the amount that engineers are required to learn | Interfaces and code separation isolate scope of every engineering task. |
The next step is to read our article entitled “Architectural Migration and Governance”.
back to Site Home
back to Architecture section Home
Back to Part 15 of 16