The term "Jamstack" was coined in 2016, but the architecture it labels predates the name by years. The recent surge of attention has brought a wave of criticism along with it — some of it fair, some of it resting on myths that persist even though each usually contains a kernel of truth.

Rebranded Static Sites?

Jamstack is arguably a rebranding of what the industry called "static sites," which is not an attempt to mislead — the opposite. "Static site" had stopped describing what people were building: sites generated with static site generators (SSG) that are full of dynamic content and capabilities.

Static sites were seen as blogs and documentation with largely fixed UI, interaction limited to embedded comments and a contact form. Jamstack sites carry user authentication, dynamic content, ecommerce and user-generated content. Prominent examples include Smashing Magazine, Sphero, Postman, Prima, Impossible Foods and TriNet.

The Fragility Question

Because Jamstack projects lean on a variety of first- or third-party services to deliver dynamic capabilities, critics raise two concerns: a single failed component takes down site functionality, and infrastructure ends up dependent on tools you do not own.

The first argument overlooks that most of a Jamstack site is pre-rendered, served as static assets from a CDN — the source of much of its speed and security. Dynamic functions such as shopping carts, authentication, user-generated content and search use serverless functions plus APIs. If Stripe's APIs go down, ecommerce stops working, but the site itself does not go down and can inform the user gracefully. A server-rendered page calling the payment back end asynchronously would be no more or less fragile; one that depends directly on the API call can leave users waiting on a response or hitting an error.

The second argument is hard to measure: many server-rendered applications rely on APIs for significant functionality to speed development, leverage a provider's expertise, or offload legal and compliance responsibility, making them no more or less dependent than a Jamstack version. Apps built mostly on internal or homegrown solutions may differ.

Content Editing and the Headless CMS

Concerns about editing content, such as needing to SSH into a Linux box and edit posts in Vim, date back to static sites of the past. A wide range of headless CMS options now exists, from free and open source to commercial offerings for large enterprises, with editing capabilities that rival traditional CMSes. Manually editing Markdown, YAML or JSON is unnecessary, even for a blog side project.

A legitimate criticism remains: the headless CMS and build process can disconnect the content being edited from the change on the site, making it hard to preview a change's impact without a complex build preview process. Stackbit, TinaCMS and Gatsby Preview are among the tools addressing it, and WYSIWYG-grade editing on top of the Jamstack is close to commonplace.

SEO on the Jamstack

SEO criticism is largely legacy: managing metadata once meant hand-editing YAML frontmatter, which grew cumbersome when injecting per-page metadata or creating structured data like JSON-LD. Advances in content management have addressed that complexity.

Pre-rendered pages make sitemaps and JSON-LD relatively simple when metadata exists, and, combined with CDNs, ease the performance benchmarks that boost ranking. Jamstack excels at technical SEO while giving editors the tools to supply keyword and other metadata.

Not a JavaScript Framework in Sight

Jamstack has come to be treated as synonymous with front-end JavaScript frameworks, since well-known solutions such as Gatsby (React), Next.js (React), Nuxt (Vue), VuePress (Vue), Gridsome (Vue) and Scully (Angular) depend on one. The confusion is compounded by the "J": it stands for JavaScript, but that does not make every solution JavaScript-based or dependent on npm or a framework.

Hugo (Go), Jekyll (Ruby), Pelican (Python) and the recently released Bridgetown (Ruby) are widely used and not built in JavaScript. Eleventy is written in JavaScript without depending on a framework. None of these tools prevents using a framework; none requires it. Frameworks are powerful and simplify complex tasks, but a framework is not a prerequisite for the Jamstack, which comes in 460 flavors.

None of this means Jamstack has no genuine weaknesses. There are plenty of legitimate criticisms, and they tend to cluster around a few recurring themes.

Where the model strains

The learning curve is real

Sebastian De Deyne made the point bluntly in Thoughts (and doubts) after messing around with the JAMstack:

In my experience, the JAMstack (JavaScript, APIs, and Markup) is great until is isn’t. When the day comes that I need to add something dynamic–and that day always comes–I start scratching my head.

Standing up a blog or simple site with a static site generator may not be terribly difficult. Building a real site with genuinely dynamic features gets complicated fast. The options for each task are numerous, so weighing pros and cons is hard work. Jamstack's biggest strength — it isn't prescriptive — is exactly what makes it look unapproachable, leaving the impression that it's a poor fit for complex projects.

Integration is the hard part

Agreed. In yesterday's web you could grab an instrument and begin playing. Today's web development feels like a conductor trying to pull together a massive orchestra into a cohesive song – you have to understand each individual musician's part to have any chance of success.

— Brian Rinaldi (@remotesynth) May 1, 2020

Once you reach the dynamic features, a site can end up depending on an array of services and APIs: a headless CMS for content, a serverless function that calls a payments API, a service like Algolia for search, and more. Wiring those pieces together is complex in itself. Each one typically brings its own dashboard plus API and SDK updates, compounding the problem.

This is the gap that tools such as Stackbit and RedwoodJS aim to close, pulling the disparate pieces of a Jamstack backend together so they are easier to build and manage.

Frameworks dominate the teaching, not the architecture

Skepticism toward the front-end's dependence on JavaScript frameworks has been growing, and the tradeoffs are real — Tim Kadlec laid them out in a post on the cost of JavaScript frameworks. A framework is not required to work in the Jamstack.

Yet that impression persists, for two reasons: so many Jamstack tools rely on frameworks, and so much Jamstack teaching is centered on them. The reasoning is understandable — many Jamstack developers are comfortable in frameworks, and no one can teach every tool, so you pick your favorite. Still, Jamstack's long-term success depends on its flexibility, which means presenting the diversity of solutions it offers, both with and without JavaScript frameworks.

Judging fit

These myths come from the perspective of someone who believes deeply in the value of the Jamstack despite its flaws. For a balanced look at when to choose Jamstack over server-side rendering and when not to, Chris Coyier's Static or Not? is a useful read.