Until now my "database server" has been happy with being a single PC.

Unfortunately the load is becoming too much, so it looks like I need to "distribute" the database.

What exactly does that entail? How can I spread my d/b across several servers? And do I need an intermediate server which users query & somehow distributes the load to the 'real' d/b servers?

How does that work? Fro d/b write? for read?

Any n00b 101 websites or books?

Accepted Answer

What exactly is the bottleneck with a single database. Is it

  • Read performance
  • Write performance

Few approaches used by high traffic websites.

  • Using master/slave model. Add one or more servers and make them as slaves to your master database. All writes will be performed on your master. Reads can performed from any of the slaves. This can be the simplest approach.

  • Sharding. Entities which does not need joins can be moved to a different database servers. Each shard can inturn have its own master-slave servers.


  • Clustering - Oracle RAC, Mysql NDB can provide clustering where a set of servers acts as a single unit.


Written by Anoop
This page was build to provide you fast access to the question and the direct accepted answer.
The content is written by members of the stackoverflow.com community.
It is licensed under cc-wiki