Now I’m more confused than ever.
You’re saying the app can depend on a web server.
The jamstack.org site explicitly says the lack of a web server is the common factor:
The thing that they all have in common is that they don’t depend on a web server.
I’m not sure what to believe.
The writing at JAMstack seems hyperbolic and lacks precision:
Entire Project on a CDN
Really? My database, customer private info, passwords, customer’s confidential image assets. the entire project on a CDN?
Everything Lives in Git
With a Jamstack project, anyone should be able to do a
git clone , install any needed dependencies with a standard procedure (like
npm install ), and be ready to run the full project locally. No databases to clone, no complex installs
So I guess that explains why almost none of the JAMstack example projects include a database?
What if we need a database? We’re supposed to read/write all customer info in flat-markdown files, commit to github and redeploy to CDN? Every mutation?
When reading about JAMstack, it seems nearly all the projects I’ve seen are pretty much static sites, or else they are consuming some API, but it doesn’t seem like many apps are richly dynamic apps backed by a database. Does JAMstack require that we replace our database with … what exactly I’m not sure.
Is anyone building a non-trivial app with JAMstack that use a MongoDb or SQL? Or are they mostly all static sites like blogs they get redeployed with every edit (Contentful)?