Why REST constraints and principles in Rest API? - Purpose & Use Cases

The Big Idea

Discover how simple rules can turn a messy app into a smooth-running machine!

The Scenario

Imagine you have a website where users can view, add, and delete items. Without a clear way to organize these actions, you write different code for each page, mixing how data is sent and received. Every time you add a new feature, you have to rewrite parts of your code, and it becomes confusing to keep track of what each part does.

The Problem

This manual approach is slow because you repeat similar code everywhere. It's easy to make mistakes, like sending wrong data or forgetting to update some parts. When your app grows, it becomes a tangled mess that's hard to fix or improve. Sharing your work with others is also difficult because there's no common way to understand how your app works.

The Solution

REST constraints and principles give you a simple, clear set of rules to organize your app's communication. By following these rules, your app becomes easier to build, understand, and maintain. Each part has a clear role, and data flows in a predictable way. This makes your app faster to develop and easier to grow.

Before vs After

✗ Before

function getData() { fetch('/data'); } // mixed logic everywhere

✓ After

GET /items HTTP/1.1 // clear, standard way to get items

What It Enables

REST principles enable building apps that are simple, scalable, and easy to connect with other systems.

Real Life Example

Think of an online store where customers can browse products, add them to a cart, and place orders. REST makes sure each action (viewing, adding, ordering) follows a clear pattern, so the store works smoothly and can grow without confusion.

Key Takeaways

Manual coding without rules leads to confusion and errors.

REST constraints provide a clear, organized way to build web services.

Following REST makes apps easier to develop, maintain, and scale.

Practice

1. Which of the following is a key constraint of REST that ensures each request from client to server must contain all the information needed to understand and process the request?

easy

A. Cacheability

B. Layered System

C. Statelessness

D. Code on Demand

Solution

1. Step 1: Understand the meaning of statelessness in REST

   Statelessness means the server does not store any client context between requests. Each request must be self-contained.

2. Step 2: Match the constraint to the description

   The description says each request must have all needed info, which matches statelessness.

3. Final Answer:

   Statelessness -> Option C

4. Quick Check:

   Request self-contained = Statelessness [OK]

Hint: Requests must be independent and self-contained [OK]

Common Mistakes:

• Confusing cacheability with statelessness
• Thinking layered system means stateless
• Assuming code on demand is required

2. Which HTTP method is NOT considered safe and idempotent according to REST principles?

easy

A. POST

B. PUT

C. GET

D. DELETE

Solution

1. Step 1: Recall safe and idempotent HTTP methods

   GET, PUT, and DELETE are idempotent; GET is safe. POST is neither safe nor idempotent.

2. Step 2: Identify the method that is not safe and idempotent

   POST changes server state and can create multiple resources, so it is not idempotent or safe.

3. Final Answer:

   POST -> Option A

4. Quick Check:

   POST is not safe or idempotent [OK]

Hint: POST changes data and is not idempotent [OK]

Common Mistakes:

• Thinking PUT is unsafe
• Confusing DELETE as unsafe
• Assuming GET modifies data

3. Given the following REST API response headers, which constraint is being applied?

Cache-Control: max-age=3600
ETag: "abc123"

medium

A. Cacheability

B. Uniform Interface

C. Statelessness

D. Client-Server

Solution

1. Step 1: Analyze the headers Cache-Control and ETag

   Cache-Control and ETag headers control how responses are cached by clients or intermediaries.

2. Step 2: Identify the REST constraint related to caching

   Cacheability means responses can be stored and reused to improve performance.

3. Final Answer:

   Cacheability -> Option A

4. Quick Check:

   Cache headers = Cacheability [OK]

Hint: Cache headers indicate cacheability constraint [OK]

Common Mistakes:

• Confusing cache headers with statelessness
• Thinking uniform interface relates to headers
• Assuming client-server means caching

4. You have a REST API that stores user sessions on the server between requests. Which REST constraint is violated and how can you fix it?

medium

A. Uniform Interface; change URL structure

B. Cacheability; disable caching on responses

C. Layered System; remove intermediaries

D. Statelessness; move session data to client or include in each request

Solution

1. Step 1: Identify the violated constraint

   Storing session data on server between requests breaks statelessness because server keeps client state.

2. Step 2: Suggest a fix to restore statelessness

   Move session info to client (like tokens) or send all needed info in each request.

3. Final Answer:

   Statelessness; move session data to client or include in each request -> Option D

4. Quick Check:

   Server session storage breaks statelessness [OK]

Hint: No server session storage means statelessness [OK]

Common Mistakes:

• Confusing cacheability with session storage
• Thinking layered system relates to sessions
• Trying to fix by changing URLs

5. You want to design a REST API that allows clients to update user profiles partially without sending the entire profile data. Which HTTP method and REST principle best support this requirement?

hard

A. PUT method and Uniform Interface constraint

B. PATCH method and Uniform Interface constraint

C. POST method and Statelessness constraint

D. DELETE method and Cacheability constraint

Solution

1. Step 1: Identify the HTTP method for partial updates

   PATCH is designed for partial updates, unlike PUT which replaces entire resource.

2. Step 2: Connect the method to the REST principle

   Uniform Interface means using standard methods consistently; PATCH fits this principle for partial updates.

3. Final Answer:

   PATCH method and Uniform Interface constraint -> Option B

4. Quick Check:

   Partial update = PATCH + Uniform Interface [OK]

Hint: Partial update uses PATCH and uniform interface [OK]

Common Mistakes:

• Using PUT for partial updates
• Confusing POST with PATCH
• Linking DELETE to updates