Raymond Blum discusses some of the challenges, solutions and discarded alternatives in creating durable storage systems at Google scale.
Scott Vokes presents some lesser-known data structures and shows how probability distributions and content-addressable storage can become tools to shape global system behavior.
Jeremy Edberg presents the data stores used by Netflix and Reddit, some of the best practices and lessons for surviving outages.
Nathan Herring presents the available storage options at Google, the ideal characteristics of a storage service, and the actual implementation of Google Cloud Storage.
Serkan Piantino discusses news feeds at Facebook: the basics, infrastructure used, how feed data is stored, and Centrifuge – a storage solution.
Andy Gross reports on how Basho used Riak and Erlang to build their cloud storage service.
Dragos Manolescu introduces some of the new features in Windows Phone Mango - TCP and UDP sockets, network preferences and local storage –, discussing their optimization for lower power consumption.
Scott Davis explains how to prepare a website for mobile devices from small tweaks –smaller screen sizes, portrait/landscape- to using HTML5’s local storage, application cache, and remote data.
Greg Young discusses how to use events to store data, and how testing, versioning and performance are impacted by an event-centered model.
Matt Wood presents the most important AWS services, explaining how to scale up and out, how to extend the basic stack, how to use storage, and how to manage MySQL databases running on EC2.
Simon Guest presents 5 cloud computing patterns along with examples and Azure solutions for scaling, multi-tenancy, computing, storage and communication.
Jay Kreps discusses the architecture, algorithms, implementation and deployment of Voldemort, a distributed storage system. He also presents the problems solved using Voldemort at LinkedIn.