Creating documents in Express - Performance Optimization Steps

Performance: Creating documents

MEDIUM IMPACT

This affects server response time and how quickly the client receives the document content.

Generating and sending a document response to the client

Express

app.get('/doc', async (req, res) => {
  const doc = await generateLargeDocumentAsync();
  res.send(doc);
});

Asynchronous generation frees the event loop, allowing other requests to be handled concurrently.

📈 Performance GainReduces server blocking, improves response time and throughput under load

Generating and sending a document response to the client

Express

app.get('/doc', (req, res) => {
  const doc = generateLargeDocumentSync();
  res.send(doc);
});

Synchronous document generation blocks the event loop, delaying response and increasing server load.

📉 Performance CostBlocks server event loop, increasing response time by hundreds of milliseconds under load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous document creation	N/A (server-side)	N/A	N/A	[✗] Bad
Asynchronous document creation	N/A (server-side)	N/A	N/A	[✓] Good

Rendering Pipeline

Express creates the document on the server, then sends it over the network to the browser, which parses and renders it.

→Server Processing

→Network Transfer

→Browser Parsing

→Browser Rendering

⚠️ BottleneckServer Processing when document creation is slow or blocking

Core Web Vital Affected

LCP

This affects server response time and how quickly the client receives the document content.

Optimization Tips

1Avoid synchronous document generation to prevent blocking the server event loop.

2Use asynchronous or streaming methods to create documents efficiently.

3Monitor server response times to ensure fast document delivery and better LCP.

Performance Quiz - 3 Questions

What is the main performance issue with synchronous document creation in Express?

A It increases client-side rendering time

B It causes layout shifts in the browser

C It blocks the server event loop, delaying all requests

D It reduces network bandwidth

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the Time and TTFB (Time to First Byte) for the document request.

What to look for: Long TTFB indicates slow server document creation; shorter TTFB means faster server response.

Practice

1. Which Express method is used to handle creating new documents via HTTP POST requests?

easy

A. app.post()

B. app.get()

C. app.put()

D. app.delete()

Solution

1. Step 1: Understand HTTP methods in Express

   Express uses different methods like get, post, put, and delete to handle HTTP requests.

2. Step 2: Identify method for creating new data

   The post method is used to create new documents or data entries.

3. Final Answer:

   app.post() -> Option A

4. Quick Check:

   Creating documents = app.post() [OK]

Hint: Use app.post() for creating new data entries [OK]

Common Mistakes:

• Using app.get() instead of app.post()
• Confusing app.put() with app.post()
• Using app.delete() for creation

2. Which code snippet correctly enables JSON parsing middleware in Express to access req.body?

easy

A. app.use(express.urlencoded());

B. app.use(express.json());

C. app.use(bodyParser.text());

D. app.use(express.static('public'));

Solution

1. Step 1: Identify middleware for JSON parsing

   Express provides express.json() middleware to parse JSON request bodies.

2. Step 2: Match correct usage

   The correct way is app.use(express.json()); to enable JSON parsing.

3. Final Answer:

   app.use(express.json()); -> Option B

4. Quick Check:

   JSON parsing middleware = express.json() [OK]

Hint: Use app.use(express.json()) to read JSON body [OK]

Common Mistakes:

• Using express.urlencoded() for JSON data
• Using bodyParser.text() instead of JSON parser
• Forgetting to enable any parser middleware

3. What will be the HTTP status code sent when the following Express route successfully creates a document?

app.post('/items', (req, res) => {
  // Assume document creation here
  res.status(201).send('Created');
});

medium

A. 200

B. 500

C. 400

D. 201

Solution

1. Step 1: Understand HTTP status codes for creation

   Status code 201 means "Created" and is used when a new resource is successfully created.

2. Step 2: Check the code's status method

   The code uses res.status(201), so it sends status 201.

3. Final Answer:

   201 -> Option D

4. Quick Check:

   Creation success status = 201 [OK]

Hint: Use status 201 for successful creation responses [OK]

Common Mistakes:

• Assuming 200 means creation success
• Using 400 or 500 for successful creation
• Not setting status code explicitly

4. Identify the error in this Express route for creating a document:

app.post('/users', (req, res) => {
  const user = req.body;
  saveUser(user);
  res.send('User created');
});

medium

A. saveUser function is not asynchronous

B. Using res.send instead of res.json

C. Missing JSON parsing middleware to read req.body

D. Route should use app.get instead of app.post

Solution

1. Step 1: Check access to req.body

   Without JSON parsing middleware, req.body will be undefined.

2. Step 2: Identify missing middleware

   The code does not show app.use(express.json()), so req.body won't work.

3. Final Answer:

   Missing JSON parsing middleware to read req.body -> Option C

4. Quick Check:

   Missing express.json() causes req.body undefined [OK]

Hint: Always enable express.json() before accessing req.body [OK]

Common Mistakes:

• Thinking res.send must be res.json
• Using app.get for creation routes
• Assuming saveUser must be async here

5. You want to create an Express route that accepts JSON data to create a new product and respond with the created product including an ID. Which code snippet correctly implements this?

hard

A. app.post('/products', (req, res) => {
const product = req.body;
product.id = Date.now();
res.status(201).json(product);
});

B. app.get('/products', (req, res) => {
const product = req.body;
product.id = Date.now();
res.json(product);
});

C. app.post('/products', (req, res) => {
const product = req.query;
product.id = Date.now();
res.status(200).send(product);
});

D. app.post('/products', (req, res) => {
const product = req.body;
res.send('Product created');
});

Solution

1. Step 1: Use correct HTTP method and access JSON body

   The route uses app.post and accesses req.body which is correct for creating a product.

2. Step 2: Add an ID and respond with status 201 and JSON

   Assigning product.id = Date.now() simulates creating an ID. Responding with res.status(201).json(product) sends the created product with proper status.

3. Final Answer:

   Option A code snippet -> Option A

4. Quick Check:

   POST + req.body + status 201 + json response = app.post('/products', (req, res) => { const product = req.body; product.id = Date.now(); res.status(201).json(product); }); [OK]

Hint: Use app.post with req.body and res.status(201).json() [OK]

Common Mistakes:

• Using app.get instead of app.post
• Reading data from req.query instead of req.body
• Not sending status 201 on creation