HTTP methods and CRUD mapping in Node.js - Step-by-Step Execution

Concept Flow - HTTP methods and CRUD mapping

Client sends HTTP request

↓

Server receives request

↓

Check HTTP method

↓

Perform CRUD operation

↓

Send response back to client

The server receives an HTTP request, checks its method (GET, POST, PUT, DELETE), maps it to the corresponding CRUD operation, performs it, then sends a response.

Execution Sample

Node.js

app.get('/items', (req, res) => {
  res.send('Read items');
});

This code handles a GET request to '/items' by sending back a message indicating a read operation.

Execution Table

Step	HTTP Method	URL	Action Taken	CRUD Operation	Response Sent
1	GET	/items	Matched GET route	Read	'Read items'
2	POST	/items	Matched POST route	Create	'Create item'
3	PUT	/items/1	Matched PUT route	Update	'Update item 1'
4	DELETE	/items/1	Matched DELETE route	Delete	'Delete item 1'
5	PATCH	/items/1	No route matched	None	'404 Not Found'

💡 Execution stops after sending response for each request.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
HTTP Method	None	GET	POST	PUT	DELETE	PATCH
URL	None	/items	/items	/items/1	/items/1	/items/1
CRUD Operation	None	Read	Create	Update	Delete	None
Response Sent	None	'Read items'	'Create item'	'Update item 1'	'Delete item 1'	'404 Not Found'

Key Moments - 3 Insights

Why does a PATCH request get a '404 Not Found' response?

Because the server code only defines routes for GET, POST, PUT, and DELETE methods. PATCH is not handled, so no matching route is found (see execution_table row 5).

How does the server know which CRUD operation to perform?

It checks the HTTP method of the request and maps GET to Read, POST to Create, PUT to Update, and DELETE to Delete (see concept_flow and execution_table).

What happens if the URL does not match any route?

The server sends a '404 Not Found' response because it cannot find a matching route to handle the request (implied in execution_table row 5).

Visual Quiz - 3 Questions

Look at the execution_table, what CRUD operation is performed at Step 3?

A Update

B Delete

C Create

D Read

💡 Hint

Check the 'CRUD Operation' column at Step 3 in the execution_table.

At which step does the server respond with '404 Not Found'?

A Step 2

B Step 3

C Step 5

D Step 1

💡 Hint

Look for the 'Response Sent' column showing '404 Not Found' in the execution_table.

If a new route for PATCH was added to update partially, what would change in the execution_table?

A Step 4 would change to '404 Not Found'.

B Step 5 would show a matched route and a CRUD operation.

C Step 1 would change to 'Create'.

D No changes would happen.

💡 Hint

Consider how the server handles PATCH requests in the execution_table row 5.

Concept Snapshot

HTTP methods map to CRUD:
GET = Read
POST = Create
PUT = Update
DELETE = Delete
Server routes handle these methods to perform CRUD operations.
Unmatched methods return 404 Not Found.

Full Transcript

This visual execution shows how HTTP methods correspond to CRUD operations in a Node.js server. When a client sends a request, the server checks the HTTP method. GET requests trigger reading data, POST creates new data, PUT updates existing data, and DELETE removes data. If the method is not handled, like PATCH here, the server responds with 404 Not Found. The execution table traces each step, showing the method, URL, action, CRUD operation, and response. Variables track the method, URL, CRUD operation, and response at each step. Key moments clarify why some requests fail and how the server maps methods to CRUD. The quiz tests understanding by referencing the execution table and variable changes.

Practice

1. Which HTTP method is typically used to retrieve data from a server in a RESTful API?

easy

A. GET

B. POST

C. PUT

D. DELETE

Solution

1. Step 1: Understand HTTP methods and their purposes

   In RESTful APIs, GET is used to read or retrieve data from the server.

2. Step 2: Match the method to the action

   POST creates, PUT updates, and DELETE removes data, so only GET fits retrieving data.

3. Final Answer:

   GET -> Option A

4. Quick Check:

   Read = GET [OK]

Hint: GET is for reading data, like looking at a book [OK]

Common Mistakes:

• Confusing POST with GET
• Using DELETE to fetch data
• Thinking PUT retrieves data

