architecture-patterns

Layered architecture centralizes business logic in distinct tiers for monolithic systems. Microservices decompose functionality into independent services for scalability. Event-driven architecture uses asynchronous messaging for loose coupling. Select based on scale, team structure, and data consistency requirements.

Domain-driven design aligns system boundaries with business domains, using ubiquitous language and bounded contexts. Apply it when decomposing large systems into services or refactoring monoliths to clarify service responsibilities and prevent tangled dependencies.

Design RESTful or GraphQL APIs with clear contracts, versioning strategy, and gateway patterns. Use API gateways for routing, authentication, and rate limiting. Follow interface segregation principles to expose only necessary operations per client.

Event-driven architecture, saga patterns, and eventual consistency models address data consistency in microservices. Use message brokers for event publishing and subscription. Apply compensating transactions for distributed workflows requiring coordination.

Repository patterns abstract data access, isolating business logic from persistence details. Organize layers as presentation, business logic, and data access with unidirectional dependencies. Apply dependency injection to decouple components and ease testing.

Zero-trust security validates every request. Circuit breakers, timeouts, and retry logic handle failures. Use API gateways for centralized authentication. Event-driven systems provide resilience through asynchronous decoupling and message durability.