Andy I was talking to some folks at a major bank the other day about TDB and got an interesting question that I didn't have an answer to. Essentially they were interested in learning how you would provide replication and hot-standy with TDB
For current generation TDB I told them that people typically place a Load Balancer in front on multiple TDB instances for read-centric workloads and manually handle replicating updates to all systems (usually be temporarily disabling the services, applying the updates and restarting) However for Lizard and TDB 2 I did not really know what the answer would be? Lizard is obviously designed as a fault-tolerant system but I don't know if the same can be said for TDB 2 (which I understand more to be about changing the on-disk data structures) For bonus points they were also interested in whether Lizard/TDB 2 would offer customisable replication policies? For example they would like to be able to configure some replicas to be read-only while having others be read/write? Rob
