Another complementary piece of functionality is the ability to provide session persistence to a web application. This is normally provided by the application container but typically has replication or scalability issues with large deployments. This problem tends to be addressed through the use of sticky sessions, where a load balancer sits in front of the application route-related traffic to the same container, but what would happen in a failure situation? If the container does not feature any form of replication, the session will be lost and a negative customer experience will be encountered.

Hazelcast can help address this issue by providing an external and distributed session store for our application. By including hazelcast-wm-3.5.jar in our web application and configuring the web.xml file, we can provide session persistence by using a web application filter. In the case that your application uses multiple filters, make sure that this is the first filter defined within...