Session-based vs token-based auth in Node.js - Performance Comparison

Performance: Session-based vs token-based auth

MEDIUM IMPACT

This concept affects page load speed and interaction responsiveness by influencing server requests and client-side processing during authentication.

Managing user authentication efficiently in a web app

Node.js

const jwt = require('jsonwebtoken');
const express = require('express');
const app = express();

app.get('/profile', (req, res) => {
  const token = req.headers.authorization?.split(' ')[1];
  if (!token) return res.status(401).send('Unauthorized');
  try {
    const user = jwt.verify(token, 'secret');
    res.send(`Hello ${user.name}`);
  } catch {
    res.status(401).send('Unauthorized');
  }
});

Token-based auth stores user info in the token, eliminating server session lookups and reducing server memory load.

📈 Performance GainRemoves server session lookup, reducing response latency and server memory usage.

Managing user authentication efficiently in a web app

Node.js

const express = require('express');
const session = require('express-session');
const app = express();

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

app.get('/profile', (req, res) => {
  if (req.session.user) {
    res.send(`Hello ${req.session.user.name}`);
  } else {
    res.status(401).send('Unauthorized');
  }
});

Session data is stored on the server, requiring a lookup on each request, which adds latency and increases server memory usage.

📉 Performance CostTriggers server-side session lookup on every request, increasing response time and server memory usage.

Performance Comparison

Pattern	Server Memory Usage	Request Latency	Scalability	Verdict
Session-based Auth	High (stores sessions)	Higher (session lookup per request)	Lower (needs sticky sessions or shared store)	[X] Bad
Token-based Auth	Low (stateless tokens)	Lower (local token verification)	Higher (easier horizontal scaling)	[OK] Good

Rendering Pipeline

Authentication affects the network request and response cycle, impacting how quickly the server can respond and the client can render authenticated content.

→Network

→Server Processing

→Client Rendering

⚠️ BottleneckServer Processing due to session lookup or token verification

Core Web Vital Affected

INP

This concept affects page load speed and interaction responsiveness by influencing server requests and client-side processing during authentication.

Optimization Tips

1Avoid server session lookups to reduce request latency.

2Use stateless tokens to lower server memory usage.

3Stateless auth improves scalability and interaction responsiveness.

Performance Quiz - 3 Questions

Which authentication method reduces server memory usage the most?

A Session-based authentication

B Token-based authentication

C Both use equal memory

D Neither affects memory

DevTools: Network

How to check: Open DevTools, go to Network tab, inspect authentication requests, check response times and headers for session cookies or tokens.

What to look for: Look for longer server response times with session cookies and smaller, faster token-based requests.

Practice

1. Which of the following best describes session-based authentication in Node.js?

easy

A. User data is stored on the server and linked to the client via cookies.

B. User credentials are sent with every request without storing data on the server.

C. A signed token is stored on the server and sent to the client.

D. Authentication is done only once without any session or token.

Solution

1. Step 1: Understand session-based auth storage

   Session-based authentication stores user info on the server side, typically in memory or a database.

2. Step 2: Identify how client links to session

   The client receives a cookie that holds a session ID to link requests to the stored session data.

3. Final Answer:

   User data is stored on the server and linked to the client via cookies. -> Option A

4. Quick Check:

   Session-based auth = server stores data + cookie link [OK]

Hint: Session auth stores data server-side, linked by cookies [OK]

Common Mistakes:

• Thinking tokens are stored on the server in session auth
• Confusing session ID with user credentials
• Assuming session data is stored on the client

2. Which code snippet correctly sets a cookie for session-based authentication in Express.js?

easy

A. res.session('abc123');

B. res.setHeader('Authorization', 'Bearer abc123');

C. res.sendToken('abc123');

D. res.cookie('sessionId', 'abc123', { httpOnly: true });

Solution

1. Step 1: Identify Express.js method to set cookies

   Express uses res.cookie() to set cookies on the client with options like httpOnly for security.

2. Step 2: Match correct syntax for session cookie

   res.cookie('sessionId', 'abc123', { httpOnly: true }) correctly sets a cookie named 'sessionId'.

3. Final Answer:

   res.cookie('sessionId', 'abc123', { httpOnly: true }); -> Option D

4. Quick Check:

   Use res.cookie() to set session cookies [OK]

Hint: Use res.cookie() to set cookies in Express [OK]

Common Mistakes:

• Using res.setHeader for cookies instead of Authorization header
• Assuming res.sendToken is a valid Express method
• Trying to set session with res.session which doesn't exist

3. Given this token-based auth code snippet, what will be the output if the token is valid?

const jwt = require('jsonwebtoken');
const token = req.headers.authorization?.split(' ')[1];
try {
  const user = jwt.verify(token, 'secretKey');
  res.send(`User ID: ${user.id}`);
} catch {
  res.status(401).send('Unauthorized');
}

medium

A. SyntaxError

B. Unauthorized

C. User ID: [user's id from token]

D. Token string printed as is

Solution

1. Step 1: Extract token from Authorization header

   The code splits the 'Authorization' header to get the token part after 'Bearer'.

2. Step 2: Verify token and extract user info

   jwt.verify checks the token with 'secretKey' and returns the decoded user object if valid.

3. Final Answer:

   User ID: [user's id from token] -> Option C

4. Quick Check:

   Valid token returns decoded user info [OK]

Hint: Valid JWT returns decoded user info, else error [OK]

Common Mistakes:

• Assuming token is printed directly without decoding
• Confusing token verification failure with syntax error
• Ignoring optional chaining and possible undefined token

4. Identify the bug in this session-based auth middleware code snippet:

function auth(req, res, next) {
  if (!req.session.user) {
    res.status(401).send('Not logged in');
  }
  next();
}

medium

A. req.session.user should be req.user instead.

B. Missing return after sending 401 response causes next() to run anyway.

C. next() should be called before checking session.

D. res.status should be res.sendStatus.

Solution

1. Step 1: Analyze control flow after sending response

   After res.status(401).send(), the function continues and calls next(), allowing unauthorized access.

2. Step 2: Fix by adding return to stop execution

   Adding return before res.status stops the function, preventing next() from running when unauthorized.

3. Final Answer:

   Missing return after sending 401 response causes next() to run anyway. -> Option B

4. Quick Check:

   Return after response to stop middleware [OK]

Hint: Add return after res.send to prevent next() running [OK]

Common Mistakes:

• Calling next() before checking session
• Confusing req.session.user with req.user
• Using res.sendStatus instead of res.status().send()

5. You want to build a Node.js app that supports multiple devices per user and scales easily. Which authentication method is best and why?

hard

A. Token-based auth, because tokens are stateless and work well across devices.

B. Token-based auth, because it requires server to store session data.

C. Session-based auth, because cookies automatically sync across devices.

D. Session-based auth, because it stores user data on the server for security.

Solution

1. Step 1: Consider multi-device and scalability needs

   Supporting multiple devices means the server should not rely on storing session state for each device.

2. Step 2: Choose token-based auth for statelessness

   Token-based auth uses signed tokens stored client-side, allowing stateless servers and easy scaling.

3. Final Answer:

   Token-based auth, because tokens are stateless and work well across devices. -> Option A

4. Quick Check:

   Stateless tokens = scalable multi-device auth [OK]

Hint: Use token auth for scalable, multi-device apps [OK]

Common Mistakes:

• Thinking sessions sync automatically across devices
• Believing token auth requires server session storage
• Choosing session auth for scalability