Best practice deploying new version or restarting server

1
0

Is there any best practice for deploying a new version of our app or restarting the server? Now if we deploy, every user is basically kicked and needs to restart the app. This could be very annoying.

One idea would be to show a notification to all online users that they need to save whatever they are doing and the prevent them from any editing. Then after some time we can deploy the new version and kick everybody. Same procedure if we need to restart the server. Using a load balancer, we could prevent new sessions on the specific server. This could be done using the health check.

I know this would be very complex but is there any option to move user states between servers?

Questions
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

Hi Bernhard,

here my solution: https://wisej.com/support/question/multiple-project

then the users use the old project without restart, until the next reopening

best

Cristian Zerbinati

  • Bernhard Lang
    Hi Cristian, we had the same Idea. At the moment we try to bring this even further. If it is fine for my company I might share some code in the future. We have some kind of shell application. But beside that we split our app in many sub-applications. When we need to update we only replace the sub-application. Users using the sub-application get a grace period where they can save their changes. Users trying to launch the sub-application get an “application in maintenance”-message. The other sub-applications are still available. After the grace period we close the control for all users. Then we switch to the new sub-application, eventually running some database migrations and then users can use the sub-application again. We also have some OData services in the same project. Therefor we also need to update them. Best regards Bernhard
  • You must to post comments
0
0

When you replace an assembly the web server restarts. It’s not our web server and there is no way around it.

There are several ways to “gracefully” kick out users but they are all part of the application’s architecture and outside of Wisej’s scope.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.