My exp is in python flask/django/data science. Moved full stack recently on freelance gigs, and want to find out more about how/when people use Jamstack?
I'd never use Jamstack.<p>Why?<p>Because Jamstack is used to build websites.<p>Any websites can be built 100x faster and cheaper using Wordpress + Elementor or Webflow.<p>If you're a freelancer, you can charge clients the same amount of money for less work while also keeping them more happy.<p>How will they be happier?<p>Because Jamstack requires a CDN, a build pipeline, and headless CMS. Too many moving parts = less robust infrastructure and higher maintenance costs.<p>Wordpress on a VPS is a single moving part.<p>When should you still use Jamstack anyway?<p>If you like cocktail parties with other developers, mentioning Jamstack might get you some attention.
Your minimum classic web page architecture is something like this:<p>client -> webserver -> db<p>With the advent of CDNs for caching, someone thought "Hey, if my page is completely static, I might as well store it entirely on the CDN!".<p>Some advantages of this architecture:<p>- you don't need to manage a server / VM, a network nor a db.<p>- better latency as your page can be closer to clients, as most CDNs are globally distribuited<p>- does not have dbs as bottlenecks<p>- trivial to scale for high traffic scenarios<p>- potentially free for small projects<p>- static pages tend to be easier to test<p>Disadvantages:<p>- you're limited to static pages. anything that needs a login, a session, etc... is a showstopper*<p>- public endpoints. can`t use most CDNs for pages that only should be accessed from private networks<p>- potentially expensive for high traffic web pages<p>* some CDN providers now offer some sort of distributed storage / worker. YMMV.
It may not answer your question directly, but I've used python with JAMstack to show (semi) updated information.<p>In my case, I needed to show real(ish) time inventory. Our inventory was stuck in an ERP system without an API. So I wrote a scraper that would pull out our inventory, write it to a bunch of markdown files, and push it to Netlify to rebuild the site using Hugo. This was on an hourly cron job.<p>Since then I've used python to build JAMstack sites from data in Google Sheets.
I find that to be a happy medium for projects where there is no user input and I need to update the info somewhat regularly.
I also asked a similar question yesterday:<p><a href="https://news.ycombinator.com/item?id=31938452" rel="nofollow">https://news.ycombinator.com/item?id=31938452</a><p>Which might have some insight.<p>I’m also a full stack dev that is a bit confused on who can actually benefit from static sites like this. Particularly when it involves marketing teams that need to manage content outside of the codebase.<p>I’m definitely not convinced by them yet.