Session + Live Q&A
A Standardized, Specification-Driven API Lifecycle
API specifications like OpenAPI are often seen as just documentation, or possibly used for code generation--when in reality they have become much, much more. OpenAPI and AsyncAPI have emerged as the way API producers and consumers are engaging across the entire API lifecycle, beginning with documentation and code generation, but also mocking, testing, security, and other essential parts of our API operations. API specifications like OpenAPI and AsyncAPI provide a machine-readable artifact that can help automate and streamline the API lifecycle, but it also normalizes who we human beings talk about APIs, how they are applied programmatically, but also iterated upon over time. Ensuring that all of us humans are on the same page through a more standardized, specification-driven API lifecycle.
Speaker
Kin Lane
Chief Evangelist @Postman
Kin Lane is the Chief Evangelist for Postman, and has been writing about the API lifecycle for over a decade as the API Evangelist. Working with companies, organizations, institutions, and government agencies to define the API lifecycles that have emerged across almost every aspect of our...
Read moreFind Kin Lane at:
From the same track
Building With Extensibility
Tuesday Nov 9 / 12:10PM EST
Extensibility isn't just making your endpoints public; you should think about how your product will be extended and enhanced by others before you write a line of code. Gain an understanding of why we want to build extensible products rather than just checking off a "public API" box....
Christi Schneider
Software Engineer @Square
Designing Event-Driven Architectures Using the AsyncAPI Specification
Tuesday Nov 9 / 11:10AM EST
In the world of REST APIs, we're used to having a great variety of tools and specifications (Swagger, OpenAPI, RAML). This has enabled us to automate the generation of documentation portals, code, and also led to a bunch of excellent API management services like Apigee, Mulesoft, Kong, and...
Fran Mendez
Founder at AsyncAPI Initiative & Director Of Engineering @getpostman
API Showdown: REST vs. GraphQL vs. gRPC – Which Should You Use?
Tuesday Nov 9 / 02:10PM EST
When architecting an API, one of the major decisions is choosing the appropriate communication technology and protocol. Every solution comes with trade-offs, so how do you find the right fit for your needs? The three panelists will each be a representative for one of today's popular...
Alex Borysov
Senior Software Engineer @Netflix
Matt McLarty
Software Architect, Author, Global Leader of API Strategy @MuleSoft
Michelle Garrett
Software Engineer @Twitter