What is Restful/Rest web services

Googling the term "resful services" will give you loads of results from the web. They're are plenty of articles that talks about REST Services and most of them can be found on the web. Here's one example: http://www.c-sharpcorner.com/UploadFile/1492b1/restful-day-1-enterprise-level-application-architecture-wit/

To give you quick overview, REST is a client-server architecture which (among other things) leverages the full capacity of the HTTP protocol. REST are very popular and widely used in any form of applications as any client apps (Mobile, Web, Desktop or Console) can consume them for as long as it supports HTTP protocols.

Some relevant points in REST taken from stackoverflow discussion:

Each URL on the server represents a resource; either a collection resource or an element resource.
- A collection resource would be available at a URL like http://restful.ex/items/which would be a representation of a list of items.
- A element resource would be available at a URL like http://restful.ex/items/2which would be a representation of a single item, identified by 2.
Different HTTP methods are used for different CRUD operations:
- a GET is a read operation
- a PUT is a write/modify operation
- a POST is a create/new operation
- a DELETE is a... ok, that one is kind of self-explanatory.
State (or rather, client context) is not stored on the server-side; all state is in the representations passed back and forth by the client's requests and the server's responses.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Gokhul Varman9y ago
Please refer the link for full explanation:https://www.slideshare.net/hburakcetinkaya/rest-res-tful-web-services
Vincent Maverick Durano9y ago
Googling the term "resful services" will give you loads of results from the web. They're are plenty of articles that talks about REST Services and most of them can be found on the web. Here's one example: http://www.c-sharpcorner.com/UploadFile/1492b1/restful-day-1-enterprise-level-application-architecture-wit/

To give you quick overview, REST is a client-server architecture which (among other things) leverages the full capacity of the HTTP protocol. REST are very popular and widely used in any form of applications as any client apps (Mobile, Web, Desktop or Console) can consume them for as long as it supports HTTP protocols.
Some relevant points in REST taken from stackoverflow discussion:
Each URL on the server represents a resource; either a collection resource or an element resource.
A collection resource would be available at a URL like http://restful.ex/items/which would be a representation of a list of items.
A element resource would be available at a URL like http://restful.ex/items/2which would be a representation of a single item, identified by 2.
Different HTTP methods are used for different CRUD operations:
a GET is a read operation
a PUT is a write/modify operation
a POST is a create/new operation
a DELETE is a... ok, that one is kind of self-explanatory.
State (or rather, client context) is not stored on the server-side; all state is in the representations passed back and forth by the client's requests and the server's responses.