Catalogue

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

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

KindRecordOrganisationYearSetup
Decision

Own the webhook pipeline after customers could not see what happened to a webhook, leaving a hosted queue

marble-2026-webhooks#d1

Marble2026
Decision

Workers atomically claim a delivery before sending so overlapping workers or retried queue messages do not send duplicates

marble-2026-webhooks#d2

Marble2026
Decision

Offload search and faceted filtering from shared Postgres to a dedicated search platform fed by denormalizing CDC

datadog-2025-cdc-replication#d1

Datadog2025Multi-region
Decision

Build the replication platform on asynchronous CDC via Debezium and Kafka Connect rather than synchronous replication

datadog-2025-cdc-replication#d2

Datadog2025Multi-region
Decision

Automate multi-step CDC pipeline provisioning with Temporal workflows

datadog-2025-cdc-replication#d3

Datadog2025Multi-region
Decision

Protect CDC pipelines from schema drift with pre-apply SQL validation and a backward-compatible Kafka Schema Registry

datadog-2025-cdc-replication#d4

Datadog2025Multi-region
Decision

Customize pipelines via Kafka Connect single message transforms, custom forks, and a centralized enrichment API

datadog-2025-cdc-replication#d5

Datadog2025Multi-region
Failure

One customer's endpoint outage made deliveries time out, filled the shared worker pool and delayed Directory Sync webhooks for everyone

workos-2025-directory-sync-webhooks#f1

WorkOS2025
Failure

Recurring Amazon EBS latency spikes and I/O stalls trigger daily database partial failures and correlated single-AZ events

planetscale-2025-ebs-failure-handling#f1

PlanetScale2025
Decision

Detect degraded EBS volumes with latency, idle-time, and file-write probes and automate zero-downtime reparenting and replacement

planetscale-2025-ebs-failure-handling#d1

PlanetScale2025
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

Pre-launch design, never shipped: a SQLite database per customer on the app servers, to put data near users

37signals-2025-fizzy-database#d1

37signals2025One database
Decision

Fall back to one shared MySQL database for all accounts days before launch

37signals-2025-fizzy-database#d2

37signals2025One database
Decision

Offer Best-Effort counters on EVCache alongside Eventually Consistent global counters instead of probabilistic sketches

netflix-2024-distributed-counter#d1peak under 100,000 requests/s

Netflix2024Multi-region
Decision

Log idempotent increments in Cassandra TimeSeries and roll up over a lagged immutable window

netflix-2024-distributed-counter#d2peak under 100,000 requests/s

Netflix2024Multi-region
Decision

Trigger rollups without distributed locks via per-instance in-memory queues, Set coalescing, lastWriteTs and read self-remediation

netflix-2024-distributed-counter#d3peak under 100,000 requests/s

Netflix2024Multi-region
Decision

Move I/O-bound telemetry receptors and processor from AWS Lambda and CloudFront to Cloudflare Workers

cloudflare-2024-baselime-migration#d1peak of 100,000 requests/s or more

Cloudflare2024Multi-region
Decision

Replace self-hosted ClickHouse on EC2, Kinesis, and multi-service AWS alerting with Workers Analytics Engine and Durable Objects

cloudflare-2024-baselime-migration#d2peak of 100,000 requests/s or more

Cloudflare2024Multi-region

65 more records. Sign in to see all 85.