Most teams reach for microservices when the system starts to hurt.
But here's a good quote to questions that approach:
"If you can't build a well-maintained monolith, what makes you think you can build a well maintained microservices system?"
In this module, you’ll walk through a clear approach for organizing system into microservices.
Some lessons focus on concepts and trade-offs, while others dive into concrete examples and real production scenarios.
You’ll define service boundaries, choose between synchronous and asynchronous communication, and reason about data and consistency in distributed systems.
Some of the material we’ll cover:
- 4 reasons to pick microservices (and 4 ways to achieve the same benefits with half of the cost)
- How to define service boundaries without creating a distributed monolith
- A concrete microservice template you can adapt for your own systems
- The common communication patterns and the trade-offs behind each
- Do you know how your distributed system is behaving in production right now? (If not, use these 3 signals to monitor your production)
