A Comprehensive Overview of Core Microservices Architecture

After a month of learning distributed microservice architecture, the author presents a complete walkthrough of the core concepts, including service discovery, gateways, configuration centers, and monitoring components.

What is Microservice – According to Martin Fowler, microservices are an architectural style that decomposes a monolithic application into small, independently deployable services communicating via lightweight protocols such as HTTP/REST.

Key Characteristics

Small, independent services

Each runs in its own process (e.g., Tomcat, Jetty)

Lightweight communication (smart endpoints, dumb pipes)

Independent deployment and technology choices

Improved manageability for large teams

Pros and Cons – Benefits include better code cohesion, faster development, team autonomy, language heterogeneity, easy third‑party integration, and clear ownership; drawbacks involve data consistency, testing complexity, and operational overhead.

Suitable Organizations – Organizations that follow Conway’s Law (system design mirrors communication structure) are ideal for microservices.

Microservice Technical Architecture

Service Discovery – Three main approaches: DNS‑based, registry‑center with client‑side load balancing, and client‑side load balancing with external proxy.

API Gateway – Acts as a reverse proxy, providing routing, security, rate limiting, logging, and can support blue‑green or canary deployments.

Configuration Center – Centralizes configuration management to avoid scattered config files; examples include Disconf, Spring Cloud Config, and Ctrip’s Apollo (https://github.com/ctripcorp/apollo).

Communication – Two main remote‑call styles are illustrated in a comparison table.

Monitoring & Alerting – Covers log monitoring, metrics, health checks, tracing, and alarm systems, with a typical monitoring architecture diagram.

Tracing (APM) – Describes how distributed tracing works (e.g., Zipkin) and shows a comparison of popular tracing tools.

Circuit Breaker, Isolation, Rate Limiting, Degradation – Explains Hystrix workflow with diagrams.

Container & Orchestration – Discusses Docker containers, their advantages over VMs, and orchestration engines such as Apache Mesos and Kubernetes, with architecture diagrams.

The article concludes with a call to join an architect community and a copyright notice.