Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
16 of 486 records match.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Decision | Replace managed object storage with Versity S3 Gateway on one server, backed up by rsync, to stop provider slowdowns | Healthchecks.io | 2026 | One server |
| Decision | Build an S3 and Spark data lake for update-heavy block data while keeping Snowflake and Fivetran for simpler workloads | Notion | 2024 | Sharded |
| Decision | Use Debezium-to-Kafka incremental CDC with one topic per table and RDS export-to-S3 only for bootstrapping | Notion | 2024 | Sharded |
| Decision | Choose Apache Hudi over Iceberg and Delta Lake and align S3 partitioning with Postgres's 480 shards | Notion | 2024 | Sharded |
| Decision | Land raw CDC data in S3 before processing and handle skewed shards differently in Scala Spark | Notion | 2024 | Sharded |
| Decision | Replace ad-hoc multi-hop legacy pipelines with one open-source Kafka and Flink platform | DoorDash | 2022 | Sharded |
| Decision | Put a customized async Confluent Kafka Rest Proxy in front of Kafka instead of direct clients in every service | DoorDash | 2022 | Sharded |
| Decision | Use replication factor 2, leader-only acknowledgments and 50ms to 100ms linger for non-transactional events | DoorDash | 2022 | Sharded |
| Decision | Register Protobuf event schemas in Confluent Schema Registry at build time in CI/CD instead of at runtime | DoorDash | 2022 | Sharded |
| Decision | Stage Kafka events to S3 Parquet via per-event Flink jobs before loading Snowflake with Snowpipe | DoorDash | 2022 | Sharded |
| Decision | Automate multi-repo Terraform event onboarding with a GitHub App, Cadence workflows and Retool UIs | DoorDash | 2022 | Sharded |
| Decision | Automate ZooKeeper replacement with ZooKeeper 3.6, Consul KV node IDs, and Terraform Auto Scaling Groups | Slack | 2022 | Sharded |
| Decision | Prevent Kafka broker hot-spotting with broker-multiple partition counts, throttled small-batch rebalances, and Cruise Control | Slack | 2022 | Sharded |
| Decision | Give each Kafka cluster its own dedicated ZooKeeper cluster to limit coordination blast radius | Slack | 2022 | Sharded |
| Decision | Upgrade Kafka by cutting over to a dark-traffic-validated cluster instead of upgrading in place | Slack | 2022 | Sharded |
| Decision | Split three of the largest topics off a saturated 90-broker cluster onto smaller dedicated Nitro d3en clusters | Slack | 2022 | Sharded |