I've started a project with the Spring MVC AppFuse 1.9.4, and I'm trying to think about high availability.
We're using Oracle 9i, and don't (currently) have the luxury of using an Oracle cluster. We can, however, make use of DataGuard, which in essence keeps a backup database "mirrored" in case the primary fails. I don't know if Sequoia (http://sequoia.continuent.org/Overview) is a good fit, because it implements RAIDb (redundant array of inexpensive databases) and expects to be able to write to any of them - whereas if we use DataGuard I want to read/write from one only, then fail over to the backup only if the primary dies. Another thought I had was to load up two Spring application contexts - one pointing to the primary, one to the secondary, then if the primary every failed detach the objects from session #1, attach them to session #2 as dirty, save them, and (hopefully) be back in sync with all the current data saved on the backup db. But that seems hack-y. I know the "right" way to do it is with a true db cluster, but given our limitations do you AppFusers have any suggestions? Jason
