Skip to main content
SDMastery

Architecture Patterns

13 topics in architecture patterns.

advanced

CQRS

CQRS separates read and write models so each can be optimized independently — write to a normalized database, read from a denormalized projection.

11 min read
beginner

Client-Server Architecture

Client-server is the most fundamental architectural pattern. Understanding it is the starting point for all system design discussions.

6 min read
advanced

Event Sourcing

Event Sourcing stores every state change as an immutable event. The current state is derived by replaying events, providing a complete audit trail and.

11 min read
intermediate

BFF Pattern

Backend for Frontend (BFF) creates dedicated backend services for each frontend type (web, mobile, TV), tailoring API responses to each client's specific.

11 min read
intermediate

Microservices Architecture

Microservices enable large engineering teams to work independently, deploy frequently, scale individual components, and use the best technology for each.

9 min read
intermediate

Serverless Architecture: Functions, Cold Starts and Scaling Tradeoffs

Learn serverless architecture for system design: FaaS, cold starts, event triggers, scaling limits, state management, observability, and cost tradeoffs.

7 min read
intermediate

Strangler Fig Pattern

The Strangler Fig Pattern incrementally migrates a legacy monolith to microservices by routing traffic to new services one feature at a time, avoiding.

11 min read
intermediate

Blue-Green Deployment: Zero-Downtime Releases and Rollbacks

Learn blue-green deployment for system design: parallel environments, traffic switching, database migration risks, rollback strategy, and release tradeoffs.

11 min read
intermediate

Event-Driven Architecture: Events, Brokers and Loose Coupling

Master event-driven architecture: producers, consumers, brokers, event schemas, ordering, idempotency, outbox pattern, and microservice tradeoffs.

10 min read
intermediate

Canary Release

Canary release gradually rolls out a new version to a small percentage of users first, monitoring for issues before expanding to 100%, reducing the blast.

11 min read
intermediate

Peer-to-Peer Architecture

P2P eliminates the need for central servers, making systems more resilient and cost-effective for certain use cases.

7 min read
beginner

Feature Flags: Progressive Delivery, Experiments and Safe Rollouts

Learn feature flags for system design: kill switches, percentage rollout, A/B tests, config stores, flag debt, consistency, and release tradeoffs.

11 min read
intermediate

Monolith vs Microservices

When to use a monolithic architecture versus microservices, the real tradeoffs involved, and practical migration strategies used by companies like.

13 min read