Resource-based design thinking in Rest API - Step-by-Step Execution

Concept Flow - Resource-based design thinking

Identify Resources

↓

Define Resource URIs

↓

Design HTTP Methods

↓

Specify Representations

↓

Implement Stateless Interactions

↓

Test and Iterate

This flow shows how to design a REST API by focusing on resources, their URIs, HTTP methods, and representations.

Execution Sample

Rest API

GET /books/123 HTTP/1.1
Host: example.com

Response:
200 OK
{
  "id": 123, "title": "REST Basics"
}

This example shows a client requesting a book resource by its ID and receiving its details.

Execution Table

Step	Action	Request/Response	Resource URI	HTTP Method	Result
1	Client requests a resource	GET /books/123	/books/123	GET	Server receives request
2	Server locates resource	N/A	/books/123	GET	Resource found in database
3	Server prepares response	N/A	/books/123	GET	Resource data serialized as JSON
4	Server sends response	200 OK with JSON body	/books/123	GET	Client receives resource data
5	Client processes data	N/A	/books/123	GET	Data displayed or used in app
6	Client sends update	PUT /books/123 with JSON body	/books/123	PUT	Server updates resource
7	Server confirms update	200 OK	/books/123	PUT	Resource updated successfully
8	Client deletes resource	DELETE /books/123	/books/123	DELETE	Server deletes resource
9	Server confirms deletion	204 No Content	/books/123	DELETE	Resource removed
10	Client requests deleted resource	GET /books/123	/books/123	GET	404 Not Found
11	End	N/A	N/A	N/A	Resource lifecycle complete

💡 Resource lifecycle ends when client receives 404 after deletion.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	After Step 8	Final
Resource Exists	False	True	True	True	False	False
Resource Data	None	{"id":123,"title":"REST Basics"}	{"id":123,"title":"REST Basics"}	{"id":123,"title":"Updated Title"}	None	None
Response Status	None	None	200 OK	200 OK	204 No Content	404 Not Found

Key Moments - 3 Insights

Why does the client get a 404 Not Found after deleting the resource?

After step 8, the resource is deleted on the server, so when the client requests it again at step 10, the server cannot find it and returns 404 as shown in the execution_table.

What HTTP method is used to update a resource and why?

The PUT method is used to update a resource as shown in step 6 because it replaces the resource at the given URI with the new data.

Why must the server be stateless in resource-based design?

The server treats each request independently without storing client state, ensuring scalability and simplicity, as implied in the concept_flow step 'Implement Stateless Interactions'.

Visual Quiz - 3 Questions

Look at the execution_table, what is the HTTP method used at step 6?

A PUT

B GET

C POST

D DELETE

💡 Hint

Check the 'HTTP Method' column at step 6 in the execution_table.

At which step does the resource get deleted from the server?

A Step 4

B Step 8

C Step 10

D Step 2

💡 Hint

Look for the DELETE method action in the execution_table.

If the client tries to GET the resource after deletion, what response status will it receive?

A 200 OK

B 204 No Content

C 404 Not Found

D 500 Internal Server Error

💡 Hint

See the response status at step 10 in the execution_table.

Concept Snapshot

Resource-based design thinking focuses on modeling APIs around resources.
Each resource has a unique URI.
Use HTTP methods (GET, PUT, DELETE) to interact.
Server responses include resource representations.
Server is stateless; each request is independent.

Full Transcript

Resource-based design thinking is a way to build REST APIs by focusing on resources. Each resource has a unique address called a URI. Clients use HTTP methods like GET to read, PUT to update, and DELETE to remove resources. The server sends back data in formats like JSON. The server does not remember past requests, making it stateless. This approach helps create clear, scalable APIs. The execution table shows a client requesting a book resource, updating it, deleting it, and then trying to get it again, receiving a 404 error because it no longer exists.