Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
73 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 |
| 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 |
| Failure | Tarpit rate limiting held sockets open until the load balancers ran out of connection slots and rejected real traffic | Healthchecks.io | 2025 | |
| Decision | Answer rate-limited requests with an immediate HTTP 429 instead of tarpitting them | Healthchecks.io | 2025 | |
| Failure | Connection pools that recycled every 15 minutes synchronized into a thundering herd after a managed Postgres upgrade | Clerk | 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 rate-limit state from MariaDB tables to Redis with per-key TTLs | Let's Encrypt | 2025 | |
| Decision | Replace week-long sliding-window counters with GCRA virtual scheduling | Let's Encrypt | 2025 | |
| Decision | Pause failing zombie clients by tracking consecutive ACME challenge failures per account and domain | Let's Encrypt | 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 |
53 more records. Sign in to see all 73.