Hey Necmettin!

Thanks so much for reading and responding. I believe Jamstack would be a great idea for a lot of greenfield projects, because you can always increase your database complexity later. Or, you could outsource your database completely (using Firebase, for example).

Indeed, don’t tools like Gatsby, Next.js, and Nuxt.js make Jamstack sites dynamic, even though they use server-side rendering?

Here’s why I think Jamstack could be a good option: Let’s say you build a Jamstack site that has some dynamic feature (like comments) using a GraphQL / Apollo API. Does the database particularly matter — it could be MongoDB, but it could be a lot of other options? Let’s say you built said site using Sanity.io to handle the content — that’s a Jamstack alternative to MongoDB.

I did update the article to point out more problems with DynamoDB.

Have a great day!

🤓 The physical therapist who writes JavaScript 💪 Web Developer 😎 Mentor 🧠 DPT 😄 SEO Expert 😁 React 😆 Jamstack 💬 Ask me anything 👉 DoctorDerek.com 👈

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store