71–80 of 89 posts
What does JAMstack means?
I consider it pre-rendering javascript on the server and serving sites that are mostly html with javascript coming in on the browser to take over interactivity.
They will first need to raise the script limit, which will mean rethinking how worker code is deployed to the edge. If you're going to have potentially hundreds of preview versions deployed per script, you can't eagerly push it to every server worldwide.
But in turn solving that problem and raising that limit will also open up Cloudflare Workers for more potential use cases. Currently if you want to deploy multi-tenant applications with customized per-tenant code on workers you would run out of scripts and need to set each tenant up with their own workers account.
I was wondering when this was going to happen! This is a legitimate contender here against Gatsby, Netlify, AWS Amplify and the like One thing I like about this over all the others is they aren’t (to my knowledge) just reselling AWS features with added convenience (not that this is an issue or bad, but this a lot of what Netlify does with their lamdas for instance, if I recall correctly) and their CDN is top notch IM…
Netlify maintains its own edge network that's actually deployed across various clouds. You are right that Netlify uses AWS lambdas to power Netlify Functions, but that was chosen for the wide support AWS lambda enjoys as a standard. The upcoming edge handlers (in beta) execute javascript directly on Netlify edge nodes worldwide.
There's also a big difference between deploying CDN nodes at the Edge as CloudFlare does and deploying ‘Edge Nodes’ in other cloud hosting providers which won't really be at the edge.
Earlier quoted context omitted.
> "Worker" functionality is already available on both Netlify and Vercel. Workers at those providers do not run _at the edge_ for each request. They lean on AWS Lambda to pre-generate or render assets, but you can't reliably run a function there on every user-facing request without a noticeable latency penalty.
Vercel's functions do run at the edge, but Netlify's are just AWS Lambda functions.
Cloudflare is increasingly becoming one of the more interesting companies out there. I feel like they're shifting more and more from being a straight up CDN and trying to dip their toes into things that are closer to but not quite exactly IaaS. Kind of like a better developer experience on top of certain AWS services.
Cloudflare has been a lot more than a CDN for a long time.
I was wondering when this was going to happen! This is a legitimate contender here against Gatsby, Netlify, AWS Amplify and the like One thing I like about this over all the others is they aren’t (to my knowledge) just reselling AWS features with added convenience (not that this is an issue or bad, but this a lot of what Netlify does with their lamdas for instance, if I recall correctly) and their CDN is top notch IM…
What if I already have static HTML and just need a host? No builds (I do them locally), no frameworks, just an HTML structure. I'd love to just be able to point to a git repo and have the site published through Cloudflare, since it already sits in front of my site anyway.