Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
154 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Failure | Traffic peak overloaded one datacenter's load balancers while a service-mesh sidecar failed to scale, and a client retry bug amplified authentication traffic | GitHub | 2026 | Multi-region |
| 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 customer-owned social-graph ingestion pipelines with a self-managed data warehouse ingestion service | Meta | 2026 | |
| Decision | Migrate jobs through three gated phases—shadow, reverse shadow and cleanup—verified on row counts, checksums, latency and resources | Meta | 2026 | |
| Decision | Contain CDC bad-data propagation via paired reverse-shadow backfills and metadata bad-partition flags | Meta | 2026 | |
| Decision | Batch shadow migrations under limited capacity, holding back jobs with known bugs and reusing legacy snapshots | Meta | 2026 | |
| Decision | Automate lifecycle promotion from Scuba signals and run hourly mismatch row-level debugging | Meta | 2026 | |
| Failure | Connection pools that recycled every 15 minutes synchronized into a thundering herd after a managed Postgres upgrade | Clerk | 2025 | |
| Failure | One customer's endpoint outage made deliveries time out, filled the shared worker pool and delayed Directory Sync webhooks for everyone | WorkOS | 2025 | |
| Decision | Split feature engineering into distributed PySpark pre-processing on Databricks and vertical Python transformations on SageMaker | Zalando | 2025 | |
| Decision | Use LightGBM with Nixtla MLForecast to combine demand forecast training and inference in one SageMaker job | Zalando | 2025 | |
| Decision | Use dual offline and online SageMaker Feature Store tiers and write interactive updates back to the offline store | Zalando | 2025 | |
| Decision | Serve interactive partner inventory-setting updates asynchronously through SQS, Lambda and event-stream notifications | Zalando | 2025 | |
| Decision | Isolate every pipeline run on dedicated transient Databricks job clusters and SageMaker jobs via zFlow | Zalando | 2025 | |
| Decision | Move ad tracking metadata out of client opaque tokens into a transient key-value Ads Metadata Registry | Netflix | 2025 | |
| Decision | Centralize ad event ingestion behind Ads Event Publisher with a unified contract and place all consumers and sessionization downstream | Netflix | 2025 | |
| Decision | Combine real-time Flink-to-Druid ad metrics with offline correction and separate offline billing workflows | Netflix | 2025 | |
| Failure | Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them | Bluesky | 2025 | Sharded |
| Decision | Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines | Bluesky | 2025 | Sharded |
134 more records. Sign in to see all 154.