REST stands for representational state transfer, and is a set of architectural styles that dictates the manners and patterns in which you construct your API. REST is nothing new; you are probably already well attuned to it because that's how the World Wide Web is structured, so don't let the terminology alienate you.
There are six requirements for REST:
- Client-server: Defines a clear separation of concerns (SoC) between client and server. The client should provide the user interface, while the server provides the data.
- Stateless: No transient information about the client should be held on the server. In other words, the server should not persist client sessions; if sessions need to be persisted, it must be done on the client. ...