Andrew Godwin tells Lanyrd’s story, covering the technology stack, tricks used, and what they would do differently if they could start afresh.
Steve Smith shares some of the change patterns used to establish the Continuous Delivery of 60+ applications at Sky Network Services over the past 2 years, and how they fit into an optimal cycle time strategy.
Dave Farley introduces the ideas of Continuous Delivery as a practical everyday process, using some of the techniques and technologies from a real world project as an example.
Robert Shilston demoes an FT app, discussing the technology choices and architectural approaches that have been used to solve some of the most difficult technical challenges faced in web development. Topics covered will include layout and interactions,native wrappers,testing and QA, and how to manage regular, reliable and successful deployments of an offline cached application.
Allen Rohner shares the difficulties encountered and the lessons learned building a PaaS in Clojure.
Jay Kreps discusses the evolution of LinkedIn's architecture and lessons learned scaling from a monolithic application to a distributed set of services, from one database to distributed data stores.
Marc Frons discusses the New York Times’ digital subscription model. Rajiv Pant shares their experiences transitioning to continuous delivery, and using NodeJS, Scala, cloud and big data.
Randy Shoup details some of the pieces forming Google’s technology stack, BigTable, Megastore, Dremel, virtualization, etc. and the design principles of their their cloud-based applications.
Alex Papadimoulis discusses various deployment strategies, scalable delivery, with examples from real-world organizations such as AllRecipes.com, Twitter, and Google.
Brian Jimerson presents a startup case study, including business challenges and the architectural solution implemented with Groovy, Grails and Spring.
Paul Downey and David Heath discuss the UK Government Digital Service API Design Principles, the lessons learnt from building the GOV.UK publishing platform and transactional services on APIs, and how these design principles are now being applied to enable departments and agencies across government to transform transactions and services into becoming "digital by default".
Stefan Armbruster discusses building a Grails application with a graph data store based on Neo4j and sharing insight based on his own experience using such a system in production.