Browser-side failover implementation. If the connection to the primary server is lost, the browser will automatically redirect itself to a fallback/spare server of your choosing.
- No single point of failure
- Incredibly easy setup - just add Maven dependency on this add-on and recompile your widgetset.
- No server-side clustering needed
- Servers are totally independent one from another - you may even use a mixture of server kinds, different versions of application, ...
- Session is lost on failover
- If the main server dies, new clients cannot connect.
- If the main server dies and the user presses F5 in the browser, she will just get "Connection Refused". This could perhaps be remedied by offline mode.
- Supports multiple fallback servers to reconnect to, either in round-robin or random-robin.
- Prior reconnecting the URL is pinged first, whether the spare server is actually alive.
- A simple load-balancer, by selecting a random server from the list instead of always choosing the primary one.
- The user must initiate the failover process manually. This way she will understand that the server has crashed and that she may lose some data (that is, the session).
- Offline mode of the bootstrap page, which will connect to the spare server even in case when the primary server is down.
For tutorial, please see homepage