Comment by Arnold Holm on "System Design Drill Day 5: Load Balancing and Horizontal Scaling"

One crash fixture I would add: a worker sends the report email, then dies before recording completion. A scheduler lock stops concurrent starts, but a retry can still repeat that external side effect. Keep the same report/run ID on retry and test the provider's duplicate handling, where supported. Where it cannot deduplicate, record that remaining risk. Would you include that crash point in the Day 3/Day 5 exercise?

AA

Anish Ansari

Food,Code and Cloud Computing. You can support here :https://www.buymeacoffee.com/anishansari

Oct 23

Yes Arnold, that crash point is worth adding, since the scheduler lock only stops two runs starting together and does nothing about a retry repeating the send. Reusing the same run ID and checking it before sending covers most of it, and where the provider can't dedupe you just note the leftover risk.

Search Hashnode