What is REST & how web api is Rest

How to define Rest with example for each points.

one rest principal is not clear to me that is Uniform Interface

what is Uniform Interface and how to explain this points.

how to explain that web api is restful architecture.

i read this article https://blogs.msdn.microsoft.com/martinkearn/2015/01/05/introduction-to-rest-and-net-web-api/

thanks

Hi,

As REST says web applicaitons should use HTTP as it was envisoned or the way it was started. Should use htpp verbs for getting, saving and modifying data.

Uniform interface - A resource in system should have only one logical URI, and then should provide way to fetch related or additional data. It’s always better to synonymise a resource with a web page.

All resources should be accessible through a common approach such as HTTP GET.

So as per i understand it has to be simple enough to access. One API leads to one URI that yiels information.

More Explaination here -

https://forums.asp.net/post/6096020.aspx

Other contraints -:

2. Client–server - Client application and server application must be able to evolve separately without any dependency

on each other. Client should know only resource URIs and that’s all.

3. Stateless - Server will not store anything about latest HTTP request client made. It will treat each and every request as new. No session, no history.

Client is responsible for managing the state of application.

4. Cacheable - Caching can be implemented server side or client side. Can improve performance.

5. Layered system - Supports layered architecture. Develop apis ondifferent layers, client cannot confirm whether it is connected directly to the end server, or to an intermediary along the way.

6. Code on demand (optional) - Majorly REST works with static data in return i.e.e XML or JSON. But it can also retunr executable code. This is optional

More details - https://restfulapi.net/rest-architectural-constraints/

Thanks.

3 Replies

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

Tushar Dikshit8y ago
Accepted answer
Hi,
As REST says web applicaitons should use HTTP as it was envisoned or the way it was started. Should use htpp verbs for getting, saving and modifying data.

Uniform interface - A resource in system should have only one logical URI, and then should provide way to fetch related or additional data. It’s always better to synonymise a resource with a web page.

All resources should be accessible through a common approach such as HTTP GET.
So as per i understand it has to be simple enough to access. One API leads to one URI that yiels information.

More Explaination here -

https://forums.asp.net/post/6096020.aspx

Other contraints -:

2. Client–server - Client application and server application must be able to evolve separately without any dependency
on each other. Client should know only resource URIs and that’s all.

3. Stateless - Server will not store anything about latest HTTP request client made. It will treat each and every request as new. No session, no history.
Client is responsible for managing the state of application.

4. Cacheable - Caching can be implemented server side or client side. Can improve performance.

5. Layered system - Supports layered architecture. Develop apis ondifferent layers, client cannot confirm whether it is connected directly to the end server, or to an intermediary along the way.

6. Code on demand (optional) - Majorly REST works with static data in return i.e.e XML or JSON. But it can also retunr executable code. This is optional

More details - https://restfulapi.net/rest-architectural-constraints/

Thanks.
Tridip Bhattacharjee8y ago
i already read that link but still not clear what they try to means Uniform Interface ?

if possible discuss here with a good example. thanks
Satish Kumar Vadlavalli8y ago
https://stackoverflow.com/questions/25172600/rest-what-exactly-is-meant-by-uniform-interface