In the fulfilment phase we engage with the DevOps team. Leveraging the dependency graph, the size of the DevOps team can be significantly reduced. Engineers can concentrate on the business solution, launch middleware components, deploy third party software and develop applications.
The infrastructure code, the platform design and the application-independent aspects are covered by a central team and exposed through the GraphQL API. This allows for faster iterations with more content.
IaC tools, like Terraform and Ansible, can still be used, but a service provider’s SDK has proven to be more efficient. Deployment functions are developed using popular runtimes like Golang and Python and packaged with the application code into a single directory, to truly provision infrastructure on demand. A GraphQL library is used to interface with the domain controller. Both the cloud provider- and the controller API communicate via HTTPS. This allows DevOps teams to work within the internal network, entirely managed by the internal user management system, making it unnecessary to manage individual cloud accounts. Service managers and Developers self-serve their needs through a portal and work independently from operations without violating existing policies and security guidelines.
Screenshots
