What websites/projects are ideal for Jamstack technology, and what are the limitations of building more complex applications using this methodology?

We mostly build websites that are static by nature. For example, landing pages, large corporate websites or large blogs -- the kind of websites where content doesn't change too often. We work on some marketing websites as well. We also build apps. Jamstack is for apps as well. There are different approaches to how you can build those apps these days. For example, you can just build a static skeleton, and the user can fetch data on the client's side and connect directly to APIs.

But that can be slow in some cases, since not every user has a good internet connection. So it's much better to render this on the server, at least the first view. If you enter some URL and hit the “go” button, then you'll get a fast response from the server. That can be done through the serverless functions, which both Netlify and Vercel have. Vercel recently released a beta of Edge Functions, which are even closer to the users. You can build dynamic apps with a Jamstack approach, but without the problems of having a single server.

Because the infrastructure has evolved, the term and the definition of Jamstack are evolving as well. And the way we build applications and websites is changing because of the new versions of Next.js and new frameworks like Remix. Since everything is so fresh, we are not sure if that's Jamstack or that's not Jamstack, because Jamstack in general is an umbrella term for a lot of things. But, it is possible to build fully featured, very dynamic applications in a modern Jamstack way.