Skip to main content

REST ↔ (standard)(model)(Paradigm) Client-Server Architecture to organize stateless Cachable Data Fetch

aka REST, Representational-State-Transfer, Representation-State-Transfer, RESTful, RESTful-API, REST-API

REST is logical way to build APIs to easier consume

REST applies a set of architecture constraints to standardize client-server communication

REST Resource​

any nameable object or rep to associate data

Resource-based​

of REST to expose API as logical resource-based URLs

uses [HTTP Verb](http-request)​

REST use HTTP Request to perform actions & NOT specify action inside URL

uses JSON​

usually REST use JSON to send data

Client-server model​

client sends data request to server, server responds with data

Stateless​

requests are transient, no require Client State/Server State to process request

Cachable​

should Cache reqs for perf

Uniform​

data access consistent for all users & systems

Separation of server & client​

REST Separation of Concerns for independent client-side & Backend code

References​

  1. RESTful ↔ Web App/Web Service that follows REST principle

  2. jsonplaceholder ↔ Online API to provide dummy REST JSON HTTP Response

  3. SOAP ↔ (standard)(model) alternative to REST to transfer messages/small data over HTTP as XML

  4. Separation of server & client ↔ REST Separation of Concerns for independent client-side & Backend code

  5. RESTful API ↔ Online API conform to REST

  6. Resource-based ↔ of REST to expose API as logical resource-based URLs

  7. uses [HTTP Verb](http-request) ↔ REST use HTTP Request to perform actions & NOT specify action inside URL

  8. uses [JSON](json) ↔ usually REST use JSON to send data

  9. API Route ↔ route to endpoint to access Online API, usually via REST

  10. Typesense API Client ↔ node/browser REST interface to abstract commands to typesense server instance