Your e-commerce catalog shows real-time stock prices. Front team proposes Jamstack on Netlify; back team a Laravel monolith in SSR. Debate focuses on "modernity." Real stake: where do you run logic on each request — and what happens when ten thousand visitors arrive at once?
Jamstack and SSR are not opposing religions. They move dynamism to different addresses: build, edge, or origin server. Misplaced, you pay both cold starts and cache invalidation.
Jamstack: deferred dynamism
Build → static assets on CDN. Personalization via client-side JavaScript, edge functions, or API calls.
Strengths: excellent TTFB on static content, CDN scale, atomic deploys. Weaknesses: fresh data = complex cache invalidation; dynamic SEO needs care; API dependency; editor preview to plan.
Typical hosting: Netlify, Vercel, Cloudflare Pages plus separate API origin.
SSR: dynamism per request
Each (or part of) request generates HTML server-side — PHP, Node, Python.
Strengths: native personalization, sessions, centralized business logic, mature stack. Weaknesses: scale = more servers or fragment cache; TTFB on heavy queries; heavier deploys.
Typical hosting: VPS, PaaS, Kubernetes, PHP shared hosting.
| Need | Jamstack favored | SSR favored |
|---|---|---|
| Blog / marketing | Yes | OK |
| Real-time stock prices | API + fine cache | Yes |
| Logged-in client area | Hybrid | Yes |
| Read-only traffic peak | Static CDN | Cache + horizontal scale |
Three patterns to place dynamism
Full static + client fetch. Simple; poor SEO without JavaScript; exposed API.
SSG/ISR + revalidation. Good marketing compromise; configurable freshness delay.
SSR per request. Maximum freshness; compute cost at peak.
Simulate peak on origin API and SSR — not only CDN. That reveals the real bottleneck.
The summit: dynamism has an address
Decide and move forward without blind spots
Classify pages as static, quasi-static (ISR), and mandatory dynamic (SSR). Simulate peak on origin API and SSR, not CDN alone. Choose edge hosting if >80% static; VPS or Kubernetes if SSR dominant. Document cache invalidation strategy before product launch. Compare edge and VPS offers via comparator and directory.
Frequently asked questions
Does Jamstack mean "no server"?
No — dynamism goes through APIs and functions; servers exist upstream. Jamstack moves execution, does not remove it.
When prefer classic SSR?
Strong personalization, server sessions, heavy back logic, intolerable cold start on critical user path.
Does Jamstack handle peaks better?
CDN yes for static; uncached API becomes bottleneck — sometimes worse than SSR with fragment cache.
Can you combine both?
Yes: ISR plus SSR routes, static marketing plus connected SSR app. Most frequent mature approach.
Dynamism should live where your traffic and freshness require it — not where fashionable stack suggests.
