Microservices

Kind: style

Layer: Structural Core

Aliases: Microservice Architecture

Record: architecture:microservices

Severity: contextual

Scope: system, service, deployment

Canonical: Ontology

A convention of splitting a system into services that each own their data and deploy independently.

Listed in Architecture principles, after Package by Feature and before Monolith Architecture.

Requires

• Autonomy
• Independent Deployment

Reinforces

• Scalability
• Bounded Context

Enables

• Decentralized Ownership

Conflicts with

• Distributed Monolith

In tension with

• Operational Complexity
• Consistency

Tensions

• Microservices / Operational Complexity
• Microservices / Consistency

Violated by

• Shared Database
• Synchronous Chain Trap

Refactored by

• Split Bounded Context
• Own Data per Service
• Domain Events

Severity

• contextual

Category

• Codebase / System Architecture Styles

Reinforced by

• Decentralization

Linked from

• Anti-patterns
• Domain Architecture
• Control / Coordination / Centralization
• Core Modular Design
• Scalability / Performance / Optimization
• Transactions / State / Concurrency
• Codebase / System Architecture Styles
• Core Vocabulary
• Domain Architecture
• Event Messaging Async
• Severity levels
• The resolutions