Name: Anonymous 2006-04-15 0:59
need ideas -
which db offers distributed redundancy and automatic switching? (when one fails, another automatically takes over. the user will never be affected) does the "auto-switching" require additional hardware or some type of softare resolution? furthermore, what if the "switch" failes? does it need redundancy in it too?
the issue gets deeper~ this db is linked to some sort of java web container or app server. havn't yet decided on one yet. so, should the db be on separate machines, what happens if the web container (app server) dies? is there a webserver that offers distributed redundancy and again, auto switching?
constriants: open-source db or relatively cheap ones.
application must not go off line, hence the lvl of redundancy we're throwing @ it.
which db offers distributed redundancy and automatic switching? (when one fails, another automatically takes over. the user will never be affected) does the "auto-switching" require additional hardware or some type of softare resolution? furthermore, what if the "switch" failes? does it need redundancy in it too?
the issue gets deeper~ this db is linked to some sort of java web container or app server. havn't yet decided on one yet. so, should the db be on separate machines, what happens if the web container (app server) dies? is there a webserver that offers distributed redundancy and again, auto switching?
constriants: open-source db or relatively cheap ones.
application must not go off line, hence the lvl of redundancy we're throwing @ it.