Course contentsShow
← System Design
Lesson 916 of 1,91924. Authentication and Authorization at ScaleFree lesson

Session vs Token Tradeoffs

Sessions offer easy revocation but require state; tokens scale horizontally but complicate logout and revocation.

Session vs Token Tradeoffs

What you'll learn: You'll understand when to choose session-based authentication versus token-based authentication by comparing their fundamental tradeoffs around state, scalability, and control.

The Core Tension

Both sessions and tokens authenticate users, but they make opposite architectural choices that cascade through your system design.

Sessions store authentication state on the server. When a user logs in, you create a session record (in memory, Redis, or a database), then give the client a simple session ID cookie. Every request uses that ID to look up "who is this user?" on the server.

Tokens embed authentication state in the credential itself. A JWT contains the user's identity and permissions, signed cryptographically. The server verifies the signature but doesn't need to look anything up.

The Fundamental Tradeoffs

Sessions: Easy Control, Hard Scaling

Pros:

  • Instant revocation: Delete the session record, user is logged out immediately
  • Easy state changes: Update permissions in one place, affect all requests
  • Smaller client payload: Just a random session ID

Cons:

  • Server state required: Every instance needs access to shared session storage
  • Horizontal scaling complexity: Need sticky sessions or distributed session store
  • Latency overhead: Extra database/cache lookup per request

Tokens: Scalable, Hard to Revoke

Pros:

  • Stateless verification: No database lookup needed, just cryptographic check
  • Perfect for horizontal scaling: Any server can verify any token independently
  • Microservices-friendly: Pass token between services without shared state

Cons:

  • Cannot revoke mid-lifetime: Valid token stays valid until expiration
  • Logout is tricky: Need token blacklists (reintroducing state!) or short expiration + refresh tokens
  • Larger payload: JWT can be hundreds of bytes vs small session ID

Key Takeaway: Sessions trade horizontal scalability for operational control (easy logout/revocation), while tokens trade revocation complexity for stateless scalability—choose based on whether you prioritize immediate control or distributed performance.