Microservice Architecture: Concepts, Evolution, Design Patterns, Practices, and Pros & Cons

Microservice Architecture (Microservice) is an architectural style that decomposes a large application into a set of independent services, each focusing on a specific business capability, thereby reducing coupling and increasing flexibility.

The concept emerged around 2012, gained attention in 2014, and became mainstream in 2015, largely promoted by Martin Fowler.

Compared with traditional monolithic development, where all functionality is packaged into a single WAR and deployed on a JEE container, microservices isolate services into separate processes, enabling independent development, deployment, and scaling.

Key design patterns for microservices include Aggregator, Proxy, Chain, Branch, Data‑Sharing, and Asynchronous Messaging patterns, each addressing different integration and scalability needs.

Practical implementation requires solving four main problems: client access (often via an API Gateway), inter‑service communication (synchronous REST/RPC or asynchronous messaging), service discovery and registration (e.g., Zookeeper), and fault tolerance (retry, rate‑limiting, circuit‑breaker, load‑balancing, fallback).

Advantages of microservices are controllable complexity, independent scaling, technology heterogeneity, fault isolation, and rapid deployment; disadvantages involve operational overhead, increased communication cost, data consistency challenges, testing complexity, and deployment intricacy.

Adopting microservices also demands a mindset shift: focusing on business‑driven service boundaries, treating services as living products, embracing DevOps and containerization (Docker), and understanding underlying middleware principles.

References: various online articles and resources on microservice patterns, SOA vs. microservices, and resilience tools such as Netflix Hystrix.