We all want to get out of the rot of traditional SDLC, waterfall, big ball of mud… We want to be faster, more flexible, providing more value upfront, WINNING 🙂, have short feedback loops, be able to work in small cross-functional teams.To do that we want to be able to do continues delivery and continues deployment which leads us to what is described in the DevOps handbook...

To do that: You should be able to reliably (tested, secure….) deploy small units of work to production (reduce the risk in deploying new code to production (roll forward, blue-green )). Have many teams work in parallel autonomously across the system functions (business). Decrease lead time of features and bug fixes to production.

This is all well and good but when we try to get there we keep getting pulled back by our architecture.

When we look at successful DevOps transformations we see that architecture is one of the significant factors of success.

In this talk, we will cover Identifying boundaries, monolith decomposition and bounded contexts and how we can build better microservices so our DevOps will be a win.

YOU MAY ALSO LIKE:

• Why Service Oriented Architecture? (SkillsCast recorded in October 2016)
• FullStack Event Sourcing and Applied DDD with Roman Sachse (Online Course on 23rd - 25th September 2020)
• Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (Online Course on 28th September - 2nd October 2020)
• Building and Leading Remote Teams (Online Meetup on 19th August 2020)
• The History of DevOps at Amazon (Online Meetup on 16th September 2020)
• Debugging Containers on Kubernetes with "kubectl debug" (SkillsCast recorded in July 2020)
• Retrospectives Antipatterns — Team Meetings That Don't Suck (SkillsCast recorded in July 2020)