REST - The ignored parts

on YouTube ↗01h 01m

" summary

Claim: most APIs calling themselves REST are just JSON over HTTP because teams ignore HTTP's constraints like HATEOAS and proper versioning. Demo uses .NET Core + Entity Framework + SQL Server and Postman to show concrete fixes: enable content negotiation and XML formatter, use HEAD/OPTIONS, return 201 with Location, configure automatic validation (validation problem details / application/problem+json / 422), and use API versioning via header or query instead of version-in-path. Toolbox shown: jsonapi.netcore, ASP.NET Core API versioning and ConfigureApiBehavior; some demos ran and produced 201/406/200 as expected while a few live-demo hiccups occurred. HATEOAS ignored

AI-written summary · about

" chapters (17)

1. 0:00Start
2. 1:15Agenda
3. 1:34What Is Rest Representational State Transfer
4. 4:35Caching
5. 5:11The Uniform Interface
6. 6:05Client Server
7. 7:34The Caching
8. 11:17Identify Resources
9. 15:03Self-Descriptive Messages
10. 15:37Media Types
11. 17:03Endpoints
12. 20:45Status Codes
13. 26:58Describe Errors
14. 41:09Browser Accept Header
15. 54:48Versioning
16. 55:54Default Api Version
17. 56:47Api Versioning Error Provider

" related talks

• 01h 01mNever RESTing – RESTful API Best Practices using ASP.NET Web APISpencer Schneidenbach · NDC London 2017
• 37mREST, for real!Vincenzo Chianese · Codemotion Milan 2017
• 01h 39mLet’s have some Effective RESTMohamed Taman · Global Summit for Java Devs 2020
• 42mLet’s Have Some Effective REST!Mohamed Taman · JCON Europe 2023
• 41mREST Again? Oh, Come On!Stas Sultanov · .NET fwdays'18
• 47mAPIs Exposed!Layla Porter · NDC London 2019
• 50mThe Fashion for REST - Creating Beautiful APIsTomek Cejner · Confitura 2013
• 47mBuilding APIs your users will want to useRyan Coates · PowerShell + DevOps Global Summit 2024