Hi Ad Marginem
There is an ongoing effort to add replication to Derby that we hope will
be ready for the next major Derby release. The currently planned
functionality will add replication for availability improvement only,
and reading/updating the "back-end" database will not be allowed.
However, if more developers took part in this issue, the scope could be
widened to, e.g., allow "back-end" reads.
A "new feature" request has already been filed for replication in
Derby's bug tracker here:
https://issues.apache.org/jira/browse/DERBY-2872. You are more than
welcome to participate in the development of this (and other) Derby
issues. As a starting point, you could have a look at the functional
specification posted on the issue mentioned above and post any comments
you might have.
Jørgen Løland
ad marginem 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!
