Find people and experiences by name, username, role/title, keyword, or technology tag.
We ran into this around push notifications when the cache went cold. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.
We ran into this around push notifications during a traffic spike. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.
We ran into this around push notifications after we split the monolith. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.
We ran into this around push notifications while rolling back payments. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.
We ran into this around push notifications on a quiet Sunday incident. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.
We ran into this around push notifications after the replica failover. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.
We ran into this around push notifications during a Friday deploy. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.