Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
23 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Decision | Own the webhook pipeline after customers could not see what happened to a webhook, leaving a hosted queue | Marble | 2026 | |
| Decision | Workers atomically claim a delivery before sending so overlapping workers or retried queue messages do not send duplicates | Marble | 2026 | |
| Decision | Deploy unicast PTPv2 with custom Go server ptp4u, PPS-disciplined NICs, and switch transparent clocks | Meta | 2022 | Multi-region |
| Decision | Expose TAI time as a 6-9s Window of Uncertainty via fbclock with parallel linearizability cross-checks | Meta | 2022 | Multi-region |
| Decision | Add client-side Priority3 tiebreaking to ptp4l BMCA so clients distribute load across identical Time Appliances | Meta | 2022 | Multi-region |
| Decision | Adopt Openark Orchestrator for automated MySQL primary failover across GTID and non-GTID clusters | 2022 | ||
| Decision | Measure absolute replication lag with heartbeat writes and guard promotions with FailMasterpromotionOnLagMinutes | 2022 | ||
| Decision | Register each cluster's dedicated backup/ETL replica as a prefer failover candidate rather than Must | 2022 | ||
| Decision | Throttle Orchestrator failovers within a two-minute window via a pre-failover hook, skipped during maintenance | 2022 | ||
| Decision | Keep performance- and latency-critical core and edge workloads on-prem while using public cloud for burst, DevOps and analytics | Roblox | 2021 | |
| Decision | Per-customer SQS queue and Lambda handler replace one shared RabbitMQ queue so slow or heavy customers stop delaying others | Dwolla | 2019 | |
| Decision | Pre-create disabled per-customer resources and toggle the event source mapping instead of creating and deleting them on subscribe | Dwolla | 2019 | |
| Decision | Give every destination its own queue and service so one slow destination cannot delay the rest | Twilio Segment | 2018 | |
| Decision | Split each destination's code into its own repo to isolate test failures | Twilio Segment | 2018 | |
| Decision | Consolidate the over 140 destination services into one service, with Centrifuge planned to replace the queues | Twilio Segment | 2018 | |
| Decision | Merge all destination code into one repo with a single version of every dependency | Twilio Segment | 2018 | |
| Decision | Record and replay destination HTTP traffic in tests so the merged repo's suite is fast and reliable | Twilio Segment | 2018 | |
| Decision | One reader per shard replaces one reader thread per customer webhook after delays reached 10 minutes | Nylas | 2018 | Sharded |
| Decision | Kinesis chosen over the MySQL binlog and Kafka as the ordered source of changes, mainly for operational simplicity | Nylas | 2018 | Sharded |
| Decision | New sender ran two months in a simulated mode that sent nothing, compared against the legacy sender, before cutover | Nylas | 2018 | Sharded |
3 more records. Sign in to see all 23.