This article reviews 'Software Architecture: The Hard Parts', highlighting eight key architectural challenges including trade-offs, data-architecture tensions, service granularity, database decomposition, distributed data access, contract design, code reuse, and error handling in distributed systems.
This article compares microservices and SOA, covering design philosophy, service granularity, autonomy, communication mechanisms, and deployment/operations, highlighting how microservices favor lightweight protocols, independent deployment, and container orchestration, while SOA relies on centralized middleware and coarse‑grained services.
This article examines the challenges of service proliferation in a microservice‑based system, defines modularity and granularity, and presents systematic splitting and merging factors—such as responsibility, fault tolerance, performance, scalability, cost‑benefit, and team size—using a concrete Promise service case study to guide optimal service design.
This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
The article examines typical microservice anti‑patterns—including overly fine or coarse service granularity, blindly following trends, and static contract versioning—explains why they occur, illustrates each with diagrams and code snippets, and offers practical guidance for making balanced architectural decisions.
