PANEL DISCUSSION + Live Q&A
API Showdown: REST vs. GraphQL vs. gRPC – Which Should You Use?
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 technologies: REST, GraphQL, and gRPC. We'll cover origin stories, what it takes to get started, when each is the right tool for the job, and when it's absolutely the wrong tool for the job.
Speaker
Alex Borysov
Senior Software Engineer @Netflix
Alex is currently a senior software engineer at Netflix, where he is working on building a unified global digital Studio that powers the effective production of Netflix content. Prior to joining Netflix, Alex had designed, implemented, and run various World-scale distributed systems,...
Read moreFind Alex Borysov at:
Speaker
Matt McLarty
Software Architect, Author, Global Leader of API Strategy @MuleSoft
Matt McLarty is the Global Field CTO for MuleSoft, a Salesforce company. He works closely with organizations to define digital strategies, as well as design and implement enterprise-grade API and microservices solutions. An experienced software architect, Matt has worked extensively in the...
Read moreFind Matt McLarty at:
Speaker
Michelle Garrett
Software Engineer @Twitter
Michelle Garrett is a Software Engineer at Twitter, where she is part of the team building Twitter's large scale GraphQL API. Prior to Twitter, Michelle worked on a GraphQL implementation at Condé Nast, powering the international Vogue websites. Michelle is an organiser of Node Girls, which...
Read moreDate
Tuesday Nov 9 / 02:10PM EST (40 minutes)
Track
Topics
APIGraphQLgRPCRESTArchitectureAdd to Calendar
Add to calendarShare
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
A Standardized, Specification-Driven API Lifecycle
Tuesday Nov 9 / 01:10PM EST
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...
Kin Lane
Chief Evangelist @Postman