4 ms·
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 ou
by ccleve 6y ago
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.
- hinkley 6y agoIt 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.