This link has been bookmarked by 33 people . It was first bookmarked on 02 Mar 2006, by Wade Ren.
-
29 May 09
-
21 Nov 08
-
22 Mar 08
-
03 Feb 07
-
26 Jan 07
-
Scaling the database is the "hard part", but still a solved problem. Once you get beyond what can be easily managed by a decent master-slave setup (and that'll probably take millions and millions of pageviews per day), you start doing partitioning. Users 1-100K on cluster A, 100K-200K on cluster B, and so on. But again, this is nothing new. LiveJournal scales like that. I hear eBay too. And probably everyone else that has to deal with huge numbers.
-
-
23 Jan 07
-
05 Dec 06
-
12 Nov 06
-
14 Sep 06
-
31 Aug 06
jeanjordaanTake state out of the application servers and push it to database/memcached/shared network drive (that's the whole Shared Nothing thang). Use load balancers between your tiers, so you have load balancers -> web servers -> load balancers -> app servers ->
rails ruby Scalability Performance rubyonrails architecture scaling for:rochecompaan
-
31 Jul 06
-
19 Apr 06
-
16 Mar 06
-
15 Mar 06
-
14 Mar 06
-
21 Dec 05
David SlatteryTechniques to scale - language independent
-
07 Nov 05
-
29 Sep 05
-
11 Sep 05
-
22 Aug 05
-
18 Jul 05
-
14 Jul 05
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.