Catalogue

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

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

KindRecordOrganisationYearSetup
Decision

Build DocDB as a self-managed sharded DBaaS in Go over MongoDB Community with a minimal query API

stripe-2024-docdb#d1peak of 100,000 requests/s or more

Stripe2024Sharded
Decision

Sort bulk-imported chunk data by common index attributes before inserting into B-tree storage

stripe-2024-docdb#d2peak of 100,000 requests/s or more

Stripe2024Sharded
Decision

Replicate migration writes bidirectionally from Kafka and S3 CDC oplogs and verify with snapshots

stripe-2024-docdb#d3peak of 100,000 requests/s or more

Stripe2024Sharded
Decision

Cut over chunk traffic in under two seconds using a custom MongoDB versioned-gating patch

stripe-2024-docdb#d4peak of 100,000 requests/s or more

Stripe2024Sharded
Decision

Reuse online chunk migration for shard bin-packing and single-step major MongoDB upgrades

stripe-2024-docdb#d5peak of 100,000 requests/s or more

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

Horizontally reshard Postgres space shards from 32 to 96 smaller instances instead of scaling vertically

notion-2023-postgres-reshard#d1

Notion2023Sharded
Decision

Replicate logical schemas to new shards with Postgres logical replication and deferred index builds

notion-2023-postgres-reshard#d2

Notion2023Sharded
Decision

Shard the PgBouncer cluster into four groups of 24 space shards before database cutover

notion-2023-postgres-reshard#d3

Notion2023Sharded
Decision

Verify with sampled bounded dark reads and cut over per shard via PgBouncer pause and reverse replication

notion-2023-postgres-reshard#d4

Notion2023Sharded
Decision

Rebalance podded MySQL shards online by migrating individual shops with Ghostferry

shopify-2021-mysql-shard-balancing#d1

Shopify2021Sharded
Decision

Plan shard rebalancing from historical utilization cohorts and pre-move simulations rather than shop counts

shopify-2021-mysql-shard-balancing#d2

Shopify2021Sharded
Decision

Guard online shop migration with SELECT FOR UPDATE batch locking, Redis MRSW cutover locks, verifiers and TLA+

shopify-2021-mysql-shard-balancing#d3

Shopify2021Sharded
Decision

Shard the Postgres monolith in application code once autovacuum stalled, rather than scale up or adopt a packaged sharding product

notion-2021-postgres-sharding#d1

Notion2021Sharded
Decision

Partition by workspace ID and shard every table reachable from the block table

notion-2021-postgres-sharding#d2

Notion2021Sharded
Decision

Move to shards with an audit log and catch-up script, not logical replication, because the strained monolith left little room for extra load

notion-2021-postgres-sharding#d3

Notion2021Sharded
Decision

One reader per shard replaces one reader thread per customer webhook after delays reached 10 minutes

nylas-2018-webhooks#d1

Nylas2018Sharded
Decision

Kinesis chosen over the MySQL binlog and Kafka as the ordered source of changes, mainly for operational simplicity

nylas-2018-webhooks#d2

Nylas2018Sharded
Decision

New sender ran two months in a simulated mode that sent nothing, compared against the legacy sender, before cutover

nylas-2018-webhooks#d3

Nylas2018Sharded

12 more records. Sign in to see all 32.