Re: [Hampshire] High availability database

Chris Simmonds wrote:
> One option I have considered is using, say, MySQL with one master node
> replicating to all the others and some mechanism to elect a new master
> if the original went down. But, that sounds messy. There must be a
> neater solution?

There are distributed databases - Hadoop, for example. Or if don't need
as much persistence, DHT.

However, I'm reasonably sure you'd find it cheaper to "bulletproof" a
master server than develop robust distributed applications.

Dan