REST

Tags: #◇Web Development #◇CCAPDEV #◇REST #◇Conceptual #◇M4

---

◇Overview

Extracted notes for REST covering both theoretical and practical elements.

◇Key Definitions

What is an API An API provides aw means for different applications to communicate and transfer information to one another
REST REST, which stands for Representational State Transfer, is an architectural style that focuses on producing efficient, reliable, and scalable distributed systems. https://developer.mozilla.org/en-US/docs/Glossary/REST
Guiding Principles of REST Client-Server decoupling Separating the user interface concerns from the data storage concerns improves the portability of the user interface across multiple platforms and improve scalability by simplifying the server components. https://www.ibm.com/cloud/learn/rest-apis
Guiding Principles of REST Statelessness Each request from the clients must contain all the information necessary to understand the request. Session state is therefore kept entirely on the client. https://www.ibm.com/cloud/learn/rest-apis
Guiding Principles of REST Cacheable REST requires that the data within a response be implicitly or explicitly labeled as cacheable or non-cacheable. If a response is cacheable, then a client cache is given the right to reuse the response data for later, equivalent requests. https://www.ibm.com/cloud/learn/rest-apishttps://restfulapi.net/caching/

◇Theoretical Framework

Guiding Principles of REST
Uniform Interface
In order to obtain a uniform interface, multiple architectural constraints are needed to guide the behavior of components.
https://www.ibm.com/cloud/learn/rest-apis

Guiding Principles of REST
Layered System
The layered system style allows an architecture to be composed of hierarchical layers by constraining component behavior. As a rule of thumb, we do not assume that the client and server applications connect directly to each other.
https://www.ibm.com/cloud/learn/rest-apis

What is HTTP?
HTTP is the underlying protocol used by the World Wide Web
Hypertext Transfer Protocol
Follows the classic client-server model
Stateless protocol – the server does not keep any state or data when the response is sent to the client.

HTTP Request Methods
A set of verbs which indicate an action to be performed for a given resource
Addresses the ‘Uniform Interface’ constraint of REST
Methods:
GET
POST
PUT
PATCH
DELETE
https://www.restapitutorial.com/lessons/httpmethods.html

Side: Safe
A property of http methods wherein the request would not alter the state of the server.
This means that the request is read-only.
https://developer.mozilla.org/en-US/docs/Glossary/Safe/HTTP

◇References & Navigation

• Previous Topic: ◇Express
• Next Topic: ◇Handlebars
• Related Notes: ◇Client Server Architecture