I'm curious to see how other developers are involved in versioning web applications and deploying different versions. The main problem is that someone can use your web application when deploying the new version, and at that point Javascript, etc. They have no client side, are outdated.
The client side version of the environment is quite simple, but if you use the version, you will also need to update your business logic and database, in which everything can become messy ...
So, I see a couple of ways to handle this:
Display an update notification on the site when you deploy the new version.
Version of the tag on the client side and reject any submission to the new version from old client sources. Fair enough, but in reality it does not go hand in hand with continuous deployment.
Continuous database migration - simultaneous work with several versions of the application (when possible, transferring users to the new version). This will require any updates to the old database schema, which will be transferred to the new schema. Seems most attractive for deployment, but can also be terribly complex.
Somewhere in the middle of all three.
I should point out that I know that worrying about these kinds of things does not fit the needs of most applications, but I thought about it and am curious to see how others deal with this.
Allan jardine
source share