🧩Design Patterns
Proven design idioms that solve recurring structural, behavioral, and architectural challenges with loose coupling and robust resilience.
Foundational Invariants & Core Principles:
Stage 1: GoF Patterns
Sequential learning progression covering core mechanics of gof patterns.
GoF Design Patterns: Strategy, Decorator, Factory & Observer
GoF Design Patterns: Strategy, Decorator, Factory & Observer provides core foundational patterns in Software Design & Architecture. Apply battle-tested Gang of Four object-oriented design patterns to decouple algorithms and dynamically extend behavior.
Sidecar Proxy Pattern
Sidecar Proxy Pattern is a foundational topic in Distributed Systems & Storage. Engineers use it to make predictable trade-offs under load, failure, and evolving requirements.
Circuit Breakers & Resilience Patterns
Circuit Breakers monitor remote service call failure rates. If downstream failures exceed a threshold (e.g. 50%), the breaker trips to OPEN, instantly returning fallback responses instead of stalling threads.
Bulkhead & Fault Isolation
The bulkhead pattern limits resources per dependency or tenant—like ship compartments—so failures stay localized.
Rate Limiting & Token Buckets
Rate limiting controls the incoming request rate per client or IP address to prevent server overload, DDoS attacks, and resource starvation.
Stage 2: Circuit Breakers
Sequential learning progression covering core mechanics of circuit breakers.
Graceful Degradation Tiers
Graceful Degradation Tiers is a foundational topic in Distributed Systems & Storage. Engineers use it to make predictable trade-offs under load, failure, and evolving requirements.
Saga & Compensation Patterns
A saga breaks a global transaction into local transactions with compensations; orchestration centralizes flow while choreography uses events.
Transactional Outbox Pattern
The outbox table stores events in the same DB transaction as business rows; a relay process publishes to Kafka/RabbitMQ with at-least-once delivery.
Idempotency & Message Deduplication
At-least-once delivery is the practical default; idempotent handlers and deduplication tables turn duplicate deliveries into harmless no-ops.
Feature Flags & Progressive Delivery
Feature Flags & Progressive Delivery is a foundational topic in System Architecture & Design. Engineers use it to make predictable trade-offs under load, failure, and evolving requirements.
Explore Other Domain Curriculums
Distributed Systems
High-availability replication, event loops, quorum consensus, and horizontal database sharding.
Software Architecture
Decoupled event streaming, microservice resilience, CQRS, and domain-driven design.
Software Engineering
Clean code craft, automated testing pyramids, CI/CD pipelines, refactoring, and technical debt.
Algorithms & Data Structures
B-Trees vs LSM-Trees, graph traversal, consistent hashing rings, and asymptotic time-space trade-offs.