“Ninety-five percent of the words are spent extolling the benefits of ‘modularity’ and that little, if anything, is said about how to achieve it”—Glenford J. Myers, 1978.
The above quote is 40 years old. Today, four decades later, nothing has changed except terminology. Time to fix this.
Vladik Khononov (Invesus Group) explains how to decompose a system into loosely coupled components: how to draw boundaries between services, how to decide whether some logic belongs to one service or another, and how domain-driven design can help us make those decisions. Finally, he takes a stab at answering the age-old question of what part of a microservice should be “micro” and how it can be measured.
You’ll hear about neither Docker nor Kubernetes. Actually, nothing related to infrastructure. Instead, you’ll dive into the difference between microservices and bounded contexts, discover when each pattern should be used, and get takeaways from Vladik’s experience optimizing microservices-quotebased architectures at Naxex.
This session was recorded at the 2019 O'Reilly Software Architecture Conference in San Jose.
- Title: On microservices, bounded contexts, and everything in between
- Release date: October 2019
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 0636920337485
You might also like
Design Patterns in the Real World, an Analysis-Based Approach
Alan Holub takes coders deep into the reality of Gang-of-Four design patterns, those reusable guides to …
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …
Software developers and architects increasingly turn to microservices as a framework for improving the agility and …
Head First Design Patterns, 2nd Edition
You know you don’t want to reinvent the wheel, so you look to design patterns—the lessons …