|
Hi all, I'm new to the list and to sequoia, and so I'm trying to understand and realize the capabilities of this product. We are trying to find a database architecture as the backend for our Java apps, with the only requisite of four nine availability (99,99). The load will always be low. My view is from the infrastructure point (I know that I should pass this problem to our dev part, I've done it indeed...), and that's why I want to build a base platform for deploying different client solutions in our virtualized datacenter: My needs should be just two backend databases ("mirrored" ideally) controlled by two controllers replicating everything. I was looking at Sequoia+Postgre as the platform, and have been reading all the documentation it seems to fit well. I have some doubts: 1) Which should be my simplest configuration? RADIb-1 in each controller would give me 4 backends... That is supposing that two controllers cannot control the same two backends, is that allright? 2) I tried using simpleDB in each controller, but I got errors saying that no distribution can be done with simpleDB... Is that allright? 3) In the configs I'm proposing, where should the RecoveryLogs be stored? In the same backends (maybe only in one of the two?) that compose the DBclusters? I need some clarifications.... Thanx in advance, Jon -- Jon |
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
