Why do we need REST?
In a typical client-server communication over a network, a server is connected to one or more clients using some protocols, that is, HTTP or TCP, and so on.
What is REST? Why is it becoming so popular over time? Is REST an alternative to Web Services? How can I make use of the .NET Framework to implement RESTful Services? We will answer these questions as we progress through the sections in this chapter.
REST is an architectural style for designing distributed applications that can intercommunicate. Note that REST is not a technology or a set of standards. Rather, it is a set of constraints that can be used to define a new style of architecture. Essentially, it is a client-server architectural style where the connections are stateless.
Note
The REST architecture style can be applied to other protocols as well. The word "stateless" applies to HTTP/HTTPS protocols. The REST architectural style is popular in the HTTP world and gives better results when used in combination with...