---
title: "Comment by Mihai_LeanZero on \"Architecture Case Study: Migrating a Developer SaaS from Serverless to a $10 VPS with Docker\" | Hashnode"
description: "The highest-numbered-container detail checks out -- checked the current docker/compose scale-down code and it explicitly orders containers so a scale-down trims"
url: "https://hashnode.com/posts/architecture-case-study-migrating-a-developer-saas-from-serverless-to-a-10-vps-with-docker/6abf646f1308726bbb4b9cd5/comment/6abf89b3d62e6e07297c10c6"
---

[Discussion](https://hashnode.com/posts/architecture-case-study-migrating-a-developer-saas-from-serverless-to-a-10-vps-with-docker/6abf646f1308726bbb4b9cd5)

Comment [Architecture Case Study: Migrating a Developer SaaS from Serverless to a $10 VPS with Docker](https://hashnode.com/posts/architecture-case-study-migrating-a-developer-saas-from-serverless-to-a-10-vps-with-docker/6abf646f1308726bbb4b9cd5)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Oct 2](https://hashnode.com/posts/architecture-case-study-migrating-a-developer-saas-from-serverless-to-a-10-vps-with-docker/6abf646f1308726bbb4b9cd5/comment/6abf89b3d62e6e07297c10c6)

The highest-numbered-container detail checks out -- checked the current docker/compose scale-down code and it explicitly orders containers so a scale-down trims the highest replica numbers first and keeps the lowest one running. So web=2 back to web=1 does remove the newer container and keep the older one, exactly as described. What the fixed-name web-blue/web-green setup buys you over --scale is not depending on that ordering holding: it's current implementation behavior, not a documented contract, so a future Compose release could change the tie-break without calling it a breaking change. Naming the slots explicitly makes the swap correct regardless of how Compose orders replicas internally.

[ZyVOP](https://hashnode.com/@zyvop)

[Oct 2](https://hashnode.com/posts/architecture-case-study-migrating-a-developer-saas-from-serverless-to-a-10-vps-with-docker/6abf646f1308726bbb4b9cd5/comment/6abf89b3d62e6e07297c10c6#reply-6abf8f3e535d6c1802c1766f)

Yep, exactly. `--scale` works today, but the blue/green naming avoids depending on an internal ordering detail that Compose could change later. That’s the main reason I prefer the explicit slots here. Good point.
