Software Architecture Patterns, Antipatterns, and Pitfalls
by Mark Richards, Neal Ford, Raju Gandhi
Chapter 13. Microservice All the Things Pitfall
Microservices has been a very popular architectural style for the past decade. Many architects and development teams, whether creating a microservices architecture from scratch or migrating to one from a legacy system, assume that their entire system must be microservices. This chapter demonstrates that this assumption is a pitfall: it is never a good idea, even from the start.
Table 13-1 summarizes the metadata for the Microservice All the Things pitfall. Because this chapter deals with a pitfall, no characteristics are improved. The “Degraded” metadata refers to the characteristics that are degraded when adopting this pitfall.
| CATEGORY | METADATA |
|---|---|
CONTEXT: |
Microservices, Modularity, Service Granularity |
IMPROVED: |
Domain Alignment |
DEGRADED: |
Atomicity, Cost, Data Consistency, Data Integrity, Simplicity |
Should I Make Everything a Microservice?
Done right, microservices is ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access