Ochan

I’ve just started thinking through some replication strategies.. to make up for berkeleydb java edition not having it. Ochan still needs high availability.. and I think I’ve figured out a way for in-place replication…

I wont release it until I have auto-regeneration scripts to show it off.

Example:

Web tiers A, B, and C

connected to Backends X and Z… with a hot spare server named ‘Joe’.

And a sync system S.

If X fails, Joe should become the new X. But, also, Joe should be able to be either X or Z.. (so, it should be unsharded). And Joe can be a backup for S as well.

We already have HA in the web tier; A,B, and C can fail and no one cares. But, having a replication group is kinda useless unless ‘something’ can identify the new middle tier replacing the failed one, and reconfiguring the webtier to start calling it.