2. Which of the following Express route definitions correctly handles updating a resource using the HTTP method for update?

easy

A. app.get('/item/:id', handler)

B. app.post('/item/:id', handler)

C. app.put('/item/:id', handler)

D. app.delete('/item/:id', handler)

Solution

1. Step 1: Identify the HTTP method for updating

   Updating a resource uses the PUT method in RESTful APIs.

2. Step 2: Match Express method to HTTP method

   Express uses app.put() to handle PUT requests, so app.put('/item/:id', handler) is correct.

3. Final Answer:

   app.put('/item/:id', handler) -> Option C

4. Quick Check:

   Update = PUT = app.put() [OK]

Hint: Use app.put() for updates in Express routes [OK]

Common Mistakes:

• Using app.post() for updates
• Using app.get() for updates
• Confusing app.delete() with update

3. Consider this Express code snippet:

app.delete('/user/:id', (req, res) => {
  res.send(`Deleted user ${req.params.id}`);
});

// Client sends DELETE request to /user/42

What will the server respond with?

medium

A. "Updated user 42"

B. "Deleted user 42"

C. "Created user 42"

D. 404 Not Found

Solution

1. Step 1: Understand the route and HTTP method

   The route listens for DELETE requests on /user/:id. The client sends a DELETE request to /user/42.

2. Step 2: Analyze the response sent

   The handler sends back the string Deleted user 42 using the id from the URL.

3. Final Answer:

   "Deleted user 42" -> Option B

4. Quick Check:

   DELETE request responds with deletion message [OK]

Hint: DELETE routes respond with deletion confirmation [OK]

Common Mistakes:

• Confusing DELETE with POST response
• Expecting 404 instead of success message
• Mixing up URL parameters

4. What is wrong with this Express route for creating a new item?

app.get('/items', (req, res) => {
  // code to add new item
  res.send('Item created');
});

medium

A. Missing route parameter for item ID

B. Route path should be '/item' not '/items'

C. Response message is incorrect

D. GET method should not be used to create data

Solution

1. Step 1: Identify the HTTP method used

   The route uses GET, which is meant for reading data, not creating.

2. Step 2: Match method to CRUD action

   Creating new data should use POST, so using GET here is incorrect.

3. Final Answer:

   GET method should not be used to create data -> Option D

4. Quick Check:

   Create = POST, not GET [OK]

Hint: Use POST to create, not GET [OK]

Common Mistakes:

• Using GET to create resources
• Ignoring HTTP method semantics
• Assuming route path is the issue

5. You want to build an Express API that allows clients to create, read, update, and delete "products". Which set of route definitions correctly maps HTTP methods to CRUD actions?

hard

A. app.post('/products', createHandler); app.get('/products/:id', readHandler); app.put('/products/:id', updateHandler); app.delete('/products/:id', deleteHandler);

B. app.get('/products', createHandler); app.post('/products/:id', readHandler); app.put('/products', updateHandler); app.delete('/products', deleteHandler);

C. app.put('/products', createHandler); app.get('/products/:id', readHandler); app.post('/products/:id', updateHandler); app.delete('/products/:id', deleteHandler);

D. app.delete('/products', createHandler); app.put('/products/:id', readHandler); app.post('/products/:id', updateHandler); app.get('/products/:id', deleteHandler);

Solution

1. Step 1: Match each CRUD action to correct HTTP method

   Create = POST, Read = GET, Update = PUT, Delete = DELETE.

2. Step 2: Check route paths and handlers

   app.post('/products', createHandler); app.get('/products/:id', readHandler); app.put('/products/:id', updateHandler); app.delete('/products/:id', deleteHandler); uses POST /products for create, GET /products/:id for read, PUT /products/:id for update, and DELETE /products/:id for delete, which is correct.

3. Final Answer:

   app.post('/products', createHandler); app.get('/products/:id', readHandler); app.put('/products/:id', updateHandler); app.delete('/products/:id', deleteHandler); -> Option A

4. Quick Check:

   POST=create, GET=read, PUT=update, DELETE=delete [OK]

Hint: Remember CRUD: POST, GET, PUT, DELETE order [OK]

Common Mistakes:

• Mixing POST and GET methods
• Using wrong paths for actions
• Assigning update to POST instead of PUT