REST

Stands for representational state transfer. REST is a style of software architecture that systems need in order to process and execute various software elements. REST interacts with HTTP (and was in fact developed in tandem with HTTP) on the World Wide Web in order to send data via XML, and acts as web architecture that establishes and dictates behavior of programming languages. REST architecture consists of interactions between clients that make requests and servers that parse requests in order to generate pertinent responses. There are 6 constraints that REST APIs must follow in order to be in compliance with architectural style. They are as follows:

• Client-server: Clients exist apart from servers by a standardized interface system.
• Stateless: No client information is stored on the server between requests.
• Cacheable: Clients are able to cache responses.
• Layered system: Clients are unable to tell whether they are connected directly to the end server or intermediary.
• Code on demand: Optional constraint, servers can temporarily modify or extend functionality for execution by transferring logic.
• Uniform interface: Uniform interface between clients and servers.