Re:Multi-Tenant Architectures
by ccleve on Sunday August 30, 2020 @06:48PM
(#24326654)
This works and solves a lot of problems. The downside is that schema changes are cumbersome because you have to make them in many places. If you want to roll out a new feature in a shared app which depends on a schema change, it's hard to do without downtime or complicated feature flags.
[ Parent
| on HN ]
It seems like some continuous deployment strategies could work here, as long as you limit the number of schema changes in flight to a handful.
Customer A is running the new schema, so gets one cluster. Customer Z will get migrated in the next hour, and then none of the old system is running.