REST Introduction
5 comments
Microsoft has a decent document regarding REST API design[1]. The main gist is, HTTP Verbs tell the application what to do with the object the URI Path points to.
1: https://docs.microsoft.com/en-us/azure/architecture/best-pra...
1: https://docs.microsoft.com/en-us/azure/architecture/best-pra...
If you wish to see everything in one single doc page.
https://github.com/Microsoft/api-guidelines/blob/vNext/Guide...
https://github.com/Microsoft/api-guidelines/blob/vNext/Guide...
Thanks all, this is probably a very good starting point
I strongly recommend Designing Web APIs: http://shop.oreilly.com/product/0636920123880.do
You can jump ahead to the Representational State Transfer chapter to get a good overview of REST, then read whichever chapters seem interesting or solve whichever problems you're facing.
You can jump ahead to the Representational State Transfer chapter to get a good overview of REST, then read whichever chapters seem interesting or solve whichever problems you're facing.
Can't find that chapter here:
https://www.amazon.com/Designing-Web-APIs-Building-Developer...
am I looking at a the right edition ?
am I looking at a the right edition ?
Sorry, it's under Chapter 2. API Paradigms / Request-Response APIs / Representational State Transfer
There's two kinds of REST. REST as most developers misunderstand it, and REST as Roy Fielding, inventor of REST, understands it.
For the former you can read the Microsoft REST guidelines, for the latter I suggest getting Mike Amundsen's RESTful Web APIs book.
If you do go with the latter be prepared for a lot of frustration with those who went with the former.
For the former you can read the Microsoft REST guidelines, for the latter I suggest getting Mike Amundsen's RESTful Web APIs book.
If you do go with the latter be prepared for a lot of frustration with those who went with the former.
Can you explain what is wrong with most people's implementation of rest?
and https://8thlight.com/blog/jason-desrosiers/2018/05/30/the-hy... if you are wondering what that means
Check this site https://restfulapi.net/
It has information about RESTful API Designs, HATEOAS, Caching, Compression, etc.
Very useful
Any recommendations ?