Moving from a traditional in memory Java session to persistent storage sessions

Posted by Benju on Programmers See other posts from Programmers or by Benju
Published on 2012-06-20T19:07:11Z Indexed on 2012/06/20 21:23 UTC
Read the original article Hit count: 199

Filed under:
|
|

We have decided to take the plunge and move from using a typical java session provider in Tomcat/Jetty/etc to persisting everything to a central datastore.

We are looking at using MongoDB for this. A few options come to mind...

http://wiki.eclipse.org/Jetty/Tutorial/MongoDB_Session_Clustering

This is nice because it will "auto-magically" persist our session to a Mongo installation. I am concerned however that we will not have fine grained control of what is happening.

https://github.com/mattinsler/com.lowereast.guiceymongo/

GuiceMongo is interesting as it integrates with Guice. Perhaps we could persist everything via this ORM.

Has anybody had to deal with this kind of move? It seems that moving from in memory to persistent session storage has a lot of gotchas.

© Programmers or respective owner

Related posts about persistence

Related posts about mongodb