Hi Gabor
I'm late to the thread.
Gf comes with Shoal libraries and given that your requirements are
pretty lightweight you could consider using Shoal's shared cache
implementation wherein your instances can join a named group and put
shareable data into this shared cache. The data will now be available
in both your instances. Before you call your JPA API for reads you ask
the shared cache for passing in the key. You will have to take care of
removing expired authenticated sessions.
Let me know if this interests you and I can send you more details.
Shreedhar
Sent from my iPhone
On Jan 27, 2008, at 1:18 PM, Gabor Szokoli <szocske_at_gmail.com> wrote:
> I'd like to thank everyone for the ideas.
>
> Glassfish with toplink and postgres (with another database in it) are
> already present, so I don't consider them as overhead. The project
> already uses JPA, so I'd prefer not to have two kinds of persistence
> architectures.
>
> The problem is that I need the data replicated between two nodes.
>
> h2 clustering looks interesting, if I can automate the recovery.
>
> ha-jdbc seems to have that aspect covered too, so that's my prime
> candidate right now.
>
> I tried to figure out which postgresql multimaster replication
> projects are still alive but already stable, but an RDBMS-agnostic
> solution is always preferred anyway.
>
>
> Thanks again everyone!
>
> Gabor
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>