Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
15 of 486 records match.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| 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 |
| Decision | Self-host Elasticsearch on Kubernetes with the ECK operator instead of using Elastic Cloud | Stack Overflow | 2025 | One site |
| Decision | Load-test the cloud stack in isolated Terraform-built environments matching production before migrating | Stack Overflow | 2025 | One site |
| Decision | Plan to put public assets behind Cloudflare CDN and process its logs in Snowflake, retiring HAProxy logs and TPS | Stack Overflow | 2025 | One site |
| Decision | Package cross-cloud deployments in CNAB containers deployed via Octopus Deploy and GitHub Actions | Stack Overflow | 2025 | One site |
| Decision | Migrate chat history from a single MongoDB replica set to Cassandra once data and index outgrew RAM | Discord | 2017 | Sharded |
| Decision | Bound Cassandra partition sizes with 10-day time buckets and Snowflake clustering keys | Discord | 2017 | Sharded |
| Decision | Delete corrupt edit/delete race rows when author_id is null and omit null columns on Cassandra writes | Discord | 2017 | Sharded |
| Failure | Millions of message tombstones in one channel triggered 10-second Cassandra stop-the-world GC pauses | Discord | 2017 | Sharded |
| Decision | Serve every Q&A site from one multi-tenant application and keep web servers overprovisioned | Stack Overflow | 2016 | Sharded |
| Decision | Use Elasticsearch for search instead of SQL Server full-text search, because SQL CPUs are expensive | Stack Overflow | 2016 | Sharded |
| Decision | Cache in two layers, a web-server HTTP cache and Redis, and clear the first layer through Redis pub/sub | Stack Overflow | 2016 | Sharded |
| Decision | Push updates to browsers over websockets, which are more efficient than polling, at the cost of load balancer port exhaustion | Stack Overflow | 2016 | Sharded |