Session-based auth with express-session - Performance & Optimization

Performance: Session-based auth with express-session

MEDIUM IMPACT

This affects server response time and client perceived load due to session management overhead and cookie handling.

Managing user authentication state efficiently

Express

app.use(session({ secret: 'secret', resave: false, saveUninitialized: false }));

Avoids saving sessions that are not modified or uninitialized, reducing unnecessary session store operations.

📈 Performance GainSaves multiple session store writes per request, reducing server response time and improving INP

Managing user authentication state efficiently

Express

app.use(session({ secret: 'secret', resave: true, saveUninitialized: true }));

Resaving and saving uninitialized sessions cause unnecessary session store writes on every request, increasing server load and response time.

📉 Performance CostTriggers extra database or memory store writes per request, increasing server response time by 10-30ms per request depending on store

Performance Comparison

Pattern	Server Load	Session Store Writes	Response Delay	Verdict
resave: true, saveUninitialized: true	High	Many writes per request	Adds 10-30ms delay	[X] Bad
resave: false, saveUninitialized: false	Low	Writes only on session change	Minimal delay	[OK] Good

Rendering Pipeline

Session-based auth involves cookie parsing on request, server-side session lookup, and response generation. This adds processing before the server sends HTML or JSON, affecting interaction speed.

→Server Request Processing

→Network Transfer

→Client Rendering

⚠️ BottleneckServer Request Processing due to session store access and cookie parsing

Core Web Vital Affected

INP

This affects server response time and client perceived load due to session management overhead and cookie handling.

Optimization Tips

1Avoid resaving sessions unless data changes to reduce server load.

2Do not save uninitialized sessions to prevent unnecessary writes.

3Use fast session stores like in-memory or Redis for better response times.

Performance Quiz - 3 Questions

What session configuration reduces unnecessary session store writes in express-session?

A resave: true, saveUninitialized: true

B resave: false, saveUninitialized: false

C resave: true, saveUninitialized: false

D resave: false, saveUninitialized: true

DevTools: Network

How to check: Open DevTools Network panel, inspect requests to your server, check cookie headers and response times.

What to look for: Look for consistent cookie headers and low server response times; high delays may indicate session store bottlenecks.

Practice

1. What is the main purpose of using express-session in an Express app?

easy

A. To store user data on the server and keep users logged in across requests

B. To encrypt user passwords before saving to the database

C. To serve static files like images and CSS

D. To handle HTTP request routing

Solution

1. Step 1: Understand session purpose

   Sessions store user info on the server to remember users between requests.

2. Step 2: Identify express-session role

   The express-session middleware manages these sessions automatically.

3. Final Answer:

   To store user data on the server and keep users logged in across requests -> Option A

4. Quick Check:

   Session-based auth = store user data server-side [OK]

Hint: Sessions keep user info server-side to maintain login [OK]

Common Mistakes:

• Confusing sessions with password encryption
• Thinking sessions serve static files
• Mixing routing with session management

2. Which of the following is the correct way to initialize express-session middleware in an Express app?

easy

A. app.use(expressSession('keyboard cat'))

B. app.session({ secret: 'keyboard cat', resave: true })

C. app.use(session({ secret: 'keyboard cat', resave: false, saveUninitialized: true }))

D. app.sessionMiddleware({ secret: 'keyboard cat' })

Solution

1. Step 1: Recall express-session syntax

   The middleware is added with app.use(session({ options })).

2. Step 2: Check options correctness

   Options like secret, resave, and saveUninitialized are standard.

3. Final Answer:

   app.use(session({ secret: 'keyboard cat', resave: false, saveUninitialized: true })) -> Option C

4. Quick Check:

   Use app.use(session({...})) with options [OK]

Hint: Use app.use(session({ secret, resave, saveUninitialized })) [OK]

Common Mistakes:

• Using app.session instead of app.use
• Passing secret as a string directly
• Calling non-existent methods like sessionMiddleware

3. Given this Express route using express-session:

app.get('/dashboard', (req, res) => {
  if (req.session.user) {
    res.send(`Welcome, ${req.session.user}!`);
  } else {
    res.status(401).send('Please log in');
  }
});

// Assume req.session.user = 'Alice'

What will the server respond when a logged-in user visits /dashboard?

medium

A. Welcome, Alice!

B. Please log in

C. Error: req.session.user is undefined

D. Redirect to login page

Solution

1. Step 1: Check session user existence

   The code checks if req.session.user exists; here it is 'Alice'.

2. Step 2: Determine response

   Since user exists, it sends Welcome, Alice! as response.

3. Final Answer:

   Welcome, Alice! -> Option A

4. Quick Check:

   Session user present = welcome message [OK]

Hint: If req.session.user exists, show welcome message [OK]

Common Mistakes:

• Assuming undefined session user causes error
• Expecting redirect without code
• Confusing status 401 with success message

4. Consider this code snippet for session setup:

const session = require('express-session');
app.use(session({
  secret: 'secret123',
  resave: false
}));

What is the likely problem with this setup?

medium

A. Session middleware must be added after routes

B. Missing saveUninitialized option may cause sessions not to save properly

C. resave must be true to save sessions

D. The secret should be a number, not a string

Solution

1. Step 1: Review required session options

   While secret and resave are set, saveUninitialized is missing.

2. Step 2: Understand saveUninitialized role

   Without saveUninitialized, some sessions may not be saved, causing unexpected behavior.

3. Final Answer:

   Missing saveUninitialized option may cause sessions not to save properly -> Option B

4. Quick Check:

   Always set saveUninitialized option [OK]

Hint: Always include saveUninitialized in session config [OK]

Common Mistakes:

• Thinking secret must be a number
• Believing resave must be true
• Adding middleware after routes

5. You want to protect a route so only logged-in users can access it using express-session. Which middleware function correctly checks the session and redirects unauthorized users to /login?

hard

A. function auth(req, res, next) { if (req.session.user) res.redirect('/login'); else next(); }

B. function auth(req, res) { if (!req.session.user) next(); else res.redirect('/login'); }

C. function auth(req, res, next) { if (req.session.user === undefined) res.send('Access granted'); else next(); }

D. function auth(req, res, next) { if (req.session.user) next(); else res.redirect('/login'); }

Solution

1. Step 1: Understand middleware signature

   Middleware must have (req, res, next) and call next() to continue.

2. Step 2: Check session user and redirect logic

   If req.session.user exists, call next() to allow access; otherwise redirect to /login.

3. Final Answer:

   function auth(req, res, next) { if (req.session.user) next(); else res.redirect('/login'); } -> Option D

4. Quick Check:

   Session user? next() : redirect [OK]

Hint: Call next() if logged in; else redirect to login [OK]

Common Mistakes:

• Missing next() call in middleware
• Reversing condition logic
• Sending response instead of redirecting