Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
22 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| 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 | Upgrade Aurora Postgres v10 to v13 via copy-on-write cloning and native logical replication instead of pg_upgrade or DMS | Lyft | 2023 | One database |
| Decision | Halt cutover writes with an Envoy circuit breaker and read-only source DB, and repoint via Route53 DNS | Lyft | 2023 | One database |
| Decision | Split the ad server out of the Read the Docs app and tune Django query by query instead of rewriting it | EthicalAds | 2021 | One database |
| Decision | Choose ad server hosting by load test, picking Azure AppService over Heroku for predictable latency | EthicalAds | 2021 | One database |
| Failure | A viral customer's pageviews backlog the shared queue for all sites while the database runs out of disk IOPS | Fathom Analytics | 2020 | One database |
| Failure | Unindexed backlog tables and a text-typed site ID kept the database slow after the disk was fixed | Fathom Analytics | 2020 | One database |
| Decision | Cap concurrent queue workers on purpose to protect the database, accepting a bigger backlog | Fathom Analytics | 2020 | One database |
| Decision | Limit pageviews processed per site per minute so one viral site cannot block the rest, then drop it | Fathom Analytics | 2020 | One database |
| Decision | Run the whole certificate authority against one database and scale the hardware instead of sharding | Let's Encrypt | 2020 | One database |
| Decision | Replace the database servers with two-CPU EPYC machines holding 24 NVMe drives under OpenZFS | Let's Encrypt | 2020 | One database |
| Decision | Run plain dedicated servers, one role each, with no containers, autoscaling or serverless | Healthchecks.io | 2019 | One database |
| Decision | Fail over the PostgreSQL primary to its hot standby by hand, using a tested procedure | Healthchecks.io | 2019 | One database |
| Decision | Replace Cloudflare's load balancer with two self-run HAProxy machines | Healthchecks.io | 2019 | One database |
| Decision | Drop a dedicated private switch and second network cards for Hetzner's vSwitch | Healthchecks.io | 2019 | One database |
| Failure | Rebuilding a lagging replica by hand ended with the primary's data directory being wiped | GitLab | 2017 | One database |
| Failure | Daily pg_dump backups had been silently failing, and Azure disk snapshots were not enabled on the database servers | GitLab | 2017 | One database |
| Decision | Restore from a staging copy of the six-hour-old manual snapshot, not the 24-hour-old one | GitLab | 2017 | One database |
| Decision | Spend the effort on recoverability and on making the host obvious, not on blocking dangerous commands | GitLab | 2017 | One database |
2 more records. Sign in to see all 22.