REST constraints and principles in Rest API - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does REST stand for?

REST stands for Representational State Transfer. It is a style for designing networked applications.

intermediate

Name the six main constraints of REST.

The six main REST constraints are:<br>1. Client-Server<br>2. Stateless<br>3. Cacheable<br>4. Uniform Interface<br>5. Layered System<br>6. Code on Demand (optional)

beginner

Explain the Client-Server constraint in REST.

Client and server are separate. The client handles the user interface, and the server manages data and logic. This separation allows each to evolve independently.

beginner

What does it mean that REST is stateless?

Each request from client to server must contain all information needed to understand and process it. The server does not store client context between requests.

intermediate

Why is the Uniform Interface constraint important in REST?

It simplifies and decouples the architecture, allowing each part to evolve independently. It defines a standard way to communicate using resources and HTTP methods.

Which REST constraint requires that each request contains all information needed to process it?

A Cacheable

B Layered System

C Stateless

D Client-Server

The Stateless constraint means the server does not keep client state between requests. Each request must be self-contained.

What is the purpose of the Cacheable constraint in REST?

A To separate client and server

B To allow clients to store responses for reuse

C To allow code to be sent from server to client

D To enforce a uniform interface

Cacheable means responses can be stored by clients or intermediaries to improve performance by reusing data.

Which HTTP method is NOT typically part of the REST uniform interface?

A GET

B POST

C DELETE

D CONNECT

CONNECT is not commonly used in REST APIs. GET, POST, DELETE are standard methods for resource operations.

What does the Layered System constraint allow in REST architecture?

A Clients cannot tell if they are connected directly to the end server or an intermediary

B Servers must store client state

C Clients and servers must be tightly coupled

D Code can be downloaded and executed on the client

Layered System allows intermediaries like proxies or gateways to be used without clients knowing.

Which REST constraint is optional and allows servers to send executable code to clients?

A Code on Demand

B Cacheable

C Stateless

D Uniform Interface

Code on Demand lets servers extend client functionality by sending code like JavaScript, but it is optional.

List and briefly explain the six REST constraints.

Think about how REST organizes communication and data handling.

Why is statelessness important in REST APIs? How does it affect server design?

Consider what happens if the server crashes or handles many clients.