Just recently there was a post about SEO and GatsbyJS which reminded me about the current JAMstack trend.
You basically connect all those, pre-render pages and send them to the user from a CDN. There is no server backend. Well there is, but there isn’t. Let’s say you don’t have to handle a server backend to deliver dynamic content. But you do…or someone else does it for you. It could be a headless CMS(cloud or self-hosted) or Amazon Lambda functions. Or it could be your own PHP server that delivers graphQL. But it doesn’t have to be. I hope I am making myself totally clear.
Anyway coming back to JAMStack and Wappler. Wappler already has a reactive frontend engine(App connect), they were considering markup(templates) and they provide natively an API. Do they? They do. All SC files are accesible as an API. And you can run php serverless functions. Might not be ideal, but you can.
The caveat is that App Connect and Server Connect are tightly integrated so it makes it unfit for a JAMstack.
On the other side it seems NodeJS is also on the table again which make serverless functions less of a pain. It would be nice that if NodeJS is under consideration it wouldn’t just be another server engine for Wappler but could also allow exporting SCs as serverless functions with our without GraphQL support.
Also, Jamstack is ideal also for PWAs.
So JAMstack? What do you guys think? Future? or Smoke?