Optimizing Downtime Management for Integrated CMS and Webstudio Workflows

I think this question appears because you are mixing a webstudio cloud with a non-cloud cms solution.

Cloud handles this stuff for you so you never have a downtime, but you self-host baserow and don't have graceful upgrade system

If you self-host your webstudio site along with your CMS, then your site will also go down along with cms if you have to restart the instance.

In this case its just as bad, but it will seem logical to you 🙂

I would recommend to either lower your expectations or use cloud.

Well or find a way to do graceful upgrades of your cms instance, e.g. starting a new instance on a separate machine, booting it up, then switching over webstudio to the new instance, then killing the old cms instance.

The later is relatively doable if you don't have writes coming from your frontend. If frontend has ability to post things to your database, then after failover you willl need to get the data that was potentially submitted as you were switching over.

Building clouds that are never offline is a complex task.

Yes I know Cloud handles this for me.

I see, I will need to learn how to do a graceful upgrade.

Yes it's logical. Just curious what options I have in this. Whether I learn graceful upgrades and/or use something like "Always Online" from cloudflare.

Cloud is not really an option, at least when it comes down to Baserow and it's API limitations for their cloud.

I understand that building clouds that go never offline is a complex task, that's where certain network engineers come in I guess!

You could probably just also minimize downtime to a few minutes