Shelby Switzer discusses success stories and failures of using the public data provided by governments, along with techniques for making such data usable.
Rob Zazueta introduces RESTed NARWHL, a design framework for building RESTful APIs that adhere to current best practices while being able to rapidly adapt to change.
Charles Lamanna talks about the scale and architecture of Microsoft’s Azure Management Gateway and how Azure API’s are built for high availability and for data sovereignty.
Rana Pereis explores case studies of how banks are using APIs to evolve new digital offerings and business models that help drive customer engagement and acquisition.
Mike Amundsen discusses innovation and how the latest round of technical advances in APIs can be used to leverage growth and innovative thinking within teams, companies, and communities.
Tom Schindl reviews Eclipse 4’s API and architecture, pinpointing successes, failures and mistakes.
Brett Adam shares how Zendesk built an API-first company and some tips and tricks learned "from the field" on how to build an API that developers love.
Sadek Drobi talks about the prismic.io API and how to understand the properties and the mechanics of a system, and to partition its different dimensions to avoid a domino style failure cascade.
Robert Metzger provides an overview of the Apache Flink internals and its streaming-first philosophy, as well as the programming APIs.
Russ Miles shows how we can build production-level confidence in our polyglot microservices by applying the test-driven approach to synchronous (REST) and asynchronous (Messaging) services.
Sebastien Lambla explores how complexity can be reduced to its smallest cohesive parts, communication normalized through evolvable contracts, ReSTful and event-driven interfaces.