SESSION + Live Q&A
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.
Speaker
Sam Newman
Microservice, Cloud, CI/CD Expert
Sam is a technologist focusing in the areas of cloud, microservices, and continuous delivery - three topics which seem to overlap frequently. Providing consulting, training and advisory services to startups and large multi-national enterprises alike, he has over 20 years in IT as a developer, sys...
Read moreFrom the same track
Beyond the Distributed Monolith: Rearchitecting the Big Data Platform
The BBC’s Audience Platform Data team collects, transforms and delivers billions of events each day from audience interactions with mobile apps and web sites such as BBC News, BBC Sport, iPlayer and Sounds.Last year we migrated to a new analytics provider and we took this as an...
Blanca Garcia-Gil
Principal Engineer on data platform @BBC
Monitoring All the Things: Keeping Track of a Mixed Estate
Monitoring all of a team’s systems can be tricky when you have a microservice architecture. But what happens when you have many teams, each building systems using totally different technology stacks? Add in decades of legacy systems and a sprinkling of third-party tools and you’ve got...
Luke Blaney
Principal Engineer Operations and Reliability Programme @FT
Why Distributed Systems Are Hard
Every company that has adopted microservices architecture operates a complex distributed system. It's basically a full-time endeavor to keep up with the ever-changing landscape of technologies and tools to build, maintain, and scale these towering production systems, but the fundamentals of...
Denise Yu
Senior Software Engineer @GitHub
To Microservices and Back Again
From the start, Segment embraced a microservice architecture in our control plane and data plane. Microservices have many benefits: improved modularity, reduced testing burden, better functional composition, environmental isolation, and development team autonomy, etc. but when implemented wrong...
Alexandra Noonan
Software Engineer @segment
Panel: Microservices - Are they still worth it?
Lots of us have moved away from monolithic architectures and embraced microservices but do we see the bang for the buck? Is the impact they are having a positive one or negative one? Is there an alternative middle ground? Have we learnt how to wrangle all the operational complexity inherent with...
Luke Blaney
Principal Engineer Operations and Reliability Programme @FT
Alexandra Noonan
Software Engineer @segment
Manuel Pais
IT Organizational Consultant and co-author of Team Topologies
Matt Heath
Senior Staff Engineer @Monzo