The author's problem arises from the inability to understand that JAMStack is tailored towards static content / client-side apps. That's it. Postgres, server lo

The author's problem arises from the inability to understand that JAMStack is tailored towards static content / client-side apps. That's it. Postgres, server logic, services etc all represent something else. He also discusses Netlify and Render feature sets. While both services allow to do more than just a stateless JAMStack, they both have too much vendor lock-ins, and offer too little to make people take that functionality seriously. For example, Render supports Docker containers, but they are tied to a single region only. This is probably enough for hobby projects, but it's a show stopper for commercial deployments. In my opinion, author drank too much Heroku-aid in his conclusions.