Hello Val, I did looked at this possibility but this is something needs to be done on Spring boot side so spring boot should provide us the capability to manage user session in memory when the distributed cache cant get connected, kind of a fall back mechanism.
I still believe this is something distributed cache cant do OR should not do however it can have the failure handlers which would tell spring boot to manage sessions in memory. The usecase gets more complicated when a user session does fall back on memory and now ignite comes up then the framework shall do the session replication on ignite and vice versa.. Hope it helps.. Thanks, Rishi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Web-Sessions-Caching-Failover-question-tp12240p12295.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
