Matt Mullenweg (WordPress) - The Architecture Behind WordPress.com
Posted by rmp at 15:18 3rd Oct 2007
Scaling platform:
88m global uniques
1.5m blogs
215m pageviews/day
- 7 boxes, $1500/mo.
- 2 balancers, 2Gb memory, any disk, pound+wackamole+spread.
- 2 databases, 4Gb+ memory, fast disk (RAID), master+slave mysql, split read/write.
- 3 webs, fast cpu, 2Gb memory, litespeed or well-configured apache.
- Everything in subversion.
- Be stateless (shared nothing)
- Memcached
geo-targetting of dns, might as well use a CDN
single box 300 req/sec 29.5m/day
Scaling community:
Ref: sxsw presentation
Scaling business:
Tie revenue streams to cost scaling, e.g. pageviews rather than bloggers.
Ads scale revenues with pageviews, effective CPM, low outlay.
VIP class of users with advanced features, customisation etc.
Scaling people:
Hire people as good as, or better than you.
Great people = Rich environment + worthwhile problems.
5 things to look for:
- Personality fit (when the shit hits the fan)
- Ability to learn (curiosity)
- Taste (can't be taught)
- Passion for the space
- Familiarity with current technologies
Don't put out too easily - don't hire if doubts exists
It's fun to know that the folks at wordpress manage deployment with ssh scripts running svn up.
I disagree with Matt's QA response suggesting that you should never do your own hosting. In principle that's ok for the large faceless mass of current web sites & traffic but under special circumstances it's the only way. I build web apps on top of bioinformatics pipelines supporting (today) 320Tb data and there's no way on Earth this would be possible to outsource.
(0 comments)
Psyphi Blog v5
Atom
