Why REST?

Mhelvin Reyes
Dec 7, 2017 · 1 min read

Client-Server

By separating the user interface concerns from the data storage concerns, we improve the portability of the user interface across multiple platforms and improve scalability by simplifying the server components

Stateless

request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server

Cache

the potential to partially or completely eliminate some interactions

Uniform Interface

REST is defined by four interface constraints:

  • identification of resources;
  • URI
  • manipulation of resources through representations;
  • HTTP, HTTP METHOD, & URI
  • self-descriptive messages;
  • text/plain
  • text/html
  • image/jpeg
  • image/png
  • audio/mpeg
  • audio/ogg
  • audio/*
  • video/mp4
  • application/octet-stream
  • and, hypermedia as the engine of application state.
  • World wide web

Layered System

each component cannot “see” beyond the immediate layer with which they are interacting

Code-On-Demand

Allowing features to be downloaded after deployment improves system extensibility

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade