Clay McCoy discusses using Groovy’s metaprogramming capabilities and AWS SWF to deal with unreliable remote services, parallelization, scheduling critical timers, and server failures.
Joe Sondow presents how Netflix uses Asgard to deploy code updates and manage resources in the Amazon cloud.
Ward Cunningham keynotes on how Events, Sockets, CORS, Closures, SVG, DSLs, Canvas, EC2 and Raspberry Pi contribute to a new type of wiki, a federated one.
Attila Narin discusses AWS concepts: Availability Zones, RDS Multi-AZ deployments, SQS and Auto Scaling, Elastic IP, load balancing, DNS, DynamoDB, Amazon S3, etc., and EC2 best practices.
Shanley Kane discusses Dynamo - consistent hashing, vector clocks, hinted handoff, gossip protocol - advances in each area, and how querying and application development has changed as a result of them
Yashwanth Nelapati and Marty Weiner share lessons learned growing Pinterest: sharding MySQL, caching, server management, all on Amazon EC2.
Soam Acharya presents a case study of a business which relied heavily on AWS and had to reduce its dependencies on it, including tips for avoiding cloud lock-in.
Chris Pinkham explains how to create an automated scalable self-service infrastructure based on principles used by Amazon to build their cloud services.
Paul Weiss introduces cloud computing and its various models, comparing them with virtualization, then overviews Eucalyptus and compares it with AWS.
Jeremy Edberg discusses running Netflix services on AWS: storage, streaming and scaling solutions, multi-region deployments, why cloud over private data center, and architectural snapshots.
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.