Tamar Bercovici presents Box’s transition from a single MySQL database to a fully sharded MySQL architecture, all the while serving 2 billion queries per day.
Zoltan Toth-Czifra shares scalability lessons learned at Softonic, a company that has developed and grew along with the Internet for over 15 years.
Joshua Suereth designs a scalable distributed search service with Akka and Scala using actors, and covering practical aspects of how to scale out with Akka’s clustering API.
Mike Nolet shares lessons learned scaling AppNexus and architectural details of their system processing 30TB/day: Hadoop, load balancer-free DNS architecture built in GSLB and Keepalived, and real-time data streaming built in C.
Peter Boros discusses a MySQL architecture useful for the majority of projects, backup, online schema changes, reliability and scalability issues, and basics of sharding.
Marton Anka shares lessons learned and technical details scaling LogMeIn over a decade.
Sid Anand uses examples from LinkedIn, Netflix, and eBay to discuss some common causes of outages and scaling issues. He also discusses modern practices in availability and scaling in web sites today.
Jesper Richter-Reichhelm shares lessons learned from failures while scaling Wooga games to millions of daily users.
Rajiv Eranki shares the pains and lessons learned scaling up Dropbox from a few thousands to tens of millions of users.
Theo Schlossnagle keynotes on the role of open source software and the breaking up of silos in the enterprise in creating scalable systems.
Jeremy Edberg shares some of the lessons learned scaling Reddit, advising on pitfalls to avoid.
Joe Armstrong outlines the architectural principles needed for building scalable fault-tolerant systems built from small isolated parallel components which communicate though well-defined protocols.