Aller au contenu principal
CAP theorem, consensus, message queues, microservices, and system design at scale.

Distributed Systems

CAP theorem, consensus, message queues, microservices, and system design at scale.

Niveau 6

Distributed Systems

CAP theorem, consensus, message queues, microservices, and system design at scale.

0/10 terminés 10 Disponible

Distributed Systems Fundamentals

Available

Understand the core challenges of distributed computing — fallacies, time/order, failure models, and the fundamental differences from single-machine systems.

Difficulty:
★★★★★
3/5 · Intermediate
Fallacies of Distributed Computing Partial Failure Clock Sync Network Partitions +1
2–3 hours
Requires: Network Models (OSI, TCP/IP), OS Overview: Kernel, Syscalls & Abstractions
Start Learning

CAP Theorem & Consistency Models

Available

Master the CAP theorem's consistency-availability-partition tolerance trade-off, plus strong vs eventual consistency models used in real systems.

Difficulty:
★★★★★
4/5 · Advanced
CAP Theorem Consistency Availability Partition Tolerance +1
2–3 hours
Requires: Distributed Systems Fundamentals
Start Learning

Consensus Algorithms (Raft/Paxos)

Available

Learn how distributed systems agree on a single value despite failures — Raft's understandable approach and Paxos's elegant foundation.

Difficulty:
★★★★★
5/5 · Expert
Leader Election Log Replication Quorum Term/Index +1
4–6 hours
Requires: CAP Theorem & Consistency Models
Start Learning

Distributed Data Structures

Available

The structural primitives that hold distributed systems together — consistent hashing with virtual nodes, Merkle trees, Gossip/SWIM, and the data structures behind ring-shaped coordination.

Difficulty:
★★★★★
4/5 · Advanced
Consistent hashing with virtual nodes Rendezvous (HRW) hashing Merkle trees for anti-entropy Gossip and SWIM-style membership +1
4 hours
Requires: Consensus Algorithms (Raft/Paxos), Hash Tables
Start Learning

Message Queues & Stream Processing

Available

Explore asynchronous communication patterns — publish/subscribe, message brokers, stream processing, and exactly-once semantics.

Difficulty:
★★★★★
3/5 · Intermediate
Pub/Sub Message Brokers Streams Consumer Groups +1
2–3 hours
Requires: Distributed Systems Fundamentals
Start Learning

Microservices Architecture & Patterns

Available

Design and reason about microservice systems — service decomposition, communication patterns, service discovery, and observability at scale.

Difficulty:
★★★★★
4/5 · Advanced
Service Decomposition API Gateway Service Discovery Circuit Breaker +1
3–5 hours
Requires: Distributed Systems Fundamentals, Message Queues & Stream Processing
Start Learning

Caching Strategies at Scale

Available

The distributed-systems view of caching — multi-level hierarchies, stampede prevention, dogpile/bounding, Bloom filters as cache guards, and CDN invalidation as a hard problem.

Difficulty:
★★★★★
3/5 · Intermediate
Multi-level cache hierarchy Cache stampede / thundering herd Bloom filters as negative caches CDN invalidation strategies +1
3 hours
Requires: Microservices Architecture & Patterns, Caching & CDNs
Start Learning

Distributed Transactions & Saga Patterns

Available

Coordinate state across services without a single ACID database — two-phase commit, the saga pattern, idempotency, and outbox tables in the real world.

Difficulty:
★★★★★
4/5 · Advanced
Two-Phase Commit Sagas Idempotency Outbox Pattern +1
3–4 hours
Requires: Microservices Architecture & Patterns, Transactions & ACID Properties
Start Learning

Backpressure, Load Shedding & Concurrency Limits

Available

Traffic shaping under overload — token buckets, adaptive concurrency, timeout budgets, hedged requests, and the laws that govern graceful degradation.

Difficulty:
★★★★★
4/5 · Advanced
Little's Law as the ceiling Token bucket and leaky bucket Adaptive concurrency limiting Timeout budgets and request hedging +1
3 hours
Requires: Distributed Systems Fundamentals, Microservices Architecture & Patterns
Start Learning

System Design Practice

Available

The engineering craft of designing systems at scale — back-of-envelope math, capacity planning, trade-off analysis, and worked designs for canonical problems like rate limiters, URL shorteners, and chat services.

Difficulty:
★★★★★
4/5 · Advanced
Capacity Estimation Trade-Offs Load Balancing Sharding +1
8–12 hours
Requires: Microservices Architecture & Patterns, Caching & CDNs
Start Learning