This post originated from an RSS feed registered with Ruby Buzz
by Patrick Lenz.
Original Post: Q&A: The adventures of scaling, Stage 1
Feed Title: poocs.net
Feed URL: http://feeds.feedburner.com/poocsnet
Feed Description: Personal weblog about free and open source software, personal development projects and random geek buzz.
My initial article about the scaling journey we went through with eins.de generated quite some buzz in the Rails niche of the web. A lot more than I had anticipated.
A number of questions have popped up here and there which I'll try to address in this article. While you'll surely understand that I'm not going to spoil what's coming up in the rest of the series (which we're only through with by a quarter!), I'll share some additional details.
Assuming the amount of questions stays at this volume, each article will be accompanied by a Q&A followup article a few days later.
As an aside, please understand that there is no one-size-fits-all solution for scalability problems or a walkthrough guide for your specific application needs. eins.de has certain characteristics which your application might not have.
For example, we store a lot of historic data for forums, personal messages, gallery comments, and more. On any given day, we have tens of thousands of rows being newly inserted while millions are already sitting in each table. This obviously affects query times and the need arises to temporarily store SQL results outside of the SQL service. Your application might have an entirely different concept there.
If you need help analyzing the characteristics and needs of your particular application, please drop me an email at patrick@limited-overload.de and we'll work something out on a consulting level.
Previous Topic
