Completed
REST IS STATE-MACHINE OVER HTTP
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
GraphQL, gRPC or REST - Resolving the API Developer's Dilemma
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 MY TWITTER TIMELINE IS A TYRE FIRE
- 3 API COMMUNITY IS SMALL WE NEED TO WORK TOGETHER
- 4 NO! THAT'S NOT THE WAY APIS WORK!
- 5 THERE IS NO UNIVERSAL BEST API STYLE
- 6 THERE IS ALWAYS A BEST API STYLE FOR YOUR PROBLEM
- 7 CONSTRAINTS = PROPERTIES
- 8 LET'S DISPEL SOME MYTHS
- 9 REST IS STATE-MACHINE OVER HTTP
- 10 FRIENDS DON'T LET FRIENDS BUILD RESTISH APIS
- 11 GRAPHQL BREAKS CACHING
- 12 WHAT KIND OF CACHING?
- 13 GET WITH PERSISTED QUERIES
- 14 OVER/UNDER FETCHING
- 15 HELLO HTTP/2, GOODBYE NETWORK HACKS
- 16 GRAPHQL IS NOT JUST ABOUT NETWORK EFFICIENCY
- 17 THE VALUE OF GRAPHQL IS THE SUM OF IT'S PARTS
- 18 GRAPHQL ELIMINATES THE NEED FOR VERSIONING
- 19 VERSIONING IS A STRATEGY NOT A REQUIREMENT
- 20 VERSIONING VS GRACEFUL EVOLUTION
- 21 GRACEFUL EVOLUTION SHOULD BE THE GOAL
- 22 YOU CANNOT OVER COMMUNICATE WITH USERS!
- 23 TOLERANT READERS ARE MODEL CLIENTS
- 24 BUG FOR BUG COMPATIBILITY
- 25 DOMAIN MODELLING IS PURELY A REST CONCERN
- 26 GRAPHQL DELAYS THE LAST RESPONSIBLE MOMENT FOR IDENTIFYING USER NEEDS
