Grant Shipley deploys an application to the cloud and then turns up the heat by leveraging the right mix of elasticity and auto-scaling.
Randy Shoup tells war stories from Google and eBay focusing on how to scale code, infrastructure, performance, and operations, along with hard-won lessons learned in scaling them.
Liz Keogh discusses breaking down requirements without going into too much detail combined with complexity estimation for easy planning, dependency management, and prioritization.
Randy Shoup, Consulting CTO, shares the history of reactive services and visits key milestones in their evolution: async techniques at Google, real-time search at Ebay, & responsive games at Kixeye.
Bas Vodde introduces Large-Scale Scrum (LeSS), a framework for scaling Scrum to medium to large projects while staying true to the original Scrum principles.
The authors discuss scaling Agile by highlighting the constraints that a company needs to address given its particular context, an approach that adapts to context rather than ignoring it.
Jason Toy talks about the evolution and history of LinkedIn's release strategy.
The authors discuss about the lessons learned from all the biggest sites on the internet about how to build scalable and resilient architectures.
Marius Eriksen explains Twitter's experiences with functional programming (with Scala) @ Twitter: where functional techniques worked and where not. Also: how the Scala language has scaled with Twitter
Sergi Almar reviews the architecture behind WebSocket and tries to show how to build highly scalable applications with it.
The authors discuss Netflix's new stream processing system that supports a reactive programming model, allows auto scaling, and is capable of processing millions of messages per second.
Terence Yim from Continuuity showcases a transactional stream processing system that supports full ACID properties without compromising scalability and high throughput.