DevOps and Continuous Delivery sets ideals and goals, but what do we do, when we do not find ourselves in the DevOps Utopia, but in the reality, with monoliths, legacy code and legacy organisation.
Systematic and Praqma share the viewpoint of the current day, looking towards the DevOps nirvana in the horizon.
16.30: Doors open
17.00: Welcome by Aarhus DevOps and Systematic
17.05: "Mission Critical Product Quality - Starting the DevOps Journey" - by Jens Erik Meldgaard, Systematic
17.35: "Configuration Management as prerequisite for Continuous Delivery" - by Troels Grosbøll-Poulsen, Systematic
18.00: Food and drinks
18.30: "Anti-patterns in decomposing a monolith" - by Dan Grøndahl Glavind, Praqma
20.00: Thanks and goodbye
"Mission Critical Product Quality - Starting the DevOps Journey"
- by Jens Erik Meldgaard, Systematic
Delivering mission critical quality products on time is not a trivial task. Success, growth and more intensive use of the products have made the challenges even more present. Development speed and cost is under pressure. Agile software development principles and methods like scrum, SAFe and focus on customer satisfaction have proven useful but not sufficient.
This talk will focus on the challenges in delivering mission critical products in a changing agile environment and how the start of the DevOps journey hopefully can help overcome some of the challenges.
"Configuration Management as prerequisite for Continuous Delivery"
- by Troels Grosbøll-Poulsen, Systematic
This talk is about how Configuration Management forms a foundation for Continuous Delivery.
It is described how there is a coherence between Continuous Delivery, pipeline architecture and Configuration Management.
An example of a pipeline design is given and it is described how this maps to the configuration items of the system.
"Anti-patterns in decomposing a monolith"
- by Dan Grøndahl Glavind, Praqma
Applications have a tendency to settle into a monolithic architecture.
The victims are often quality and sustainable pace. Monoliths complicates collaboration, maintainability and deployability.
The most common solution is to decompose. Disassembling a monolith is more like an epic adventure than an easy stroll in the park.
We often end up with all the trouble and very little of the gains of deconstructing our application.
In this talk Dan will cover anti-patterns in decomposing a monolithic application and how to combat them using insights and software architecture and organizational patterns.