Catalogue

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

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

KindRecordOrganisationYearSetup
Decision

Replace managed object storage with Versity S3 Gateway on one server, backed up by rsync, to stop provider slowdowns

healthchecks-2026-object-storage#d1peak under 1,000 requests/s

Healthchecks.io2026One server
Decision

Use cloud-based AWS Elemental transcoding paired with a custom packager and custom Live Origin

netflix-2025-live-streaming#d1

Netflix2025Multi-region
Decision

Deliver live video over the existing Open Connect CDN shared with on-demand streaming

netflix-2025-live-streaming#d2

Netflix2025Multi-region
Decision

Stream live video over HTTPS with 2-second segments and cloud-delivered segment-template manifests

netflix-2025-live-streaming#d3

Netflix2025Multi-region
Decision

Validate live changes with internal test streams, synthetic load up to 100K starts/sec, failure injection, and scheduled live practice

netflix-2025-live-streaming#d4

Netflix2025Multi-region
Decision

Pair viewership-prediction pre-provisioning with prioritized load shedding and feature degradation

netflix-2025-live-streaming#d5

Netflix2025Multi-region
Failure

Recurring brief live viewing interruptions triggered manual stream restarts and 10x traffic increases

netflix-2025-live-streaming#f1

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

Replace the monolithic Reloaded video pipeline with microservices on Cosmos and switch over by use case

netflix-2023-video-processing-pipeline#d1

Netflix2023
Decision

Split video stages by domain boundary while hiding chunked encoding and assembly inside VES

netflix-2023-video-processing-pipeline#d2

Netflix2023
Decision

Separate member streaming and studio operations into dedicated workflow orchestrators over shared video services

netflix-2023-video-processing-pipeline#d3

Netflix2023
Decision

Acknowledge archives only after they reach standard S3, not the reduced-redundancy class

tarsnap-2023-infrastructure#d1

Tarsnap2023
Decision

Run the server on one EC2 instance and accept an outage if its hardware fails

tarsnap-2023-infrastructure#d2

Tarsnap2023
Failure

An EC2 power loss corrupted the metadata disk, and a full rebuild from S3 ran slowly through recovery code only ever tested on small data

tarsnap-2012-ec2-power-outage#f1

Tarsnap2012
Decision

Keep all user data in S3 and only cached metadata on the EC2 server so that all server state can be rebuilt

tarsnap-2012-ec2-power-outage#d1

Tarsnap2012
Decision

Treat the corrupted local state as untrustworthy and rebuild it all from S3 instead of trusting it

tarsnap-2012-ec2-power-outage#d2

Tarsnap2012
Decision

Introduce a dedicated BFF microservice returning view models instead of putting UI fields on platform APIs

lyft-2023-bikes-scooters-sdui-bff#d1

Lyft
Decision

Combine Declarative Components with client-side Semantic Components and decoupled chainable Actions

lyft-2023-bikes-scooters-sdui-bff#d2

Lyft

5 more records. Sign in to see all 25.