Microservices

Edit · View history

Microservices (also known as the microservice architecture) is an architectural style that structures an application as a collection of loosely coupled, independently deployable services. Each service is self-contained and implements a single business capability. This contrasts with the traditional monolithic application where all functionality is combined into a single process.

History

The term "microservices" gained prominence in 2011–2012 through discussions among software architects and at technology conferences. The concept evolved from earlier service-oriented architecture (SOA) but emphasized finer granularity and improved modularity. In 2014, Martin Fowler and James Lewis published a seminal article "Microservices" that defined key characteristics. The approach was popularized by companies like Netflix, Amazon, and Uber, which successfully adopted microservices to scale their systems.

Characteristics

Service per business capability: Each microservice focuses on a single business function.
Independent deployability: Services can be updated, scaled, and deployed independently without affecting others.
Decentralized data management: Each service manages its own database or storage (database per service pattern).
Technology diversity: Different services can use different programming languages, frameworks, or data stores.
Resilience: Failure in one service does not cascade to others, often achieved through circuit breaker pattern and bulkhead pattern.

Benefits

Scalability: Individual services can be scaled independently based on demand.
Agility: Teams can develop, test, and deploy services in parallel, accelerating delivery.
Maintainability: Smaller codebases are easier to understand and modify.

Challenges

Complexity: Managing distributed systems introduces network latency, distributed transactions, and service discovery issues.
Data consistency: Maintaining eventual consistency across services requires careful design (e.g., saga pattern).
Testing and debugging: Inter-service communication makes end-to-end testing harder.

Tools and Technologies

Popular tools include Docker for containerization, Kubernetes for orchestration, and API gateways like Kong or AWS API Gateway. Monitoring tools such as Prometheus and Grafana are commonly used.

References

Fowler, M. & Lewis, J. (2014). Microservices.