java不停机部署,Java应用程序的零停机时间部署

I am trying to build the very lightweight solution for zero downtime deployment for Java apps. For the sake of simplicity lets think that we have two servers. My solution is to use:

On the "front" -- some load balancer (software) - I am thinking about HAProxy here.

On the "back" - two servers, both running Tomcat with deployed application.

When we are about to deploy new release

We disable one of the servers with HAProxy, so only one server (let's call it server A, which is running old release) will be available.

Deploy new release on other server (let's call it server B), run production unit tests (in case we have them :-) and enable server B with HAProxy, disabling server A at the same time.

Now we have again only one server active (server B, with the new release). Deploy new release on server B, and re-enable it.

Any advises how to improve? How automate?

Any ready made solutions or do I have to end up with my own custom scripts?

Thanks!

解决方案

Rolling upgrade is indeed a good solution, provided your load-balancer supports this option (server starvation).

Another solution is to use OSGi-enabled application servers, to hot-replace parts or whole of your application.

I would recommend the first one. SpringSource's AMS supervision console can take down a cluster of tcServer (a custom tomcat on steroids), and IIRC do the rolling upgrade automatically (but check the docs).