Hacker News Reader

Comment by cakes | Hacker News Reader

Multi-tenancy solves some problems around maintenance and upgrade paths that are hugely beneficial when you are managing multiple deployments. If you have even more than just 1 deployment of a thing and scale to 2 (or N), you now also have to manage the software level of those N containers (without multi-tenancy) vs. just 1 deployment for everywhere.

View on HN

> If you have even more than just 1 deployment of a thing and scale to 2 (or N), you now also have to manage the software level of those N containers (without multi-tenancy) vs. just 1 deployment for everywhere.

Sometimes this is a feature. If you're doing managed enterprise SaaS then you frequently need to have different customers running on different releases for whatever reason (maybe one customer has a difficult data migration that has to take place before you can upgrade, maybe another customer has something custom that needs to be upgraded in sync).

Entirely agree. Sometimes it is a feature (and sometimes a curse). Even uptime is a good point for why you couldn't "upgrade everyone" together.

At the same point if I were hosting something for a group of parties (at my own expense/will/etc.) and I want everyone to just be at version X.Y.Z - having to upgrade each deployment itself is definitely a pain.

Not all software needs to be multi-tenant but it also isn't something that is no longer needed or without thought.

Reply on news.ycombinator.com