On Oct 17, 2008, at 11:06 AM, Edward Capriolo wrote:
Very interesting. If those classes implement serialization
Even if they don't (I don't remember one way or another), it would be trivial to implement it.
they can be used with tomcat session replication?
I'm not sure that I see how *session* replication can be used to replicate a *shared* (across multiple users) resource.
Also, consider that database can be modified on different nodes at once by different web site visitors. Say, one user will add a document and another user will delete some other document. After these changes are made, how you are going to synchronize state of these databases?
That's why I suggested building a replication layer on top. Instead of trying to replicate complete database (which will be costly if database size is anything but trivial), you'd replicate only modifications.
I am also looking into http://www.jgroups.org/. My goal is to have some type of database that can scale on the fly.
Yes, jgroups can be employed to build communication for the replication layer.
Vadim
