Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
30 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Decision | Own the webhook pipeline after customers could not see what happened to a webhook, leaving a hosted queue | Marble | 2026 | |
| Decision | Workers atomically claim a delivery before sending so overlapping workers or retried queue messages do not send duplicates | Marble | 2026 | |
| Decision | Replace managed object storage with Versity S3 Gateway on one server, backed up by rsync, to stop provider slowdowns | Healthchecks.io | 2026 | One server |
| Decision | Use cloud-based AWS Elemental transcoding paired with a custom packager and custom Live Origin | Netflix | 2025 | Multi-region |
| Decision | Deliver live video over the existing Open Connect CDN shared with on-demand streaming | Netflix | 2025 | Multi-region |
| Decision | Stream live video over HTTPS with 2-second segments and cloud-delivered segment-template manifests | Netflix | 2025 | Multi-region |
| Decision | Validate live changes with internal test streams, synthetic load up to 100K starts/sec, failure injection, and scheduled live practice | Netflix | 2025 | Multi-region |
| Decision | Pair viewership-prediction pre-provisioning with prioritized load shedding and feature degradation | Netflix | 2025 | Multi-region |
| Decision | Replace the monolithic Reloaded video pipeline with microservices on Cosmos and switch over by use case | Netflix | 2023 | |
| Decision | Split video stages by domain boundary while hiding chunked encoding and assembly inside VES | Netflix | 2023 | |
| Decision | Separate member streaming and studio operations into dedicated workflow orchestrators over shared video services | Netflix | 2023 | |
| Decision | Acknowledge archives only after they reach standard S3, not the reduced-redundancy class | Tarsnap | 2023 | |
| Decision | Run the server on one EC2 instance and accept an outage if its hardware fails | Tarsnap | 2023 | |
| Decision | Per-customer SQS queue and Lambda handler replace one shared RabbitMQ queue so slow or heavy customers stop delaying others | Dwolla | 2019 | |
| Decision | Pre-create disabled per-customer resources and toggle the event source mapping instead of creating and deleting them on subscribe | Dwolla | 2019 | |
| Decision | Give every destination its own queue and service so one slow destination cannot delay the rest | Twilio Segment | 2018 | |
| Decision | Split each destination's code into its own repo to isolate test failures | Twilio Segment | 2018 | |
| Decision | Consolidate the over 140 destination services into one service, with Centrifuge planned to replace the queues | Twilio Segment | 2018 | |
| Decision | Merge all destination code into one repo with a single version of every dependency | Twilio Segment | 2018 | |
| Decision | Record and replay destination HTTP traffic in tests so the merged repo's suite is fast and reliable | Twilio Segment | 2018 |
10 more records. Sign in to see all 30.