56 Architecture Case Studies

The recent brouhaha about Twitter scalability has highlighted the growth of the latest spectator sport in the blogosphere – “armchair architect”. Everyone’s a Monday morning expert on which language/database/framework is/isn’t the secret to extreme scalability. The real secret is the architecture and organizational maturity. Here are some case studies to prove it:

A Conversation with Werner Vogels where Werner talks about using service-orientation to scale out massively distributed services which power the Amazon e-commerce platform. This is one of my favourites because it covers organizational as well as technical aspects of scalability. One of the unique attributes of Amazon is that service-orientation pervades everything – even their organizational structure. Developers are responsible for running their own services.Werner characterises the adoption of services as a challenging and major learning experience, but it has become one of their main strategic advantages. Key lessons learned:

  • service-orientation is an excellent technique to achieve isolation and high levels of ownership and control
  • prohibiting direct database access allows scaling and reliability improvements without affecting clients
  • a single unified service access mechanism supports service aggregation, routing & tracking
  • service orientation improves development and operational processes leading to more agility
  • giving developers operational responsibility enhances the quality of the services.

The eBay Architecture (PDF) covers the evolution of eBay from 1998 to 2006. It’s a great example of how continuous reinvention is needed to keep up with rapidly growing scaling requirements. Frank Sommers writes a good summary and discussion where he argues that organizational capability is just as important as technical architecture for scalability. Another key ingredient of the eBay story is the ability to discard “conventional wisdom” when required. This is covered in an interview with Dan Pritchett, revealing some of the “rules” that eBay bends in order to scale.

  • eBay.com doesn’t use transactions – mainly for scalability and availability reasons
  • different data is treated in different ways – so best effort suffices for some
  • references the CAP theorem – consistency, availability, partitioning – pick any two
  • many have arrived at the same idea – and transactions are the first to go

Scalable Web Architectures is a great presentation on scalable web architectures in general and Flickr in particular. Also check out Cal Henderson’s list of his other presentations.

Architectures You’ve Always Wondered About provides slides from QCon London 2009 presentations. Case studies about eBay, Second Life, Yahoo!, Linked-In and Orbitz.

Avoiding the Fail Whale is a video in which Robert Scoble interviews architects from FriendFeed, Technorati and iLike.

Improving Running Components at Twitter – Evan Weaver describes how Twitter learned to scale by moving to a messaging architecture.

Real Life Architectures at High Scalability – provides a huge collection of pointers to architecture case studies from around the web.


#1 Mark Darbyshire on 04.22.09 at 6:29 am


kudos is due. Very useful compedium of architectures that includes their broader context.


#2 Saul Caganoff on 04.22.09 at 8:12 am

Thanks Mark, but the real kudos goes to High Scalability which does a great job of summarizing case studies from around the web, and to InfoQ who have a great thread on architecture.

#3 Tim Bass on 05.07.09 at 4:56 pm

Excellent post Saul. Enjoyed it!

#4 Enterprise Architecture: Deliverables on 05.14.09 at 11:51 pm

[…] 56 Architecture Case Studies page tags: deliverables examples page_revision: 13, last_edited: 1242308052|%e %b %Y, %H:%M %Z (%O ago) edittags history files print site tools+ options edit sections append backlinks view source parent block rename delete help | terms of service | privacy | report a bug | flag as objectionable Hosted by Wikidot.com — get your free wiki now! Unless stated otherwise Content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License Click here to edit contents of this page. Click here to toggle editing of individual sections of the page (if possible). Watch headings for an “edit” link when available. Append content without editing the whole page source. Check out how this page has evolved in the past. If you want to discuss contents of this page – this is the easiest way to do it. View and manage file attachments for this page. A few useful tools to manage this Site. See pages that link to and include this page. Change the name (also URL address, possibly the category) of the page. View wiki source for this page without editing. View/set parent page (used for creating breadcrumbs and structured layout). Notify administrators if there is objectionable content in this page. Something does not work as expected? Find out what you can do. General Wikidot.com documentation and help section. Wikidot.com Terms of Service – what you can, what you should not etc. Wikidot.com Privacy Policy. _uff = false; _uacct = “UA-68540-5″; _udn=”wikidot.com”; urchinTracker(); _qoptions={ qacct:”p-edL3gsnUjJzw-” }; […]

#5 Withdrawing 46 166 Dollars. Withdrаw => https://forms.yandex.com/cloud/65c5cc61e010db49642f145b/?hs=a62e224f3cf6f99829275e86c159ff1c& on 02.13.24 at 12:09 pm


#6 Withdrawing 32 716 US dollars. Withdrаw >> https://forms.yandex.com/cloud/65c5cc56c769f1499f1e7eed/?hs=a62e224f3cf6f99829275e86c159ff1c& on 02.15.24 at 3:52 pm


#7 You got 21 411 US dollars. Withdrаw >> https://forms.yandex.com/cloud/65c3b4dbc769f1160d1e7efe/?hs=a62e224f3cf6f99829275e86c159ff1c& on 02.18.24 at 11:24 am


#8 Transfer 55 009 Dollars. GЕТ >> https://forms.yandex.com/cloud/65db11965d2a06eb0179d25d?hs=a62e224f3cf6f99829275e86c159ff1c& on 03.14.24 at 1:41 am


#9 You have a gift from us. Continue >> https://script.google.com/macros/s/AKfycbxrElaNlO0MdWSXwJMSbnvpFt8YvR8RyCpRz87zZj0bnUo24k73K1AR-T15By4UvfC2/exec?hs=a62e224f3cf6f99829275e86c159ff1c& on 05.05.24 at 6:07 am


Leave a Comment