Simon Ferguson describes how MBIE is using APIs, initiatives that are underway to increase use of APIs, and the considerations that are involved with providing governmental services as APIs.
Matt Ranney covers the evolution of Uber's architecture and some of the systems they built to handle the current scaling challenges.
Marc Danneels tells a story on how ASB started using APIs and the lessons learned along the way, covering ASB’s plans to continue extending the API environment externally.
Anders Ivarsson discusses how teams are autonomous at Spotify, how they are organized in squads, chapters, tribes and guilds, and how management and leadership works in their company.
Dustin Hudson discusses enterprise architecture using case studies and life examples to illustrate how to put together legacy systems and third-party apps while considering user-driven decisions.
Josh Evans uses the Netflix Operations Engineering team as a case study to explore the challenges faced by centralized engineering teams and approaches to addressing those challenges.
Katrina Clokie discusses how BNZ does web (SOAP, REST) services testing, the tools and practices employed and some of the resources and exercises their testers use to learn how to test.
Scott Hickey answers audience questions about what it is like to build a mission critical application for a Fortune 500 company using Groovy.
Nitesh Kant describes how embracing asynchrony in Netflix applications, from networking to business processing, creates gracefully degrading and highly resilient applications.
Joe Brophy discusses the journey of NZ Posts digital team from inception to maturity, the new way of working that has developed, combining Design Thinking and Lean Start-up and the role of APIs.
Hans Dockter discusses how to solve the challenges of standardization, dependency management, multi-language builds, and automatic build infrastructure provisioning.
Erran Berger discusses how they scaled architecture at LinkedIn across multiple data centers.