Martin Grotzke wrote:
Tomcat sounds like such a pisser :P Even with your backup thing I'd
probably still add an option to allow it to journal to a database, and I
say this knowing how to get every last ounce of efficiency out of
memcached.
Tomcat provides a PersistentManager ([1]) which allows to store sessions
in the database. But this manager backups all sessions in batches every
10 seconds. For one thing scalability of the application is then
directly dependent from the database (more than it is already if a
database is used) and there's a timeframe where sessions can be lost. If
the session backup frequency is shortened, the database is hit more
often. Additionally sessions are stored in the database again and again
even if they were not changed at all. That was the reason why I decided
not to use this.
What about tomcat's ClusterManager? Doesn't that provide replication across
server instances?
--
Les Mikesell
[email protected]
