Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
81 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Failure | Daily peak event burst saturated shared database primary, and with no automatic circuit breaker the throttling was manual | GitHub | 2026 | |
| Failure | Brief pod reduction during routine rollout saturated remaining sites, OOMed service-mesh sidecars, and triggered invalid-job runner retries | 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 | |
| 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 | Rebuild fragmented async systems incrementally in phases instead of writing a replacement from scratch | Dropbox | 2025 | |
| Decision | Standardize ingestion, ordering, delayed scheduling, and dynamic flow control into separate MSM layers | Dropbox | 2025 | |
| Decision | Use health-aware push routing and Atlas-backed SOA lambdas for autoscaling and automated release rollbacks | Dropbox | 2025 | |
| Decision | Batch ping writes with COPY in one transaction instead of calling a stored procedure once per ping | Healthchecks.io | 2025 | One database |
| Decision | Cache not-found results for UUID ping URLs so repeated pings to missing checks skip the database | Healthchecks.io | 2025 | One database |
| Decision | Replace sequential monolithic RepositoryPushJob with a Kafka topic fanning out to isolated per-owner background jobs | GitHub | 2024 | |
| Decision | Use consistent per-event feature flagging to cut over push processing without data loss or double processing | GitHub | 2024 | |
| Failure | Recurring incidents where errors on the Pushes MySQL cluster early in RepositoryPushJob kept unrelated pull requests from synchronizing | GitHub | 2024 | |
| Failure | A surge of duplicate webhooks and the retry setup filled one queue's provider quota, so new events were not delivered for hours | Onfido | 2024 | |
| Decision | Moved jobs from Resque on Redis to a database-backed queue, starting with the most critical ones | 37signals | 2023 |
61 more records. Sign in to see all 81.