Jeremy Edberg shares the need, the benefits, the pain points and the lessons learned moving Reddit and Netflix’s internal solution to Amazon AWS.
Mark Ryland presents and demoes identity and access management concepts as used in the cloud and EC2 security groups and packet networking inside the Amazon AWS.
Yves Reynhout discusses event sourcing and storage, demoing implementing a conceptual event storage model on top of AWS Storage and Azure Storage Services.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Jinesh Varia discusses automating continuous integration, continuous deployment and continuous optimization in the context of using cloud computing services.
Siddharth Anand presents how Netflix’s architecture evolved from a traditional 3-tier configuration to a cloud-based one, detailing the scalability and fault tolerant issues encountered.
Carl Quinn presents the build and deployment architecture used by Neflix in order to provide content out of Amazon AWS.
Peter Ledbrook outlines the differences between several PaaS providers from the perspective of building, deploying and running a Grails application in the cloud, demoing running it on Cloud Foundry.
Siddharth Anand overviews Netflix’s business model, then he explains why they chose Amazon AWS, and how they moved their data into the cloud using a NoSQL solution.
Andy Gross discusses the design philosophy behind Riak based on Amazon Dynamo - Gossip Protocol, Consistent Hashing, Vector clocks, Read Repair, etc. -, overviewing its main features and architecture.
Adrian Cockcroft discusses the advantages of running Netflix on AWS, comparing the old data center solution against the new cloud architecture, the current implementation and plans for the future.
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.