db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering" <da...@vancouvering.com>
Subject Re: Derby and replication
Date Tue, 18 Sep 2007 17:17:18 GMT
I think the responses you have heard so far talk about replication to
provide availability (HA-JDBC, the ongoing Derby effort).

What you are talking about is basically using Derby as a reliable
front-end cache to a back-end database where the connection can be
unavailable from time to time.

What this is about is really synchronization, not replication.
Synchronization is keeping two sometimes disconnected databases in

One product out there that works with Derby is Daffodil Replicator,
see http://sourceforge.net/projects/daffodilreplica/.  It's an open
source project using the GPL license.


On 9/18/07, ad marginem <admarginem@gmail.com> wrote:
> Hello,
> I want to develop a program, using derby as a back-end.
> There will be a POS and a Warehouse module. They will use the same database
> scheme, but they cannot use the same database because of reliability (in
> case of broken connection the POS must not stop).
> So my question is: how to develop such a reliable workflow? Replication? Or
> maybe there are some other options? If replication - how to implement it?
> Are there any existing methods to replicate derby database?
> Thank you!
> --
> по краям
View raw message