Catalogue

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

13 of 486 records match.

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
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
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

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
Decision

Offload failed stream items to a controlled-delay service to keep At-Least-Once retries from clogging checkpoints

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

MetaMulti-region