qetr1ck-op / RESTful-Web-Services-with-Node.js-and-Express

#What is REST anyway?

The term REpresentational State Transfer came from a dissertation written by Roy Fielding back in 2000. He described a series of constraints that should be in place whenever two systems talk to each other.

So ultimately REST is just a series of rules in place for your server, so everyone who uses your service understand what it does and how it works.

#The Uniform interface

Whenever you're dealing with RESTful service you'll be dealing with a resource or resources and all that really means is you're dealing with with nouns.

Uniform resource are built around things, not actions.

For example dealing with books as a resource, the url be http://domain/books. With authors it would be /authors.

The another part of uniform interface are HTTP verbs that we use in our request will dictate the type of activity we're trying to do on the resource:

• GET will simply request data (/books get all or /books/:id a unique book)
• POST uses to add data (/books add new book)
• DELETE will remove an entity (books/:id)
• PUT is used for update or replace a resource
• PATCH updates piece of that resource

The last part of interface is HATEOS (Hypermedia as the Engine of Application State). Basically all that means is that in each request will be a set of hyperlinks that you can use to navigate the API. In example, what type of actions you can do on a particular resource.