We scale Streamfile.com with Erlang. Both front & back-end.
Check out:
How do you scale your web application?
11–20 of 41 posts
Re: How do you scale your web application?
#12Up (in the short-term)
Re: How do you scale your web application?
#13Check out this presentation, it includes almost everything you need to know about scaling: http://www.coderholic.com/the-ultimate-scalability-presentat...
Re: How do you scale your web application?
#14Generally we stick with caching, when that starts to give diminishing returns we add a web server. Database stuff is quite a bit harder, of course, we're been fortunate there so far :)
Re: How do you scale your web application?
#15Ah caching, the cause of and solution to all of life's problems.
There are only two hard things in Computer Science: cache invalidation and naming things.
-Phil Karlton
Re: How do you scale your web application?
#16We scale Streamfile.com with Erlang. Both front & back-end. Check out: http://www.erlang-web.org/
Adding lots of application servers isn't the hard part, generally (from what I've read... I have to admit I've never had to do more than the 'easy stuff'). The database is. How's Mnesia scale up? Where does it work well, and where does it not work so well?
Re: How do you scale your web application?
#17Mini-guide to scaling your app:
Step 1. Measure, measure, measure: response time, page load time, query time
Step 2. Identify bottlenecks: Why isn't your page load snappy? Too much JS? Round-trip to DB is killing you? Your mongrels are overloaded?
Tip: Use YSlow for frontend measurements and take most of its advice
Step 3. Fix bottlenecks: Lots of techniques to fix faster frontend performance, start with YSlow above. Architectural and backend issues can be solved with a combination of hardware (load balancers, more web boxes, more db boxes) and software (better caching strategies, evolve your DB architecture, break up your application into smaller micro-apps that scale independently)
Step 4: Go to step 1 and keep at it.
I'd have to say that if you're not doing Step 1, you're going to fail now, or eventually. As one of my first mentors taught me:
"You cannot improve, what you don't measure"
Re: How do you scale your web application?
#18After the easy stuff: move your database to its own server, add a load balancer in front of additional web servers, implement memcached, start splicing your database to multiple servers, continue to add web servers, serve your static files from a cdn
baller
Re: How do you scale your web application?
#19After the easy stuff: move your database to its own server, add a load balancer in front of additional web servers, implement memcached, start splicing your database to multiple servers, continue to add web servers, serve your static files from a cdn
What would be the first thing you do? All that adds up...
Re: How do you scale your web application?
#20After the easy stuff: move your database to its own server, add a load balancer in front of additional web servers, implement memcached, start splicing your database to multiple servers, continue to add web servers, serve your static files from a cdn
I'd suggest implementing memcached before adding a second DB server, often this can help in scaling incredible amounts. We had an application which as soon as we implemented memcached(we really should have off the bat) the load was cut over 1/2. Of course this was an extreme example since the server was getting pounded with tons of reads from our DB every second.