Session-based authentication in Ruby on Rails - Performance & Optimization

Performance: Session-based authentication

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by managing user state on the server and sending session cookies with requests.

Managing user login state efficiently

Ruby on Rails

class ApplicationController < ActionController::Base
  before_action :load_user

  def load_user
    @current_user ||= User.find_by(id: session[:user_id])
  end
end

Uses memoization to avoid multiple database calls per request and uses find_by which returns nil safely.

📈 Performance Gainreduces database queries by 50-100% per request, improving response time

Managing user login state efficiently

Ruby on Rails

class ApplicationController < ActionController::Base
  before_action :load_user

  def load_user
    @current_user = User.find(session[:user_id]) if session[:user_id]
  end
end

This loads the user from the database on every request, causing repeated database queries and slowing response time.

📉 Performance Costblocks rendering for 20-50ms per request due to database query

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Loading user on every request	0 (server-side)	0	0	[X] Bad
Memoized user loading	0 (server-side)	0	0	[OK] Good
Large, insecure cookies	0	0	0	[X] Bad
Optimized secure cookies	0	0	0	[OK] Good

Rendering Pipeline

Session-based authentication involves server-side session lookup and cookie handling before rendering the page. The browser sends cookies with requests, the server validates sessions, and then renders the response.

→Network

→Server Processing

→Rendering

⚠️ BottleneckServer Processing due to session lookup and database queries

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by managing user state on the server and sending session cookies with requests.

Optimization Tips

1Avoid loading user data from the database on every request; use memoization or caching.

2Configure cookies with secure, HTTP-only, and SameSite flags to reduce network overhead and improve security.

3Keep session data minimal and avoid large cookies to improve request and response speed.

Performance Quiz - 3 Questions

What is a common performance issue with session-based authentication in Rails?

A Too many DOM nodes created by session data

B Excessive CSS animations triggered by session state

C Repeated database queries to load user on every request

D Large JavaScript bundles for session handling

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and inspect request and response headers for cookie size and flags.

What to look for: Look for cookie size in request headers and presence of Secure, HttpOnly, and SameSite flags to confirm good cookie practices.

Practice

1. What does session[:user_id] typically store in a Rails application using session-based authentication?

easy

A. The user's password

B. The user's email address

C. The ID of the currently logged-in user

D. The entire user object

Solution

1. Step 1: Understand session usage in Rails

   Rails uses the session hash to store small pieces of data between requests, commonly the user ID for authentication.

2. Step 2: Identify what session[:user_id] holds

   This key stores the unique identifier of the logged-in user to recognize them on subsequent requests.

3. Final Answer:

   The ID of the currently logged-in user -> Option C

4. Quick Check:

   session[:user_id] = user ID [OK]

Hint: Remember session stores user ID, not full user data [OK]

Common Mistakes:

• Thinking session stores full user object
• Confusing user ID with password or email
• Assuming session is client-side storage

2. Which of the following is the correct way to log out a user by clearing the session in a Rails controller?

easy

A. session.clear

B. All of the above

C. session[:user_id] = nil

D. session.delete(:user_id)

Solution

1. Step 1: Review methods to clear session data

   In Rails, you can remove session data by clearing all keys, deleting a specific key, or setting a key to nil.

2. Step 2: Confirm all options effectively log out user

   All three methods remove the user ID from session, effectively logging out the user.

3. Final Answer:

   All of the above -> Option B

4. Quick Check:

   Any method removing user_id logs out user [OK]

Hint: Any method removing session[:user_id] logs out user [OK]

Common Mistakes:

• Only using session[:user_id] = nil and ignoring others
• Trying to clear session without removing user_id
• Confusing session.clear with resetting entire app

3. Given this Rails controller code snippet:

def create
  user = User.find_by(email: params[:email])
  if user&.authenticate(params[:password])
    session[:user_id] = user.id
    redirect_to dashboard_path
  else
    render :new
  end
end

What happens when the user enters correct email and password?

medium

A. User ID is saved in session and redirected to dashboard

B. User is redirected to login page again

C. Session is cleared and user stays on login page

D. An error is raised because session[:user_id] is not set

Solution

1. Step 1: Analyze authentication condition

   The code checks if a user with the given email exists and if the password matches using authenticate.

2. Step 2: Understand session assignment and redirect

   If authentication passes, it stores the user's ID in session and redirects to the dashboard.

3. Final Answer:

   User ID is saved in session and redirected to dashboard -> Option A

4. Quick Check:

   Correct login sets session[:user_id] and redirects [OK]

Hint: Correct login sets session[:user_id] and redirects [OK]

Common Mistakes:

• Assuming user stays on login page after success
• Thinking session[:user_id] is not set on success
• Confusing render with redirect behavior

4. Identify the error in this logout action:

def logout
  session[:user] = nil
  redirect_to root_path
end

medium

A. No error, this code works fine

B. redirect_to should be redirect_back

C. session[:user] = nil does not clear session

D. Session key should be :user_id, not :user

Solution

1. Step 1: Check session key used for authentication

   Rails session-based authentication typically uses session[:user_id] to track logged-in user.

2. Step 2: Identify mismatch in session key

   The code sets session[:user] to nil, which does not clear the actual user ID stored in session[:user_id].

3. Final Answer:

   Session key should be :user_id, not :user -> Option D

4. Quick Check:

   Correct session key is :user_id [OK]

Hint: Use session[:user_id] to clear login, not session[:user] [OK]

Common Mistakes:

• Using wrong session key name
• Assuming setting any session key to nil logs out user
• Confusing redirect_to with redirect_back

5. You want to restrict access to a controller action so only logged-in users can see it. Which code snippet correctly checks session-based authentication before allowing access?

hard

A. before_action :require_login

def require_login
redirect_to login_path unless session[:user_id]
end

B. before_action :require_login

def require_login
redirect_to login_path if session[:user_id]
end

C. before_action :require_login

def require_login
redirect_to root_path unless session[:user_id]
end

D. before_action :require_login

def require_login
redirect_to login_path unless session[:user]
end

Solution

1. Step 1: Understand access control with before_action

   Use a method to check if session[:user_id] exists before allowing access.

2. Step 2: Identify correct redirect condition

   If session[:user_id] is missing, redirect to login page to block access.

3. Final Answer:

   Redirect to login unless session[:user_id] exists -> Option A

4. Quick Check:

   Access allowed only if session[:user_id] present [OK]

Hint: Redirect unless session[:user_id] exists to protect pages [OK]

Common Mistakes:

• Redirecting if session[:user_id] exists (wrong logic)
• Using wrong session key like :user
• Redirecting to wrong path on failure