The 12 Days of Scale-Out
MySQL.com has put together 12 days of case studies and discussion on database scale-out. “Scale-out” describes the process of increasing web application speed and scale by adding multiple replicated database servers incrementally and only as-needed. As your hot new web app gains users, you scale it out from one database to three, or from four to 23. It’s the opposite of “scaling-up”, which involves upgrading all of your hardware and database licenses to add capacity. Growing companies can keep their existing investment; large companies can save millions.
The case studies have some interesting facts and figures but they don’t go into a lot of depth. But that also makes all 12 days a quick read! If nothing else, it should help anyone who’s trying to convince the higher-ups that MySQL is a viable, scalable choice by allowing them to do a little name dropping. “It will save us money” also tends to resonate with the folks in suits.
12 Scale-Out Case Studies and Discussion
- Day One: Booking.com
- Day Two: GumTree.com
- Day Three: Alcatel-Lucent
- Day Four: Zimbra
- Day Five: Wikipedia
- Day Six: Top Five Scale-Out Pitfalls to Avoid
- Day Seven: The Phone House
- Day Eight: Zappos.com
- Day Nine: RightNow Technologies
- Day Ten: iStockphoto.com
- Day Eleven: Skyblog
- Day Twelve: Zillow.com and mixi
