Replication

Hi,

we are using prevayler 2.02.006 for 5 years now without problems.

An new requirement is replication and automatic fail-over to an backup
server if the primary one gets unreachable. Could you tell us your
opinion for the best solution?

1) Upgrade to Version 2.3
There is an unfinished replication implementation. It seems to be
removed in the latest git version. Can you tell me the reason why? Do
you know anybody using this code?

2) A own implementation witch sends every incoming transaction to an
queue. A background threads sends all elements from the queue to
another server instance.

3) A filesystem approach sending new journal entrys to the other server.

We need an async approach because there are a lot of transactions
which need to be as fast as possible processed. It is no problem if
some few transactions get lost if the primary server gets unreachable.

Also there is no need for automatic resync from backup to the master server.

For approach 2) and 3) it is not needed to update to version 2.3. It
is practical to upgrade our code? We have no problems and don't need
any new feature expect replication.

I think 2) is the easiest way to implement replication for us. If you
have any ideas or suggestions please let me know.

Thank you
Dennis Rieks

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org