GraphQL, gRPC or REST - Resolving the API Developer's Dilemma

Explore the intricacies of API design in this comprehensive conference talk that delves into the world of GraphQL, gRPC, REST, and WebHooks. Learn how to navigate the complex landscape of API technologies and architectural styles, cutting through the noise of online debates to make informed decisions for your specific development needs. Discover best practices, game-changing supporting technologies like HTTP/2, and strategies for delivering a world-class developer experience. Gain insights on determining API style suitability, supporting graceful evolution of API contracts, understanding supporting toolchains, and treating your API as a product. By the end of this session, acquire the knowledge to elevate your API design expertise and confidently implement various API styles in practice.

Intro
MY TWITTER TIMELINE IS A TYRE FIRE
API COMMUNITY IS SMALL WE NEED TO WORK TOGETHER
NO! THAT'S NOT THE WAY APIS WORK!
THERE IS NO UNIVERSAL BEST API STYLE
THERE IS ALWAYS A BEST API STYLE FOR YOUR PROBLEM
CONSTRAINTS = PROPERTIES
LET'S DISPEL SOME MYTHS
REST IS STATE-MACHINE OVER HTTP
FRIENDS DON'T LET FRIENDS BUILD RESTISH APIS
GRAPHQL BREAKS CACHING
WHAT KIND OF CACHING?
GET WITH PERSISTED QUERIES
OVER/UNDER FETCHING
HELLO HTTP/2, GOODBYE NETWORK HACKS
GRAPHQL IS NOT JUST ABOUT NETWORK EFFICIENCY
THE VALUE OF GRAPHQL IS THE SUM OF IT'S PARTS
GRAPHQL ELIMINATES THE NEED FOR VERSIONING
VERSIONING IS A STRATEGY NOT A REQUIREMENT
VERSIONING VS GRACEFUL EVOLUTION
GRACEFUL EVOLUTION SHOULD BE THE GOAL
YOU CANNOT OVER COMMUNICATE WITH USERS!
TOLERANT READERS ARE MODEL CLIENTS
BUG FOR BUG COMPATIBILITY
DOMAIN MODELLING IS PURELY A REST CONCERN
GRAPHQL DELAYS THE LAST RESPONSIBLE MOMENT FOR IDENTIFYING USER NEEDS