Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
169 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 | 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 | |
| Failure | NOTIFY inside transactions serialized all commits globally on Postgres, causing three downtimes | Recall.ai | 2025 | |
| Decision | Replace Postgres LISTEN/NOTIFY with application-layer tracking for bot configuration updates | Recall.ai | 2025 | |
| Decision | Build a minimal backup banking stack with separate software on GCP instead of replicating Primary | Monzo | 2025 | Multi-region |
| Decision | Sync minimal immutable state asynchronously to Stand-in and replay Stand-in outcomes as verbatim Advices | Monzo | 2025 | Multi-region |
| Decision | Deduplicate Stand-in and re-synced Primary transactions using a shared Correlation ID | Monzo | 2025 | Multi-region |
| Decision | Coordinate failover with dual Configuration services and manual disable for gradual app rollback | Monzo | 2025 | Multi-region |
| Decision | Proxy payments via Primary by default with direct data-centre fallback, testing both continuously in production | Monzo | 2025 | Multi-region |
| 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 | Move the public sites from bare-metal data centers to Kubernetes in one GCP region, using Windows Kubernetes for legacy .NET apps | Stack Overflow | 2025 | One site |
| Decision | Run SQL Server on dedicated high-memory GCP VMs with half the CPU cores disabled instead of managed cloud SQL | Stack Overflow | 2025 | One site |
| Decision | Use GCP MemoryStore for Redis with key prefixes instead of self-hosting Redis on Kubernetes | Stack Overflow | 2025 | One site |
149 more records. Sign in to see all 169.