---
title: "Comment by Abhinav Sharma on \"System Design Drill Day 5: Load Balancing and Horizontal Scaling\" | Hashnode"
description: "The readiness-vs-liveness split is the detail most first-time setups get wrong: folding Redis into readiness means one cache blip pulls every server out of rota"
url: "https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924/comment/6adaf85b48ac65c800153b4f"
---

[Discussion](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924)

Comment [System Design Drill Day 5: Load Balancing and Horizontal Scaling](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 23](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924/comment/6adaf85b48ac65c800153b4f)

The readiness-vs-liveness split is the detail most first-time setups get wrong: folding Redis into readiness means one cache blip pulls every server out of rotation at once. The duplicate report email is the other classic: a scheduled job needs a single owner the moment more than one box exists.

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

[Oct 23](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924/comment/6adaf85b48ac65c800153b4f#reply-6adb0a338c60127c2817e582)

Thanks Abhinav, keeping Redis out of readiness is exactly what stops one cache blip from emptying the whole pool. And the duplicate report email is the bug that only shows up the day you add a second server 🙂