Jeff Johnson introduces Apollo, a hierarchical NoSQL data system meant to deal with Facebook's distributed storage needs.
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.
Ian Plosker explains why a data model needs to follow the query patterns when using a NoSQL storage solution.
Geir Magnusson explains how Gilt Groupe is using Project Voldemort to scale out their e-commerce transactional system. The initial SQL solution had to be replaced because it could not handle the transactional spikes the site is experiencing daily due to its particular way of selling their inventory: each day at noon. Magnusson explains why they chose Voldemort and talks about the architecture.
In this FutureRuby talk, Ilya Grigorik explores Tokyo Cabinet's features such as the key-value store, ordered traversal, attribute search, schemaless data structures,indexing, and scripting with Lua.