Given
I run multiple application servers running optionally behind a load balancer. The application servers share a single SQL Db. Pretty conventional setup I think.
Imagine a sw upgrade package is made available for the app. The upgrade includes changes both to the app and to the Db schema.
Problem
An admin starts installing the upgrade on the first application server. This results the app server and the Db schema to be updated to the new version.
Once the Db update is running, the remaining app servers should somehow be notified they should stop using the Db until they receive the upgrade. I wonder are there known solutions to that?
Technology in use
- Application servers: Linux daemons running behind lighttpd-1.4.35 on Ubuntu 16
- Db: MySQL-5.7 on top of Ubuntu 16
- Load balancer: not decided on it yet (suggestions are welcome)