Olaf Carlson-Wee examines various novel cryptosystems used to facilitate the secure storage of billions of dollars in global crypto banks.
Rob Scherer and Rob Alford discuss the Design Sprint process used by Google Ventures, some of the changes made to it and lessons learned along the way.
Marcus Frodin discusses a few failures he has overseen at Spotify, deriving a framework of how to think about and evaluate what worked and what didn’t, and how to get more of the things that did.
Sean Cribbs discusses practical applications of academic research with a large scale distributed system, as well as membership and dissemination protocols and their application in practice.
Luke Kosewski describes Flow, how it adds value to a microservice architecture, what preconditions must be met for such a recovery mechanism to succeed, and tells the story of a 2015 Q4 outage.
Michael Hyatt discusses the main complains users have with APIs and ways to address them using early user acceptance testing, RAML, JSON schemas, traits and mocks.
Thomas Gamble examines each factor in the Twelve Factor App (12factor.net) which describes elements of cloud native, and presents how Spring, and platforms such as Cloud Foundry satisfy them.
Josh Long looks at how high performance organizations like Ticketmaster, Alibaba, and Netflix make short work of that complexity with Spring Boot and Spring Cloud.
Stefanie Schirmer talks about the case study of building an API-first architecture at Etsy, why they built it, the tools used, the mistakes made and the lessons learnt along the way.
The authors keynote on Pivotal and Cloud Foundry, the role of women in software development, containers and broken culture, experiences shared by Comcast and City Bank building solutions with Pivotal.
Adrian Cockroft keynotes on the lessons learned so far on cloud computing and applying them to simplify future projects.
The authors keynote on Spring Framework 5, the roadmap to 5.1 and designing reactive applications with Spring.