Catalogue

Cards
165
Records
486
Workloads
19
Corpus version
74847648e25a
Workload
Kind
Setup

21 of 486 records match; the first 20 are shown.

KindRecordOrganisationYearSetup
Failure

Brief pod reduction during routine rollout saturated remaining sites, OOMed service-mesh sidecars, and triggered invalid-job runner retries

github-2026-actions-rollout-saturation#f1

GitHub2026Multi-region
Failure

Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them

bluesky-2025-lossy-timelines#f1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines

bluesky-2025-lossy-timelines#d1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Cache high-follow accounts in a Redis sorted set loaded into memory every 30 seconds instead of reading follow counts per write

bluesky-2025-lossy-timelines#d2peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Batch ping writes with COPY in one transaction instead of calling a stored procedure once per ping

healthchecks-2025-ping-ingest#d1peak under 100,000 requests/s

Healthchecks.io2025One database
Decision

Cache not-found results for UUID ping URLs so repeated pings to missing checks skip the database

healthchecks-2025-ping-ingest#d2peak under 100,000 requests/s

Healthchecks.io2025One database
Decision

Scale ZippyDB keyspaces online via logical-to-physical shard indirection and coordinator-worker resharding

meta-2023-threads#d1

Meta2023Sharded
Decision

Offload Instagram-to-Threads follow-graph mirroring and notifications to rate-limited Async workers

meta-2023-threads#d2

Meta2023Sharded
Failure

A viral customer's pageviews backlog the shared queue for all sites while the database runs out of disk IOPS

fathom-2020-viral-customer-backlog#f1

Fathom Analytics2020One database
Failure

Unindexed backlog tables and a text-typed site ID kept the database slow after the disk was fixed

fathom-2020-viral-customer-backlog#f2

Fathom Analytics2020One database
Decision

Cap concurrent queue workers on purpose to protect the database, accepting a bigger backlog

fathom-2020-viral-customer-backlog#d1

Fathom Analytics2020One database
Decision

Limit pageviews processed per site per minute so one viral site cannot block the rest, then drop it

fathom-2020-viral-customer-backlog#d2

Fathom Analytics2020One database
Failure

Database contention filled Redis memory, and a full Redis could neither accept nor release jobs

slack-2017-job-queue#f1peak under 100,000 requests/s

Slack2017Sharded
Decision

Added Kafka in front of the Redis job queue instead of replacing Redis

slack-2017-job-queue#d1peak under 100,000 requests/s

Slack2017Sharded
Decision

Enqueue path acknowledges after the Kafka leader only, trading a small risk of lost jobs for latency

slack-2017-job-queue#d2peak under 100,000 requests/s

Slack2017Sharded
Failure

A hundred checker Lambdas each opened a database connection at once, and Postgres refused further connections

onlineornot-2023-lambda-write-fan-in#f1

OnlineOrNotOne database
Decision

Fan results in through SNS and a batching queue so one Lambda writes to Postgres, instead of upgrading the database

onlineornot-2023-lambda-write-fan-in#d1

OnlineOrNotOne database
Decision

Split the monolithic Dispatcher into per-source Tailer adapters and a generic Scheduler service

meta-2023-async-tier#d1peak of 100,000 requests/s or more

MetaMulti-region
Decision

Switch workload transport from pull to RPC push from Tailers to the Scheduler

meta-2023-async-tier#d2peak of 100,000 requests/s or more

MetaMulti-region
Decision

Support both FOQS queues and Scribe streams as first-class storage backends for async jobs

meta-2023-async-tier#d3peak of 100,000 requests/s or more

MetaMulti-region

1 more records. Sign in to see all 21.