Elevator Pitch
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 🙂.
Description
You want to do DevOps and move fast using continuous delivery but your architecture is holding you back. In this talk, we will look at how a microservices architecture is essential to make DevOps and CI/CD successful.
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 🙂.
Notes
Build stuff Nov 2017: SOA lessons learnt (OR Microservices done better)
Vox Vienna June 2017: SOA lessons learnt (OR Microservices done better)
Codemotion Milan November 2018: [Successfully Decomposing Your Monolith or UpdateUser(); Means Nothing To Me] (https://www.youtube.com/watch?v=yxjrObdWQow)