---
title: "Comment by Mahdi Jabinpour on \"System Design Drill Day 5: Load Balancing and Horizontal Scaling\" | Hashnode"
description: "The rolling-deploy exercise would be even stronger with a checkout running while old and new application versions overlap. Database compatibility is one boundar"
url: "https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924/comment/6add1206838a42a2d61b83ef"
---

[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)

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

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

The rolling-deploy exercise would be even stronger with a checkout running while old and new application versions overlap. Database compatibility is one boundary; session payloads and queued-job formats are two more. Testing that mixed-version window makes “any server can handle any request” a property of the release process as well as the steady state.

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

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

Agreed Mahdi, the article only covers backward-compatible migrations, but session payloads and queued jobs cross that old and new window too. Running a real checkout through a half-rolled deploy is a nice way to prove it.
