Tag: playground Basic
This content is a draft and will not be included in production builds.
39 articles tagged playground:
- Design: build a shortener that handles 38,600 req/s
- Design: move checkout from synchronous to asynchronous
- Design: uploading images and 2 GB lecture videos
- Matching: is this event schema change backward, forward, full or breaking?
- Matching: log, metric or trace for each question
- Matching: pick a design pattern for each situation
- Matching: pick a lock or isolation level for each situation
- Matching: pick an index type for each query
- Matching: pick the Cache-Control for each response
- Matching: pick the HTTP status code for each API case
- Ordering: a correct OAuth Authorization Code + PKCE login
- Ordering: a payment is declined in the middle of a saga
- Ordering: a Pod gets replaced during a rolling deploy
- Ordering: create an index online on a large table
- Ordering: rename a column with zero downtime
- Ordering: ship a new checkout with canary and feature flags
- Ordering: the incident response sequence
- Playground: learn by making decisions
- Scale Lab — Interview problem: a notification system
- Scale Lab — Interview problem: concert ticketing
- Scale Lab — Interview problem: realtime chat
- Scale Lab — Interview problem: URL shortener
- Scale Lab: build a system, run traffic, watch it fall over
- Scale Lab: Sandbox
- Scenario: a 3 a.m. incident, checkout p99 up to 4 seconds
- Scenario: a 5-million-follower account posts and every feed falls 40 minutes behind
- Scenario: a cache stampede at peak hour
- Scenario: a customer sees another company's invoices
- Scenario: a flash sale oversells inventory
- Scenario: a migration locks the orders table
- Scenario: a Node.js Pod gets OOMKilled every 6 hours
- Scenario: a payment timeout charges customers twice
- Scenario: a query slows down as the table reaches 30 million rows
- Scenario: a retry storm takes down the whole chain
- Scenario: an admin token leaks
- Scenario: an API leaks other customers' orders
- Scenario: checkout p99 hits 1.2 s while CPU sits at 40% of the limit
- Scenario: Kafka consumer lag climbs mid-campaign
- Scenario: probes trigger cascading restarts across the whole Pod fleet