I am investigating the ins and outs of a system that consists of several JVMs running on possibly separate machines all manipulating separate instances of Derby that collectively are kept in synch - somehow. Does anyone know of a possible solution to the synchronisation side of things or am I dreaming? I am not sure if HA-JDBC or Daffodil Replicator can handle the inter-machine communication issues.
-JCT > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Van Couvering > Sent: Wednesday, 19 September 2007 03:17 > To: Derby Discussion > Subject: Re: Derby and replication > > 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 > synch. > > 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. > > David > > On 9/18/07, ad marginem <[EMAIL PROTECTED]> 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! > > > > > > -- > > по краям
