Understanding Microservice Architecture: Concepts, Advantages, Challenges, and Comparison with Monolithic Architecture

Author: cyfonly

Source: http://www.importnew.com/23227.html

Recently the term "microservice architecture" has become popular; a programmer named Cheng Xiaopang wanted to learn it, and his architect colleague Lao Wang, who is researching microservice adoption, explained the concepts.

Wang first emphasized that to understand microservices one must first understand system architecture design, which describes how an application is divided into parts based on business, technology, organization, flexibility, scalability, and maintainability, and how these parts cooperate to deliver value.

Three‑Layer Architecture

The three‑layer architecture consists of presentation layer, business logic layer, and data access layer. Early web applications combined all three into a single layer; later, data access was separated forming a two‑layer architecture; finally, presentation and business logic were split, resulting in the three‑layer model.

In a monolithic (single‑block) architecture, all layers run in the same process, so the code is compiled, packaged, and deployed together.

Advantages of Single‑Block Architecture

1. Easy development: simple workflow, good IDE support, easy debugging.

2. Easy testing: all functionality runs in one process, enabling system testing after startup.

3. Easy deployment: a single software package can be released to a server.

4. Easy horizontal scaling: adding a new server node with the same runtime environment allows the application to run.

Disadvantages of Single‑Block Architecture

1. High maintenance cost: as functionality and team size grow, communication and management costs increase, and bug analysis becomes more complex.

2. Long continuous‑delivery cycles: build and deployment time increase with more features.

3. Long onboarding time for new members.

4. High technology‑selection cost: adopting a new technology or framework later is risky.

5. Poor scalability: vertical scaling becomes expensive, and horizontal scaling is limited because all code runs in one process.

Microservice Architecture Overview

Microservice architecture is an architectural style that divides a single application into a set of small, independent services that communicate via lightweight mechanisms (usually HTTP‑based RESTful APIs). Each service is built around a specific business capability and can be deployed independently.

Key Characteristics of Microservices

1. Single Responsibility – each service is a high‑cohesion, low‑coupling unit that performs one business function.

2. Lightweight Communication – services interact using language‑ and platform‑agnostic formats such as JSON or XML over HTTP.

3. Independence – services are developed, tested, and deployed independently.

4. Process Isolation – each service runs in its own process, allowing independent deployment to different hosts.

5. Service as Component – services are reusable components with clear, language‑independent interfaces, though they rely on network reliability.

6. Business‑Oriented Teams – teams are organized around business capabilities rather than technical specialties.

7. Product‑Focus – teams own the full lifecycle of a service, fostering product ownership.

8. Technology Diversity – each service can use the most suitable technology stack for its domain.

9. Independent Business Data – each service manages its own data, enabling flexible data interfaces.

10. Infrastructure Automation – high demands on continuous delivery and DevOps practices.

Microservices vs. SOA

SOA Implementation

Microservice Implementation

Enterprise‑level, top‑down

Team‑level, bottom‑up

Coarse‑grained services composed of subsystems

Fine‑grained services split from a system

Enterprise Service Bus, centralized

Loose coupling, no central bus

Complex integration (ESB/WS/SOAP)

Simple integration (HTTP/REST/JSON)

Monolithic inter‑dependencies, complex deployment

Independent service deployment

Challenges of Adopting Microservices

1. Distributed System Complexity – performance overhead, reliability concerns, asynchronous communication difficulty, and data consistency trade‑offs (CAP theorem).

2. Operational Costs – configuration, deployment, monitoring, and log collection for each service increase exponentially.

3. Automated Deployment – frequent releases require robust CI/CD pipelines.

4. DevOps and Organizational Change – developers take full ownership of services, while operations shift to a consulting role.

5. Dependency Testing – ensuring correct inter‑service contracts becomes a major testing challenge.

6. Dependency Management – visualizing and managing numerous service dependencies is non‑trivial.

In summary, microservice architecture addresses many pain points of the three‑layer monolithic model but also introduces new complexities that must be carefully evaluated before adoption.