Comprehensive Overview of Microservices Architecture and Practices

Microservices Overview

Microservices are an architectural style that decomposes a monolithic application into a set of small, independently deployable services, each running in its own process and communicating via lightweight mechanisms such as HTTP RESTful APIs.

Advantages and Disadvantages

Advantages include small, cohesive services, faster development, language‑agnostic implementation, independent deployment, easier scaling, and improved team autonomy. Disadvantages involve distributed data consistency, testing complexity, and increased operational overhead.

Suitable Organizations

Organizations whose communication structures align with Conway's Law and that can adopt cross‑functional teams benefit most from microservices.

Core Technical Components

Service Discovery

Three common approaches: DNS‑based lookup, registration‑center based discovery (e.g., spring cloud), and client‑side load balancing with external registries.

Gateway

Acts as a reverse proxy, handling routing, authentication, rate‑limiting, logging, and can support blue‑green or canary deployments. Example: zuul with pre‑, routing, and post‑filters.

Configuration Center

Centralized management of configuration files; examples include Apollo, Disconf, and Spring Cloud Config.

Communication

Comparison of RPC (binary, strong coupling, high performance) vs REST (textual, loose coupling, lower performance).

Monitoring & Alerting

Key monitoring layers: log collection, metrics, health checks, tracing, and alerting. Tools include agents sending data to MQ, ELK, InfluxDB, and tracing systems like Zipkin, Pinpoint, SkyWalking, CAT.

Circuit Breaker, Isolation, Rate Limiting, Degradation

Pattern implemented with hystrix to protect services from cascading failures.

Containerization & Orchestration

Containers (e.g., Docker) provide lightweight isolation; orchestration engines such as Apache Mesos and kubernetes manage deployment, scaling, and networking.

Service Mesh (Pending Update)

Future section on service mesh integration.

References

Key literature includes Martin Fowler’s microservices overview, Conway’s Law, and various open‑source projects for tracing and monitoring.