Are REST APIs Still Relevant Today?
summary
Argues that REST remains relevant when teams use actual HTTP features — URLs, verbs, headers, response codes, content negotiation, caching and intermediaries — rather than re-embedding protocol semantics. Notes GraphQL lets frontends select nested fields but has no edge caching and limited content negotiation; gRPC gives bi-directional HTTP/2 high performance via protobuf and code generation but ties you to generators and fewer content types. Points to GitHub webhooks, Zapier and Kafka as examples of event integration and urges picking API style to fit the business, learn RFCs and operationalize.
AI-written summary · about
chapters (7)
related talks
21mThe REST API Myth
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
01h 01mAn Architect's Approach to API Strategies
06mBeyond REST: Exploring Modern API Paradigms
56mWhy REST APIs are dead and we should use GraphQL APIs
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
50mREST, gRPC, GraphQL, Webhooks: When to Use Each?
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma