Master-master vs master-slave database architecture?

Viewed 98582

I've heard about two kind of database architectures.

  • master-master

  • master-slave

Isn't the master-master more suitable for today's web cause it's like Git, every unit has the whole set of data and if one goes down, it doesn't quite matter.

Master-slave reminds me of SVN (which I don't like) where you have one central unit that handles thing.

Questions:

  1. What are the pros and cons of each?

  2. If you want to have a local database in your mobile phone like iPhone, which one is more appropriate?

  3. Is the choice of one of these a critical factor to consider thoroughly?

2 Answers
Related