Catalogue

Cards
165
Records
486
Workloads
19
Corpus version
74847648e25a
Workload
Kind
Setup

14 of 486 records match.

KindRecordOrganisationYearSetup
Decision

Upgrade Aurora Postgres v10 to v13 via copy-on-write cloning and native logical replication instead of pg_upgrade or DMS

lyft-2023-aurora-postgres-upgrade#d1

Lyft2023One database
Decision

Halt cutover writes with an Envoy circuit breaker and read-only source DB, and repoint via Route53 DNS

lyft-2023-aurora-postgres-upgrade#d2

Lyft2023One 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-ad-server#d1peak under 100 requests/s

EthicalAds2021One database
Decision

Choose ad server hosting by load test, picking Azure AppService over Heroku for predictable latency

ethicalads-2021-ad-server#d2peak under 100 requests/s

EthicalAds2021One database
Decision

Run the whole certificate authority against one database and scale the hardware instead of sharding

letsencrypt-2020-database-servers#d1

Let's Encrypt2020One database
Decision

Replace the database servers with two-CPU EPYC machines holding 24 NVMe drives under OpenZFS

letsencrypt-2020-database-servers#d2

Let's Encrypt2020One database
Decision

Run plain dedicated servers, one role each, with no containers, autoscaling or serverless

healthchecks-2019-hosting-setup#d1

Healthchecks.io2019One database
Decision

Fail over the PostgreSQL primary to its hot standby by hand, using a tested procedure

healthchecks-2019-hosting-setup#d2

Healthchecks.io2019One database
Decision

Replace Cloudflare's load balancer with two self-run HAProxy machines

healthchecks-2019-hosting-setup#d3

Healthchecks.io2019One database
Decision

Drop a dedicated private switch and second network cards for Hetzner's vSwitch

healthchecks-2019-hosting-setup#d4

Healthchecks.io2019One database
Failure

Rebuilding a lagging replica by hand ended with the primary's data directory being wiped

gitlab-2017-database-outage#f1

GitLab2017One database
Failure

Daily pg_dump backups had been silently failing, and Azure disk snapshots were not enabled on the database servers

gitlab-2017-database-outage#f2

GitLab2017One database
Decision

Restore from a staging copy of the six-hour-old manual snapshot, not the 24-hour-old one

gitlab-2017-database-outage#d1

GitLab2017One database
Decision

Spend the effort on recoverability and on making the host obvious, not on blocking dangerous commands

gitlab-2017-database-outage#d2

GitLab2017One database