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.
Randy Shoup shares war stories from eBay and Google about performance, consistency, iterative development, and autoscaling, connecting them with experiences building KIXEYE's gaming platform.
Sebastian Stadil advises on selecting the right cloud from EC2, GCE, or OpenStack based on one's needs, outlining the deployment and administrative challenges to be faced with each option.
Sebastian Kanthak overviews Spanner, covering details of how Spanner relies on GPS and atomic clocks to provide two of its most innovative features: Lock-free strong (current) reads and global snapshots that are consistent with external events.
Randy Shoup details some of the pieces forming Google’s technology stack, BigTable, Megastore, Dremel, virtualization, etc. and the design principles of their their cloud-based applications.
John Penix describes the test automation system and the supporting build system infrastructure used by Google.
Rob Pike explains how Google designed Go to address major development issues they encounter while using other languages: long build times, poor dependency management, lack of robustness, etc.
Mike Solomon shares some of the experiences and lessons learned scaling YouTube over the years.
Derek Parham discloses details of the largest and most complicated user migration and code refactoring in Google’s history when all their services were made available to Google Apps users.
Roberto Peon introduces SPDY which is the starting point for HTTP 2.0, a standard in development, explaining why a new HTTP standard is needed and how SPDY helps.
Kevin Bourrillion introduces Guava, a set of open source core libraries used internally by Google.