If you’ve been reading Mastering Mongoose
, the tradeoffs of using the Jamstack may sound familiar. That’s because they’re similar to the tradeoffs for denormalizing data in MongoDB.
If you have a `BlogPost` model in Mongoose, and you choose to embed the blog post author’s name, you get the same benefits: performance, durability, and predictability. But you also risk update anomalies if you aren’t careful when you update the author’s name.
Jamstack takes the principle of denormalization to the edge
(pun intended). You can think of the Jamstack as “denormalizing” your whole web app.
Because the tradeoffs are similar, the Jamstack is best suited for similar use cases as database denormalization: data that is read 1000x more than it is updated. Blog posts are a classic example. Blog posts are typically written once, and then read thousands of times.