Open JLDLaughlin opened 2 years ago
Downtime is bad! And not a thing we want our users to suffer through. In the ideal world, Materialize Cloud would upgrade behind the scenes without a single user noticing.
Once https://github.com/MaterializeInc/materialize/issues/13040 and https://github.com/MaterializeInc/cloud/issues/3456 are completed, we should continue to improve our version upgrade tooling to avoid any downtime. (Some ideas for this found here.)
This comment describes the approach discussed so far: https://github.com/MaterializeInc/cloud/issues/2471#issuecomment-1128434562
What's wrong
Downtime is bad! And not a thing we want our users to suffer through. In the ideal world, Materialize Cloud would upgrade behind the scenes without a single user noticing.
What should we do
Once https://github.com/MaterializeInc/materialize/issues/13040 and https://github.com/MaterializeInc/cloud/issues/3456 are completed, we should continue to improve our version upgrade tooling to avoid any downtime. (Some ideas for this found here.)