Catalogue

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

12 of 486 records match.

KindRecordOrganisationYearSetup
Decision

Store user segment membership for 270M+ users in roaring bitmaps downloaded from S3 at startup instead of Bloom filters

grab-2023-frequency-capping#d1

Grab2023Sharded
Decision

Enforce per-user frequency caps with a Redis sorted-set sliding log instead of DynamoDB or a sliding window limiter

grab-2023-frequency-capping#d2

Grab2023Sharded
Decision

Preload the Lua script via SCRIPT LOAD and pipeline per-user EVALSHA calls to avoid Redis Cluster CROSSSLOT errors

grab-2023-frequency-capping#d3

Grab2023Sharded
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

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
Decision

Serve every Q&A site from one multi-tenant application and keep web servers overprovisioned

stackoverflow-2016-architecture#d1peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Use Elasticsearch for search instead of SQL Server full-text search, because SQL CPUs are expensive

stackoverflow-2016-architecture#d2peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Cache in two layers, a web-server HTTP cache and Redis, and clear the first layer through Redis pub/sub

stackoverflow-2016-architecture#d3peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Push updates to browsers over websockets, which are more efficient than polling, at the cost of load balancer port exhaustion

stackoverflow-2016-architecture#d4peak under 10,000 requests/s

Stack Overflow2016Sharded