Architecture at scale. Lessons from the BBC, Facebook, Twitter and more [List]

This is part of my trails and lists series, after Vannevar Bush. In that vein, please send me items to add or follow me @danfrost. I’ll update these as I come across new things.

My trail of spying on how big companies build things. Some things I’ve learnt:

  • They have a deep understanding of their use cases. The understand how the users will use the system and what this means for the their design of the system.
  • They’ll combine very new things for specific tasks with old (sometimes really old) stuff. And they’ll replace things.

The Tech Behind Dropbox’s New User Experience on Mobile

More traffic, more videos, more screens: building the BBC’s Olympic site

And their “2012 Programme: Architecture Overview“:

How Three Guys Rebuilt the Foundation of Facebook
Which is interesting how they had dug themselves into a PHP-hole, and got out from the ground up.

And some slagging of Facebook: Database high priest mud-wrestles Facebook

I nice trick from Spotify. What is the advantage of having a domain name (spotilocal) that resolves to

Some Facebook Data Store API Thoughts

Facebook e-mail mess: Address books altered; e-mail lost

Twitter changing its tools. Twitter jilts Ruby for Scala

Scaling lessons learned at Dropbox, part 1

2012: Putting your robots to work: security automation at Twitter


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s