Engineering & Architecture

Switched to SSR When “Good Enough” Started Causing Real Problems

Dana Iti3 min readRendering with Intent series, part 4

Static rendering worked for content that rarely changed. ISR handled fresh-but-not-immediate pages. But some parts of WonderBook couldn’t be cached or prebuilt at all, they had to be evaluated per user, per request, every time.

That’s when I turned to SSR (Server-Side Rendering).

How SSR works

SSR generates HTML at request time using live data, not a cached copy. Each visitor gets a page rendered specifically for them, with fresh database queries and user context baked into the HTML before it’s sent.

This guarantees that the user sees up-to-date data, but at the cost of caching efficiency.

When SSR makes sense

✅ Use SSR when❌ Avoid SSR when
Data depends on the userContent is static
Page requires authenticationData changes rarely
Security or privacy mattersSpeed is the top priority
Real-time accuracy is criticalSEO is the main goal without dynamic data

SSR trades cached speed for correctness and security. It’s about trust: ensuring what’s displayed is exactly true in that moment for that user.

Why SSR can feel slower. TTFB and rendering cost

SSR doesn’t just render on demand, it waits until a user asks. That extra computation time shows up as TTFB (Time To First Byte), which is how long it takes for the browser to start receiving the first byte of HTML from the server.

Here’s how different rendering strategies typically impact TTFB:

Rendering StrategyTTFB ImpactWhy
Static (SSG/ISR prebuilt)Very lowAlready rendered and served instantly from a CDN
ISR (after regen)LowActs like static once cached
SSRHighServer fetches data and renders fresh HTML per request
Client-side renderingLow TTFB but slower to become usefulHTML arrives quickly, but content isn’t interactive until JS runs
StreamingMedium TTFB but feels fasterServer sends partial HTML progressively so users see something sooner

SSR isn't bad because it's slower. It’s slower because it’s doing real work in real time, and that work only makes sense when correctness outweighs latency.

SSR in WonderBook - Dashboard

The user dashboard shows generated stories, word counts, and AI credit balances. It’s personalised, authenticated, and constantly changing. Caching it would risk showing the wrong data to the wrong user.

export const dynamic = "force-dynamic";

export default async function DashboardPage() {
  const user = await getUser();
  const stories = await getUserStories(user.id);
  return <Dashboard stories={stories} />;
}

What I took away

I only use SSR where the page depends on who’s looking or on something that just changed. In WonderBook that’s the dashboard. Pages that are the same for everyone stay static or use ISR, so most visitors still get the fast cached version, and only the signed-in pages pay the cost of rendering on every request.

nextjsssrrenderingfrontend-architecturesystem-design
The Rendering with Intent series
  1. Part 1. Rendering Blindly Cost Me Speed, Money, and Sanity. Here’s How I Fixed It
  2. Part 2. Static Rendering. Doing the Work Before Anyone Asks For It
  3. Part 3. I Wanted Static Speed Without Serving Yesterday’s Data. ISR Was the Answer
  4. Part 4. Switched to SSR When “Good Enough” Started Causing Real ProblemsYou are here
  5. Part 5. When Static Pages Weren’t Enough, Client Components Took Over
  6. Part 6. I Made Data Feel Faster Without Actually Speeding It Up

Keep reading

Engineering & Architecture

Explain to me like I'm 12

Making something genuinely complex feel simple. I built how I want it to work, and now I'm working through how it needs to work so it stays simple.

Engineering & Architecture

Next.js 16. Caching Finally Makes Sense

Next.js 16 flipped caching from implicit magic to explicit choice. Everything is dynamic by default now, and you opt into caching when you want it.

Engineering & Architecture

I Made Data Feel Faster Without Actually Speeding It Up

I made WonderBook feel faster without actually making it faster. Here's how streaming changed everything.