Deliver – how is the Software System Deployed on the Platform?

What good is the most beautiful, best, and most secure software if it cannot be efficiently rolled out into production?
We take care of this in the Deliver stopover, naturally with the background of our principles such as automation, traceability, reproducibility, and immutability.
What Can I Expect from this Stop?
The following topics are included in the Deliver stopover:
This stopover builds on the 12-Factor-App methodology and expands it with our wealth of experience on the topics mentioned. However, we do not pursue a “one-size-fits-all” approach, but have developed different reference models for different target groups. We then adapt these reference models specifically to the concrete needs of the customers.
The great advantage of this is that we immediately have a starting point that is iteratively adapted to the current context. So it is quasi a combination of the best features from already implemented solutions and a greenfield approach.
Why should I Stop at this Stop?
This stopover realizes our principles and our TAO towards software development and software operation:
The points mentioned are not marketing buzzwords for us, but enable our customers to have a clear competitive advantage in the delivery and operation of software, thanks to achieving:
How Does this Stop Work?
The most important step is the introduction of automation at all levels, from the infrastructure to scans and tests to software deployment with “Everything-as-Code“.
In doing so, immutable artifacts and semantic versioning provide considerable support. As this enables such comprehensive reproducibility and traceability.
Many of our customers need to be able to intervene manually in the delivery process at any time. Therefore, we always develop corresponding processes with the principle “automated and continuous delivery whenever possible, but with defined exit points“.
Once the outlined step has been taken, it is subsequently possible in a simple manner to introduce changes gradually, for example, using Canary Releases or Feature Flagging.
To explore this topic further, we will discuss in the next blog post what GitOps is, how it helps to achieve the points mentioned, and how it can ideally be implemented with ArgoCD.




