System Design
Push traffic through real architectures and watch where they break.
Spread the load, cache it close to users, and cap abusers. Then copy and split the data, keep one failing service from taking down the rest, and move slow work to queues.
Sessions
Go in order. Each session is one idea you can drag, step and break.
01Scalability and performance
12 live · 1 comingHandle more users without slowing down.
Already live in other tracks: Streams and backpressure
Interactive
LiveVertical vs horizontal scaling
Make one server bigger or add more servers, and see where each one hits a wall.
Open session →
Interactive
LiveBack-of-the-envelope estimates
Turn daily users into requests per second, storage and bandwidth.
Open session →
Interactive
LiveLoad balancing strategies
Queues, health checks, and timeouts — not just which server is next.
Open session →
Interactive
LiveAutoscaling
Add servers when traffic climbs and remove them when it drops, without flapping.
Open session →
Interactive
LiveCaching and eviction
Watch a cache hit, miss and evict, then predict the next request.
Open session →
Interactive
LiveCache invalidation
Write-through, write-behind, TTLs and explicit purges: keeping cached data fresh.
Open session →
Interactive
LiveCDNs: caching at the edge
Pick a TTL, ship a new logo, and see which cities still get the old one.
Open session →
Interactive
LiveLatency, throughput and concurrency
Why a faster request and more requests per second are different goals.
Open session →
Interactive
Coming soonDatabase bottlenecks
Connection pools, slow queries, N+1 calls and read replicas.
Interactive
LiveRate limiting
Fixed window, sliding window and token bucket on the same burst.
Open session →
Interactive
LiveBackpressure and load shedding
Slow the sender or drop work on purpose before the whole system falls over.
Open session →
Interactive
LiveCounting at scale: HyperLogLog and count-min sketch
Count unique visitors and frequent items in kilobytes, by accepting a small error.
Open session →
Interactive
LiveTop-K, trending and leaderboards
Rank millions of scores live, and find what's trending right now.
Open session →
02Data and databases
5 live · 6 comingChoose where data lives and how it stays correct.
Interactive
Coming soonSQL, document and graph databases
Same data in three models: joins, flexible documents, or relationships first.
Interactive
Coming soonData modeling: normalize or denormalize
Design a schema, then trade duplicate data for faster reads.
Interactive
Coming soonIndexes and query optimization
Find one row in a million with a B-tree instead of a full scan, and pay for it on writes.
Interactive
Coming soonTransactions, ACID and isolation levels
Two people book the last seat at once: see which isolation level stops the double booking.
Interactive
LiveReplication and stale reads
Write to the leader, read from a follower, and crash the leader mid-write.
Open session →
Interactive
LiveSharding: choosing the shard key
Hash, country or date: see hot shards and queries that ask every shard.
Open session →
Interactive
LiveBloom filters
Answer "definitely not here" without touching the database, with a tunable false-positive rate.
Open session →
Interactive
Coming soonB-trees vs LSM trees and the write-ahead log
How databases lay data on disk, and why one is faster for reads and the other for writes.
Interactive
LiveChange data capture
Stream every database change to search, caches and analytics without dual writes.
Open session →
Interactive
LiveZero-downtime schema migrations
Change a table under live traffic: expand, migrate, then contract.
Open session →
Interactive
Coming soonTime-series databases
Metrics and sensor data: append-only writes, downsampling and retention.
03Networking and APIs
4 live · 4 comingHow services find and talk to each other.
Interactive
LiveDNS, TCP, TLS and HTTP: one request
Follow a request from a domain name to a response, one layer at a time.
Open session →
Interactive
Coming soonREST, GraphQL, gRPC and WebSockets
Four ways to shape an API, and what each one is good at.
Interactive
Coming soonSynchronous vs asynchronous communication
Wait for the answer, or hand off the work and get told later.
Interactive
LiveAPI gateways and service discovery
One front door for auth, routing and limits, and how it finds services that move.
Open session →
Interactive
LiveIdempotency and request deduplication
Send the same payment twice and charge it once.
Open session →
Interactive
LiveWebhooks
Call another system when something happens: signatures, retries and replay.
Open session →
Interactive
Coming soonService mesh
Sidecars handle retries, TLS and traffic splits between services.
Interactive
Coming soonHTTP/2, HTTP/3 and QUIC
Multiplexing, head-of-line blocking, and why HTTP/3 moved to UDP.
04Reliability and resilience
7 live · 1 comingKeep working when parts fail.
Interactive
LiveAvailability and the nines
What 99.9% really allows, and how redundancy buys more nines.
Open session →
Interactive
LiveFault tolerance and graceful degradation
Turn off the extras so the core feature keeps working.
Open session →
Interactive
LiveRetries and circuit breakers
Turn a retry storm into a fast failure and let the broken service recover.
Open session →
Interactive
LiveBulkheads
Split resources so one slow dependency can't use up every thread.
Open session →
Interactive
LiveFailover, disaster recovery, RTO and RPO
Lose a region and measure how long you're down and how much data you lose.
Open session →
Interactive
LiveCAP theorem and quorums
Split the network and choose: answer with stale data, or refuse until it heals.
Open session →
Interactive
Coming soonDistributed transactions and two-phase commit
Commit across two databases, and see what happens when the coordinator dies.
Interactive
LiveHedged requests and retry budgets
Send a backup request to cut slow tails, without doubling the load.
Open session →
05Distributed systems
12 live · 2 comingMany machines acting like one system.
Interactive
Coming soonEvent-driven architecture
Services react to events instead of calling each other directly.
Interactive
LiveMessage queues
Slow consumers, duplicate charges and a dead-letter queue: at-least-once in action.
Open session →
Interactive
Coming soonPub/sub and event streaming
Publish once; many consumers read a partitioned log at their own pace.
Interactive
LiveOrdering, delivery guarantees and duplicates
At-most-once, at-least-once, exactly-once, and keeping events in order.
Open session →
Interactive
LiveEventual consistency
Replicas disagree for a moment, then converge. When is that acceptable?
Open session →
Interactive
LiveCQRS and event sourcing
Store every change as an event and build separate read models from them.
Open session →
Interactive
LiveSagas and the transactional outbox
Run a multi-service order without a global transaction, and never lose the event.
Open session →
Interactive
LiveLeader election and consensus
Nodes vote in a leader with Raft; crash it and watch them elect another.
Open session →
Interactive
LiveDistributed locks
Only one worker may run the job: leases, fencing tokens and expired locks.
Open session →
Interactive
LiveConsistent hashing
Add and remove nodes and see how few keys move.
Open session →
Interactive
LiveUnique IDs at scale
Auto-increment, UUIDs and Snowflake IDs: ordering, collisions and coordination.
Open session →
Interactive
LiveClocks and ordering
Machine clocks drift: Lamport and vector clocks order events without them.
Open session →
Interactive
LiveGossip protocols
Spread membership and state through a cluster by talking to a few peers at a time.
Open session →
Interactive
LiveMerkle trees and anti-entropy
Find which data two replicas disagree on without comparing every row.
Open session →
06Software architecture
0 live · 4 comingHow to split a codebase into parts.
Interactive
Coming soonMonolith, modular monolith or microservices
Where to draw service boundaries, and what each split costs.
Interactive
Coming soonLayered, clean and hexagonal architecture
Keep business logic apart from the database and the web framework: ports and adapters.
Interactive
Coming soonDomain-driven design
Bounded contexts, aggregates and a shared language with the business.
Interactive
Coming soonArchitecture decision records
Write down why a choice was made so the next person doesn't undo it.
07Security and access control
0 live · 9 comingWho can do what, and keeping data safe.
Interactive
Coming soonAuthentication vs authorization
Who you are versus what you're allowed to do.
Interactive
Coming soonOAuth 2.0, OpenID Connect and JWTs
Sign in with another provider and pass tokens between services safely.
Interactive
Coming soonRole- and attribute-based access control
RBAC and ABAC: permissions by role, or by rules about the user and the data.
Interactive
Coming soonEncryption at rest and in transit
TLS on the wire, encrypted disks and keys you can rotate.
Interactive
Coming soonSecrets management
Keep API keys and passwords out of code, and rotate them without downtime.
Interactive
Coming soonAudit logs
Record who did what and when, in a log nobody can quietly edit.
Interactive
Coming soonThreat modeling and security boundaries
Map where untrusted input enters and what an attacker could reach.
Interactive
Coming soonXSS, CSRF and SQL injection
The classic web attacks from the OWASP Top 10, and what stops each one.
Interactive
Coming soonDDoS protection and WAFs
Absorb floods of traffic and filter bad requests before they reach your servers.
08Production engineering
2 live · 6 comingRun it, watch it and pay for it.
Already live in other tracks: A CI/CD pipeline, stage by stage, Containers vs virtual machines, Kubernetes rolling deploys
Interactive
Coming soonLogs, metrics and distributed tracing
Follow one slow request across five services.
Interactive
Coming soonMonitoring, SLOs and alerting
Alert on what users feel, not on every CPU spike.
Interactive
LiveBlue-green and canary deployments
Ship to a small slice of traffic first, and roll back in seconds.
Open session →
Interactive
Coming soonInfrastructure as code
Describe servers and networks in files you can review and repeat.
Interactive
Coming soonCapacity planning and cost optimization
Forecast growth, size for the peak, and stop paying for idle machines.
Interactive
LiveFeature flags
Ship code dark, turn it on for 1% of users, and switch it off without a deploy.
Open session →
Interactive
Coming soonChaos engineering
Break things on purpose in a controlled way to find weak spots first.
Interactive
Coming soonIncident response and postmortems
Roles, communication and a blameless write-up when production goes down.
09Web application design
3 live · 9 comingPutting it together for real products.
Interactive
Coming soonFrontend architecture
Component boundaries, state, data fetching and rendering choices.
Interactive
Coming soonBackend architecture
API boundaries, service layers and where business rules live.
Interactive
Coming soonAPI design: pagination, versioning and errors
Resource modeling, cursors vs offsets, validation and useful error responses.
Interactive
Coming soonSessions, tokens and refresh flows
Cookies or tokens, short-lived access and safe refresh.
Interactive
LiveReal-time: WebSockets, SSE and presence
Push live updates and show who is online, and what each approach costs.
Open session →
Interactive
Coming soonFile uploads and object storage
Signed URLs, multipart uploads and processing media after upload.
Interactive
LiveBackground jobs and scheduling
Workers, retries, cron and dead-letter queues for work users shouldn't wait on.
Open session →
Interactive
LiveMulti-tenancy
Keep each customer's data apart, with per-tenant settings and limits.
Open session →
Interactive
Coming soonSearch: indexing, filtering and ranking
Full-text search that returns the right results first.
Interactive
Coming soonMobile and offline sync
Local databases, syncing back, resolving conflicts and push notifications.
Interactive
Coming soonCollaborative editing
Two people type in the same document: operational transforms and CRDTs.
Interactive
Coming soonEmail and notification delivery
Queues, providers, retries, preferences and not sending the same alert twice.
10AI: LLM application architecture
1 live · 6 comingThe parts around the model.
Already live in other tracks: How an LLM picks the next token, The context window, turn by turn, Force valid JSON
Interactive
Coming soonLLM gateways: routing, fallbacks and versions
Pick a model per request, fall back when a provider fails, and pin versions.
Interactive
Coming soonPrompt templates and versioning
Treat prompts like code: templates, versions and safe rollouts.
Interactive
Coming soonContext windows and token budgets
Decide what fits in the prompt when everything can't.
Interactive
LiveStreaming responses
Send tokens as they're generated, through every hop to the browser.
Open session →
Interactive
Coming soonInference latency and token cost
Where the seconds and the money go, and how to cut both.
Interactive
Coming soonPrompting vs RAG vs fine-tuning
Which one to reach for: missing knowledge, missing behavior, or missing format.
Interactive
Coming soonSemantic caching
Reuse an answer when a new question means the same thing as an old one.
11AI: RAG and knowledge systems
0 live · 6 comingGive the model the right documents.
Already live in other tracks: Embeddings and similarity search, Hybrid search and reranking, RAG, step by step
Interactive
Coming soonDocument ingestion and chunking
Parse PDFs and pages, then split them so each chunk still makes sense.
Interactive
Coming soonEmbeddings and vector databases
Store vectors, search them fast, and filter by metadata.
Interactive
Coming soonRetrieval evaluation and reranking
Measure whether the right chunks come back, then reorder them.
Interactive
Coming soonCitations and source attribution
Show which document each part of the answer came from.
Interactive
Coming soonIncremental indexing
Update the index when one document changes, without rebuilding everything.
Interactive
Coming soonChanging embedding models
Swap the embedding model without breaking search: dual indexes and backfills.
12AI: Agents and orchestration
0 live · 6 comingModels that take actions.
Already live in other tracks: Call a tool, then answer, Agent patterns: workflow or agent?, Pause for a person, MCP: tools the model can call, A coding agent's loop
Interactive
Coming soonTool execution and sandboxing
Run the tool the model asked for, safely, with limits.
Interactive
Coming soonAgent loops and state machines
Model an agent as explicit states so you can see and resume where it is.
Interactive
Coming soonWorkflows vs autonomous agents
Fixed steps you control, or a model that decides the next step.
Interactive
Coming soonPlanning and task decomposition
Break a big request into steps, and replan when one fails.
Interactive
Coming soonMulti-agent coordination
Several agents share work: hand-offs, shared state and conflicts.
Interactive
Coming soonDurable execution and recovery
Crash mid-task and resume from the last step instead of starting over.
13AI: Context and memory
0 live · 5 comingWhat the model remembers between turns.
Interactive
Coming soonConversation and session state
Store the chat so it survives reloads, devices and server restarts.
Interactive
Coming soonShort-term and long-term memory
Working memory, semantic facts and episodes: what to keep and for how long.
Interactive
Coming soonMemory extraction, updates and conflicts
Pull facts from chats, fix wrong ones, and resolve contradictions.
Interactive
Coming soonContext selection and compression
Summarize and pick what matters when the history is too long.
Interactive
Coming soonPer-user memory and isolation
One user's memories must never reach another user.
14AI: Evaluation and quality
0 live · 4 comingKnow whether it actually works.
Already live in other tracks: Evals: is the new prompt better?
Interactive
Coming soonGolden datasets and regression tests
A fixed set of questions with known good answers, run on every change.
Interactive
Coming soonRetrieval quality vs answer quality
Faithfulness, relevance and correctness: find which stage caused a bad answer.
Interactive
Coming soonOnline evals, A/B tests and feedback
Measure quality on real traffic and feed it back into the next version.
Interactive
Coming soonTracing and debugging agents
See every model call, tool call and decision in one timeline.
15AI: Model serving and infrastructure
0 live · 4 comingRunning the models themselves.
Interactive
Coming soonHosted APIs vs self-hosted models
Pay per token or run your own GPUs: cost, control and effort.
Interactive
Coming soonGPU capacity, batching and queueing
Group requests to keep GPUs busy without making users wait.
Interactive
Coming soonQuantization and serving optimization
Smaller numbers, smaller models, faster answers, and what you lose.
Interactive
Coming soonProvider rate limits and quotas
Stay under tokens-per-minute limits across many users and keys.
16AI: Security and governance
0 live · 7 comingNew ways for AI systems to go wrong.
Interactive
Coming soonPrompt injection, direct and indirect
Instructions hidden in user input or in a retrieved document take over the model.
Interactive
Coming soonTool permissions and least privilege
Give an agent only the tools and scopes this task needs.
Interactive
Coming soonSensitive-data leakage
Stop secrets and personal data from reaching prompts, logs or other users.
Interactive
Coming soonTenant-aware retrieval
Only retrieve documents the current user is allowed to see.
Interactive
Coming soonOutput validation and action approval
Check what the model produced before the backend acts on it.
Interactive
Coming soonAI auditability and data retention
Keep a record of what the model saw and did, for as long as you need it, and no longer.
Interactive
Coming soonGuardrails and content moderation
Check inputs and outputs for unsafe content, off-topic requests and policy breaks.
17Specialized systems
0 live · 5 comingCommon product types that combine the above.
Interactive
Coming soonPayments and ledgers
Double-entry ledgers, reconciliation and never losing a cent.
Interactive
Coming soonEvent pipelines and data warehouses
Move events into analytics: batch vs streaming, and late data.
Interactive
Coming soonDistributed object storage
How systems like S3 store and replicate huge numbers of files.
Interactive
Coming soonMulti-region systems
Serve users from several regions: latency, failover and data residency.
Interactive
Coming soonEdge and IoT systems
Devices with patchy connections: telemetry, sync and updates.
18Case studies: design a system
0 live · 13 comingPut the pieces together: one product, end to end.
Interactive
Coming soonDesign a URL shortener
Short codes, redirects at scale, and counting clicks.
Interactive
Coming soonDesign a rate limiter
A shared limiter for many servers: where counters live and what happens when it fails.
Interactive
Coming soonDesign a notification system
Push, email and SMS to millions of users, with preferences and retries.
Interactive
Coming soonDesign a chat app
Messages, delivery receipts, presence and group chats.
Interactive
Coming soonDesign a news feed
Fan-out on write vs fan-out on read, and what to do about celebrities.
Interactive
Coming soonDesign search autocomplete
Suggestions in under 100 ms as the user types.
Interactive
Coming soonDesign file sync (like Dropbox)
Chunked uploads, deduplication and syncing edits across devices.
Interactive
Coming soonDesign video streaming
Upload, transcode, and adaptive bitrate playback through a CDN.
Interactive
Coming soonDesign ride sharing (like Uber)
Find nearby drivers with geohashing and match them in real time.
Interactive
Coming soonDesign a web crawler
Crawl billions of pages politely, without fetching the same page twice.
Interactive
Coming soonDesign a payment system
Charge exactly once, keep a ledger, and reconcile with the bank.
Interactive
Coming soonDesign a document assistant
RAG with citations that only shows each user documents they're allowed to read.
Interactive
Coming soonDesign a coding agent
Read the repo, propose a fix, run the tests, and report the evidence.
In production
Tools you can use
135 technologies across 46 live sessions. Same names in any language — pick a session to see how the idea maps to the real world.
Services, platforms, protocols and standards — not one stack.
Clouds make both kinds of scaling a configuration change.
Every system design starts with rough numbers.
Load balancers sit between clients and your app tier regardless of how the backends are written.
- NGINXSoftware
Reverse proxy with round robin, least connections, weighted upstreams, and health checks.
Official site ↗ - HAProxySoftware
L4/L7 balancing and observability for large deployments.
Official site ↗ - EnvoySoftware
Service mesh data plane; advanced routing and retries.
Official site ↗ - AWS Application Load BalancerPlatform
Managed HTTP balancing with target groups.
Official site ↗ - Kubernetes ServicePlatform
Cluster IP / Ingress distributes traffic to pods.
Documentation ↗
Every cloud has an autoscaler; the policy is the hard part.
The same hit / miss / eviction ideas show up in dedicated cache servers and in front of your app — in any language.
- RedisService
In-memory key–value store with TTL, LRU-style eviction policies, and replication.
Official site ↗ - MemcachedService
Simple, fast distributed memory cache for hot keys.
Official site ↗ - Amazon ElastiCachePlatform
Managed Redis or Memcached on AWS.
Official site ↗ - CDN edge cachePlatform
Cloudflare, Fastly, Akamai — cache HTTP responses close to users.
Official site ↗ - HTTP Cache-ControlStandard
Browser and proxy caching without a custom app cache.
Documentation ↗
Every cache layer needs an invalidation story.
Every CDN works the same way: edges near users, a cache with a TTL, and a way to purge.
- Cloudflare CDNService
Reverse-proxy CDN in hundreds of cities; purge by URL, tag or everything.
Official site ↗ - Amazon CloudFrontService
AWS's CDN with invalidations and cache policies.
Official site ↗ - FastlyService
Programmable edge cache with near-instant purge.
Official site ↗ - Varnish CacheSoftware
The open-source HTTP cache many CDNs grew from.
GitHub ↗ - HTTP Cache-ControlStandard
max-age, s-maxage and immutable decide how long edges keep a copy.
Documentation ↗
Every load test shows this curve.
Rate limits live in the gateway in front of your API, with counters in a shared store.
- RedisSoftware
INCR and EXPIRE make a shared counter every gateway can see.
GitHub ↗ - Envoy rate limit serviceSoftware
Global rate limiting for Envoy and Istio, backed by Redis.
GitHub ↗ - NGINX limit_reqSoftware
Leaky-bucket request limiting in the web server.
Official site ↗ - Kong GatewaySoftware
API gateway with rate-limiting plugins per consumer.
GitHub ↗ - HTTP 429Standard
Too Many Requests, with a Retry-After header.
Documentation ↗
Every queue and stream library has a backpressure mechanism.
HyperLogLog counts uniques in most analytics systems.
Sketches power trending lists and heavy-hitter detection.
Every major database ships leader–follower replication; the knobs are sync vs async and where reads go.
- PostgreSQL streaming replicationSoftware
WAL shipped to standbys; synchronous_commit picks sync or async.
GitHub ↗ - MySQL replicationSoftware
Binlog replication, with semi-synchronous mode.
GitHub ↗ - Amazon RDS read replicasService
Managed async replicas and Multi-AZ failover.
Official site ↗ - MongoDB replica setsSoftware
Write concern and read preference control durability and staleness.
GitHub ↗
When one database is too big, these systems split it by a shard key and route queries for you.
- VitessSoftware
Sharding layer for MySQL, born at YouTube.
GitHub ↗ - CitusSoftware
Distributed PostgreSQL: pick a distribution column, queries fan out.
GitHub ↗ - CockroachDBSoftware
Range-sharded SQL that splits and moves ranges automatically.
GitHub ↗ - MongoDB shardingSoftware
Hashed or ranged shard keys, with a router (mongos).
GitHub ↗
Bloom filters sit in front of slow lookups in databases, caches and browsers.
CDC keeps search, caches and warehouses in sync with the database.
Migration tools help, but expand and contract is a process.
Tracing tools show the whole path of a request.
Most API platforms put a gateway in front of services.
Payment and messaging APIs accept idempotency keys so clients can retry safely.
- Stripe idempotent requestsService
Send Idempotency-Key and Stripe replays the first result for 24 hours.
Official site ↗ - IETF Idempotency-Key headerStandard
Draft standard for the header and its error codes.
Official site ↗ - AWS Lambda Powertools idempotencySoftware
Store keys and results in DynamoDB around a handler.
Official site ↗
Every payment and SaaS platform sends webhooks.
Every SLA is expressed in nines.
Resilience libraries provide timeouts and fallbacks.
Timeouts, retries with backoff and circuit breakers are built into service meshes and resilience libraries.
- EnvoySoftware
Retry policies, timeouts and outlier detection between services.
GitHub ↗ - IstioPlatform
Service mesh that configures Envoy's retries and circuit breaking.
GitHub ↗ - Resilience4jSoftware
Circuit breaker, retry and bulkhead for JVM services.
GitHub ↗ - CircuitBreaker (Martin Fowler)Standard
The classic write-up of the pattern and its three states.
Official site ↗
Resilience libraries implement bulkheads as separate pools.
Clouds document these DR tiers explicitly.
Every replicated database makes this choice; most let you tune it per request.
- Cassandra consistency levelsSoftware
Choose ONE, QUORUM or ALL per read and write.
Official site ↗ - etcdSoftware
Raft-based key-value store that refuses writes without a majority (CP).
Official site ↗ - Amazon DynamoDBService
Eventually consistent reads by default; strongly consistent on request.
Official site ↗ - JepsenSoftware
Tests what databases really do during partitions.
Official site ↗
Hedging is built into some RPC frameworks.
Queues decouple producers from consumers in every stack; the delivery guarantees are what differ.
- Amazon SQSService
Visibility timeout, at-least-once delivery, dead-letter queues.
Official site ↗ - RabbitMQSoftware
Acks, redelivery and dead-letter exchanges.
GitHub ↗ - Apache KafkaSoftware
A replicated log; consumers commit offsets after processing.
GitHub ↗ - Redis StreamsSoftware
Consumer groups with pending entries and claims.
GitHub ↗
Queues give you at-least-once; consumers make it safe.
Leaderless stores let you tune R and W per query.
Event stores and stream processors make this practical.
Workflow engines run sagas; CDC tools relay outboxes.
Consensus sits under most coordination services.
Lock services give you leases; correctness under pauses needs fencing at the storage.
Distributed caches, databases and load balancers all use rings or similar schemes to move as little data as possible.
- Apache CassandraSoftware
Token ring with virtual nodes for data placement.
GitHub ↗ - Amazon DynamoDBService
Partitioning descended from the Dynamo paper's consistent hashing.
Official site ↗ - Envoy ring hash / MaglevSoftware
Load balancing that keeps a client on the same backend.
GitHub ↗ - Memcached clientsSoftware
Ketama consistent hashing spreads keys over cache servers.
GitHub ↗
Most large systems generate ids without a central counter.
Distributed databases choose a clock to order events.
Gossip runs membership in many distributed databases.
Merkle trees verify and sync data everywhere.
Deploy tooling automates these rollouts.
Flag platforms handle targeting and rollout for you.
Real-time services wrap these transports for you.
Every web framework has a job queue library.
SaaS platforms choose a tenancy model early.
Streaming has to be enabled at every hop.
Roadmap
Coming soonA step-by-step path through the track, with sessions and practice at each stage.
- Stage 1
Foundations and trade-offs
- Stage 2
Distributed systems and production design
- Stage 3
AI application architecture
- Stage 4
Agent and AI production systems
- Stage 5
Advanced architecture
Projects
Coming soonBuild something real to lock in the skill.
- Design a URL shortener
- Design a chat service
- Design a news feed