Evan Broder talks about how Stripe has designed the systems to speed up the development process and how the software infrastructure in their API enables the next tech companies to build faster.
Andrew Psaltis talks about Apache Beam, which aims to provide a unified stream processing model for defining and executing complex data processing, data ingestion and integration workflows.
Saul Caganoff discusses the different use cases for API consumption and the technical affordances API designers can provide to support those use cases.
Matthew Erbs discusses the need for applying lessons learned building APIs for customers to the creation of internal APIs for the DevOps team.
Ross Garrett explores how design decisions may be leading to poor UX, discussing the principles of reactive applications and how streaming APIs can deliver significant benefits over RESTful APIs.
Nik Wakelin discusses why developers dislike writing documentation, what can be done about it and how to improve the process of writing docs.
Lindsay Holmwood discusses the problems with the traditional approach to digital service delivery in government, and how APIs enable the DTO to help government deliver simpler, faster public services.
Katharina Probst talks about the situations in which server-side scripting is a good solution for applications. She describes Netflix’s first approach, which uses Groovy scripts.
Bruce Haefele shares from the successes and failures implementing an API strategy at Healthdirect Australia.
Neville Li and Igor Maravić cover the evolution of Spotify’s event delivery system, discussing lessons learned moving it into the cloud using Scio, a high level Scala API for the Dataflow SDK.
Tom Adams outlines the problems faced when building small services, and how using a good type system can help, introducing Finch and highlighting how it addresses these concerns.
Adeel Ali presents insights from his database of 11,500 real world APIs.