AAGood call on the stale prices. Adding a line like "prices may have changed, final price is confirmed at checkout" to the limited search notice would make that MySQL check feel expected instead of surprising.Reply·Article·2d ago·System Design Drill Day 16: Product Search, Ranking and Typeahead
AAThat stale price case is exactly why price and stock get their own fast lane, since a late bulk import is annoying but a wrong price at checkout costs trust. Glad the typeahead numbers felt realistic too, precomputing hourly is what keeps each keystroke cheap.Reply·Article·4d ago·System Design Drill Day 16: Product Search, Ranking and Typeahead
AATrue, a clean runbook link beats one more dashboard every time. Thanks for keeping this thread going, Rishabh, it's been a fun one.Reply·Article·6d ago·System Design Drill Day 5: Load Balancing and Horizontal Scaling
AASame here, Rishabh. When the runbook link is sitting right in the ticket, the first few minutes go into fixing things instead of figuring out where to start.Reply·Article·Nov 13·System Design Drill Day 5: Load Balancing and Horizontal Scaling
AALinking the runbook from the ticket is a great habit, Rishabh. Whoever picks it up at 2 AM gets the fix steps right there instead of digging for them.Reply·Article·Nov 13·System Design Drill Day 5: Load Balancing and Horizontal Scaling
AANice one Rishabh, putting the check name and endpoint in the ticket title saves whoever picks it up a trip through the logs. The review date is a good touch too, otherwise those tickets just sit there forever.Reply·Article·Nov 12·System Design Drill Day 5: Load Balancing and Horizontal Scaling
AAGood fixture to add. If the status check itself times out, keeping the send in that uncertain state with the original provider reference means the next retry is a deliberate call instead of a quiet rejection.Reply·Article·Nov 11·System Design Drill Day 13: Designing a Multi-Channel Notification System
AAGlad the save first, broadcast second rule clicked for you. Once the socket is just a notification layer, offline delivery stays simple, and pairing the unconditional resync with Parsa's recent messages cache is a nice way to soften that reconnect spike.Reply·Article·Nov 11·System Design Drill Day 15: Real-Time Chat and Live Order Tracking
AAGood call. Having the last green run right there in the ticket gives whoever picks it up a clear starting point for what changed since then.Reply·Article·Nov 11·System Design Drill Day 5: Load Balancing and Horizontal Scaling
AAGood 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.Reply·Article·Nov 10·System Design Drill Day 15: Real-Time Chat and Live Order Tracking