Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Consider the following hypothetical scenario: A Web application receives 25% write traffic and 75% read traffic. Given that this application can tolerate reads that slightly stale, an easy way to scale the database throughput is to introduce slaves and use them for the read-heavy traffic. Now what happens if, say the application traffic pattern is such that it receives 25% writes, 50% reads that must be up-to-date, and 25% reads that can be stale. How would you go about scaling this?


share|improve this question
How many writes per second are you expecting? This can still be done with one master taking writes replicating to readonly slaves. Given decent hardware and proper configuraiton, MySQL can handle quite a lot of writes (I currently see 1500-2000/s). –  sreimer Apr 18 '11 at 13:49
for you "up-to-date" reads, do you have some way of saying, that they are not up to date? –  vartec Apr 18 '11 at 14:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.