REST principles
REST is modeled around starting with nothing and then adding constraints. We will apply constraints to a software architecture, and your architecture will become RESTful.
Client - server
Note that throughout Roy T. Fielding's work, he does not mention that REST has to be applied to the HTTP protocol. In our case, a client server will be the browser as the client and IIS as the server.
Note that the separation of the client and server allows abstraction. These two components can be built independently as well as deployed independently.
Stateless
The next constraint to add is stateless. The server should not contain any state of workflow. In this way, the client is the driver of the information that it wants. When the client asks the server for data, the client needs to pass all the relevant information to the server. This method of designing software creates an abstraction, where the server is unaware of the client; it creates a loose couple design, which is conducive to changes...
