Part 1 of 8 · 1 min read
Why this page comes fifth
In this module you will
- Explain what a microservice is and what makes the style different from libraries, modules and a monolith.
- List the main benefits, and say which cost pays for each one.
- Explain why microservices avoid shared databases and cross-service transactions, and what a saga is.
- Describe how team ownership and Conway's law shape the style.
- Say, in a few sentences, when microservices are the wrong choice.
Pages 3 and 4 covered styles with one or a few deployments. Microservices is the far end of that line: many small deployments, each with its own data. It is the style most often named in interviews and the one most often chosen too early. This page gives the case for it and the bill for it side by side. Two books are used. "Building Microservices" by Sam Newman (BM), chapters 1 and 10, gives the benefits and the team view. "Fundamentals of Software Architecture" (FSA), chapter 17, gives the topology, the data rules and the ratings. The numbers are made up to show the idea, unless the text names a book.