Catalogue

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

14 of 486 records match.

KindRecordOrganisationYearSetup
Decision

Build a minimal backup banking stack with separate software on GCP instead of replicating Primary

monzo-2025-stand-in#d1

Monzo2025Multi-region
Decision

Sync minimal immutable state asynchronously to Stand-in and replay Stand-in outcomes as verbatim Advices

monzo-2025-stand-in#d2

Monzo2025Multi-region
Decision

Deduplicate Stand-in and re-synced Primary transactions using a shared Correlation ID

monzo-2025-stand-in#d3

Monzo2025Multi-region
Decision

Coordinate failover with dual Configuration services and manual disable for gradual app rollback

monzo-2025-stand-in#d4

Monzo2025Multi-region
Decision

Proxy payments via Primary by default with direct data-centre fallback, testing both continuously in production

monzo-2025-stand-in#d5

Monzo2025Multi-region
Decision

Restrict Venice to asynchronous batch and stream writes with background version swaps, server-side partial updates, and hybrid replay

linkedin-2022-venice#d1peak of 100,000 requests/s or more

LinkedIn2022Multi-region
Decision

Push vector math onto Venice servers with Read Compute and embed Da Vinci as an eager local-state client library

linkedin-2022-venice#d2peak of 100,000 requests/s or more

LinkedIn2022Multi-region
Decision

Swap BDB-JE for pluggable RocksDB storage formats and operator-driven Zstandard shared-dictionary compression

linkedin-2022-venice#d3peak of 100,000 requests/s or more

LinkedIn2022Multi-region
Decision

Run active-active multi-region replication and rack-aware Apache Helix self-healing reusing the Full Push rebalance path

linkedin-2022-venice#d4peak of 100,000 requests/s or more

LinkedIn2022Multi-region
Decision

Enforce per-dataset storage and read quotas on multi-tenant clusters and group over-replicated partitions to bound fanout

linkedin-2022-venice#d5peak of 100,000 requests/s or more

LinkedIn2022Multi-region
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
Failure

Resuming from the last sent MySQL auto-increment id made the new webhook sender skip transactions in testing

nylas-2018-webhooks#f1

Nylas2018Sharded