---
title: "Comment by Branden Floris on \"System Design Drill Day 15: Real-Time Chat and Live Order Tracking\" | Hashnode"
description: "The seq number plus resync-from-DB approach is the right call, and it quietly makes the pub/sub backplane's at-most-once delivery a non-issue, which a lot of ch"
url: "https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28/comment/6af2ab08085d2a44211e06f6"
---

[Discussion](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28)

Comment [System Design Drill Day 15: Real-Time Chat and Live Order Tracking](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28)

[Branden Floris](https://hashnode.com/@branden991)

[Nov 10](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28/comment/6af2ab08085d2a44211e06f6)

The seq number plus resync-from-DB approach is the right call, and it quietly makes the pub/sub backplane's at-most-once delivery a non-issue, which a lot of chat writeups never explain. One thing I'd add for the reconnect storm: when a WebSocket node dies, all its clients reconnect within a second or two, and they all hit the same after\_seq endpoint at once. Jitter on the client reconnect delay plus the Redis recent-messages cache mentioned above usually covers it. Also good call questioning whether order tracking needs WebSockets at all. Location updates every few seconds with tolerance for a missed one is a great fit for SSE or even polling, and it keeps the stateful connection count reserved for chat where it actually matters.

[Anish Ansari](https://hashnode.com/@anish78)

[Nov 10](https://hashnode.com/posts/system-design-drill-day-15-real-time-chat-and-live-order-tracking/6af182ac97c64d348b044f28/comment/6af2ab08085d2a44211e06f6#reply-6af317ca89a0e7693f62dfcc)

Good point on the reconnect storm, Branden. Random jitter on the client's retry delay plus the recent-messages cache keeps that after\_seq burst from hitting MySQL all at once, and staggering deploys helps in the same way.
