There are several factors to adopting the practices of Continuous Delivery. Most organizations start with tools. Should we adopt PaaS, is a container eco-system the right approach? Sadly if you currently have any legacy software or infrastructure you will soon find that these are not the hard questions you need to answer. Adopting continuous delivery practices requires change that includes organizational structure, processes and architecture. You cannot tackle one without the other as Conway's Law states they are inherently intertwined. So how do you create an organizational culture, methodology and architecture that supports rapid delivery of software, whilst still keeping your legacy systems up and running? How do you avoid common pitfalls or anti-patterns, which will hinder your ability to deliver? In this talk, I will address patterns such as micro-services, evolutionary architecture and empowered x-functional teams, which can speed up your delivery, but are not a free lunch. And how you move from your current monolith to adoption of these patterns.
