Friends for Sale Architecture - A 300 Million Page View/Month...
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
URL Tag Cloud
Bookmark History
Saved by 21 people (-4 private), first by anonymouse user on 2008-02-21
- Somphol on 2009-10-14 - Tags facebook , rail , scalability , FFS
- Drsnyder on 2009-05-13 - Tags architecture , scalability , sysadmin
- Iskaldur on 2009-04-24 - Tags todo
- Tttaohhhan on 2009-03-19 - Tags no_tag
- Kellyhair on 2008-09-04 - Tags facebook , rails , ror , rubyonrails
Public Sticky notes
Joe Armstrong
Highlighted by juliob
n a short three months Friends for Sale (think Hot-or-Not with a market economy) grew to become a top 10 Facebook application handling 200 gorgeous requests per second and a stunning 300 million page views a month. They did all this using Ruby on Rails, two part time developers, a cluster of a dozen machines, and a fairly standard architecture. How did Friends for Sale scale to sell all those beautiful people? And how much do you think your friends are worth on the op
Highlighted by kelliegirl54
two part time developers
Highlighted by tttaohhhan
Choose a good host if you
plan on scaling, because migrating isn't fun.
plan on scaling, because migrating isn't fun.
Highlighted by wbahlke
database
Highlighted by wbahlke
two Rails developers
Highlighted by wbahlke
a remote DBA
Highlighted by wbahlke


Public Comment