Petar Maymounkov introduces Go Circuit, a system that reduces the human development and sustenance costs of complex massively-scaled systems nearly to the level of their single-process counterparts.
Delivering Performance Under Schedule and Resource Pressure: Lessons Learned at Google and Microsoft
Ivan Filho shares lessons learned during the development and release of several large scale services at Microsoft and Google from the perspective of a performance manager.
Kiran Prasad discusses what impact mobile has on architecture, explaining how HTML5 and Node.js can help, and sharing how to use these technologies effectively at scale.
Matt West explains how to use technologies like CloudStack, Beanstalk, Gearman, mod_gearman, Nagios, nagconf and other tools to monitor large web applications at scale deployed in the zCloud.
Xavier Amatriain discusses the machine learning algorithms and architecture behind Netflix' recommender systems, offline experiments and online A/B testing.
Stephane Maldini on addressing several issues concerning web applications written with Grails: scrolling large data sets without blocking, streaming to the browser, scale Grails in the cloud, etc.
Deepak Nadig, Praveen Alavilli present how PayPal redesigned its APIs based on lessons learnt developing their services in over 14 years, and the principles, patterns and anti-patterns used in API design.
Matthias Broecheler discusses graph computing, introducing the Aurelius graph cluster enabling graph computing at scale by building on distributed systems like Cassandra, HBase, and Hadoop.
Pedro Canahuati describes how Facebook's operations maintains their infrastructure, including challenges faced and lessons learned: prioritizing calls, managing technical debt, incident management.
Blake Dournaee covers the often forgotten back-end architecture for mobile apps which should expose cross-platform APIs to mitigate some of the effects of mobile O/S fragmentation.
Steve Pember discusses creating Grails applications integrating message broker technologies, especially RabbitMQ, and applying SOA principles.
Kyle Kingsbury discusses some of the limitations found in distributed systems and the way some of them behave under partitioning.