Monolith Decomposition Patterns
Patterns to help you incrementally migrate from a monolith to microservices.
Big Bang rebuilds of systems are so 20th century. With our users expecting new functionality to be shipped more frequently than ever before, we no longer have the luxury of a complete system rebuild. In fact, a big bang migration of a monolithic architecture into a microservice architecture can be especially problematic, as we’ll explore in this talk.
We want to ship features, but we also want to improve our architecture, and for many of us this means breaking down existing systems into microservices. But how do you do this while still regularly releasing new features?
In this talk, I’ll share with you some key principles and a number of patterns which you can use to incrementally decompose an existing system into microservices. I’ll also cover off patterns that can work to migrate functionality out of systems you can’t change, which are useful when working with very old systems or vendor products. We'll look at the use of strangler patterns, change data capture, database decomposition and more.
What You'll Learn
Coming out of this talk you’ll have a better understanding of the importance of evolving an architecture, along with some concrete patterns to help you do that on your own projects.
This talk should be suitable for any technologist who is interested in how to break down a monolith without resorting to a big bang rebuild. It's aimed primarily at developers and architects, but operations, testers and anyone actively involved in software delivery will be able to take something away from this talk.
You can view the slides here, although please note that given the way I use presentations, it may be hard to get a sense of what the talk is about just by looking at the slides.