Microservicessystem_design~12 mins

Architecture decision records (ADR) in Microservices - Architecture Diagram

Choose your learning style9 modes available

Learn Why Deep Arch Practice Challenge Design Recall Scale

System Overview - Architecture decision records (ADR)

This system manages Architecture Decision Records (ADRs) for a microservices environment. It helps teams document, store, and retrieve architectural decisions to ensure clarity and consistency across services. Key requirements include easy access, version control, and integration with development workflows.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  v
+------------------+      +----------------+
| ADR Management    |<---->| Version Control|
| Service           |      | Service        |
+------------------+      +----------------+
        |
        v
+------------------+
| Database         |
+------------------+

Components

User

client

Developer or architect accessing ADR system

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Routes requests to ADR Management Service and handles authentication

ADR Management Service

service

Handles creation, retrieval, update, and deletion of ADRs

Version Control Service

service

Manages versioning and history of ADR documents

Database

database

Stores ADR metadata and content

Request Flow - 8 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → ADR Management Service

ADR Management Service → Version Control Service

ADR Management Service → Database

ADR Management Service → API Gateway

API Gateway → Load Balancer

Load Balancer → User

Failure Scenario

Component Fails:Database

Impact:ADR content cannot be read or saved; version history may be incomplete

Mitigation:Use database replication and failover to maintain availability; cache recent ADRs for read access

Architecture Quiz - 3 Questions

Test your understanding

Which component handles authentication before routing requests to the ADR service?

AAPI Gateway

BLoad Balancer

CVersion Control Service

DDatabase

Design Principle

This architecture uses a layered approach with a load balancer and API gateway to manage traffic and security. Separating version control from ADR management allows focused handling of document history. Database replication and caching improve reliability and performance.