Tom Limoncelli discusses creating resiliency at the most economic level, doing risky procedures often, and creating a blameless culture to encourage communication and improve system reliability.
Giannakakis and Dalkitsis present how Shazam releases faster, more predictably and with more features by using BDD and automation testing, without slowing down or hindering the development process.
Michael Brunton-Spall shows how DevOps-like patterns can be applied on microservices to give the development teams more responsibility for their choices, and much more.
Phil Calcado shares the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable, dealing with operations overhead, DevOps, breaking changes and asynchronous behaviors.
Anil Madhavapeddy describes how to design and build "deploy-and-forget" cloud services that are specialized into unikernels, single-address space virtual machines.
Martin Lippert and John Arthorne demo the creation of a cloud service with Flux, connecting it to a running Flux environment, and implement some basic features for a sample language.
Eberhard Wolff discusses the benefits of microservices and some of the advantages of creating smaller services instead of larger ones.
Kin Lane discusses the opportunities of deploying high value, re-mixable APIs, using Docker.
Paul Fremantle explores the challenges of security for IoT, including reviewing some existing attacks and predicting others, hardware, software, network and cloud attacks.
Adrian Cockcroft summarizes the differences and commonalities across some of the largest microservices deployments in production, showing how they are evolving.
Dave Farley looks at a history littered with inefficient processes resulting in poor quality and failed projects, wondering how we got here, what can be done and what does good really look like?
Chris Richardson shares his experiences developing and deploying a microservices-based application.