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.
Ali Kheyrollahi elaborates on the Client-Server tenet of REST which focuses on separation of concerns and responsibilities between the client and the server.
Shiva Narayanaswamy discusses event driven architectures, serverless architectures, identity management and security related to building APIs in the cloud.
Swagger is a simple but powerful representation of RESTful APIs. This talk gives an introduction to API creation using the Swagger Editor, and creating a REST service using swagger-codegen.
Vivian Chandra outlines the benefits of an API they created including how it has helped them automate part of their CRM process and protected them from changes of the CRM system.
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.
Owen Rubel talks about IO state that can be shared, cached, synced and reloaded on the fly for all architectural instances without having to restart any instance.
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.
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.
Jason Harmon discusses using API specification formats to drive the development process, focusing on parallelizing work, improving feedback loops, and delivering high quality API products.
Adam Duvander shares 4 API lessons: outsourcing development, possible regrets on making an API public, not all need your API, and an API can provide more opportunities that one can build.