Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Pages: the best way to build JAMstack websites

blog.cloudflare.com

Post reply on HN
Print view View original

81–89 of 89 posts

Re: Cloudflare Pages: the best way to build JAMstack websites

#81

Post by nojvek »

This is huge!

"It’ll work the exact same way Pages does: just write your code, git push, and we’ll deploy it for you. The only difference is, it won’t just be your frontend, it’ll be your backend, too. And just to be clear: this is not just for stateless functions. With Workers KV and Durable Objects, we see a huge opportunity to really enable any web application to be built on this platform."

The three primitives to anything on the internet is

1) static assets - just served as is to the client (cf pages/cdn) 2) dynamic api - compute per client request (cf workers) 3) a fast and consistent data store - (cf kv / objects)

The three primitives allow any developer to build powerful serverless services. Plus they have built in analytics and other nice extras.

What I want next from cloudflare is being able to run containers like google cloud run, and a nice firestore like database. That would make cloudflare a pretty amazing cloud provider.

Re: Cloudflare Pages: the best way to build JAMstack websites

#82

Post by rita3ko »

nojvek wrote: post #81

This is huge! "It’ll work the exact same way Pages does: just write your code, git push, and we’ll deploy it for you. The only difference is, it won’t just be your frontend, it’ll be your backend, too. And just to be clear: this is not just for stateless functions. With Workers KV and Durable Objects, we see a huge opportunity to really enable any web application to be built on this platform." The three primitives to…

Genuinely curious — what would you expect to get from containers that you can't get from building on Workers + Pages as described above?

Re: Cloudflare Pages: the best way to build JAMstack websites

#83

Post by saagarjha »

parhamn wrote: post #37

CloudFlare has leveraged the fact that they are pretty close to the sole provider of DDoS (which 99% of people don't need to worry about) beautifully. Once your in for the DNS/DDoS/Nginx-as-a-service adding anything else is a matter of hop/latency minimization. Like I love and use Netlify but I'm always happy to reduce hops where I can.

> sole provider of DDoS

I should hope not…

Re: Cloudflare Pages: the best way to build JAMstack websites

#84

Post by twelve40 »

no_wizard wrote: post #28
nrmitchi wrote: post #7

This is probably going to go somewhere, and it's good to see Netlify get some more competition, but this announcement kind of lost me at: > There are no great solutions. Therea are plenty of existing solutions here that do pretty much the same thing, including Netlify, Vercel, and going all the way back to Heroku. Cloudflare is expanding their product line, which is fine, but lets not pretend that this is some brand…

There is some marketing here to be sure, but in some sense, they are at least partially right in that: - they aren’t just reselling AWS services (if I recall correctly Netlify and to at least some extent Vercel do, for instance) - They will be providing their own database platform (coming soon according to the blog post, as of 12/17/2020) which means they can provide the ability to have a single end to end provider f…

> no other player really offers that out of the box

S3 + cloudfront?

Re: Cloudflare Pages: the best way to build JAMstack websites

#85

Post by string »

JoachimSchipper wrote: post #56
string wrote: post #46

Always pleased to see more alternatives to Netlify/Vercel. I love how easy Netlify makes it to deploy things, but I don't really understand their pricing. I recently built a pretty basic static webapp that would have racked up around £100 in bandwidth charges (~0.5TB) in the first 24 hours on Netlify. I stuck it on BunnyCDN instead after I realised this and it ended up costing around £3. The five or so minutes I save…

Anyone reselling AWS services wants to price bandwidth above AWS' price, and AWS' bandwidth pricing is high. (E.g. AWS EC2 in us-east-1 to the internet costs up to ~0.09/GB, so your ~0.5 TB would end up at around £33 - although Netlify will obviously have some volume discounts.)

I haven't dealt with AWS very much, but I suspected that might be the case. Thanks for the figures. I guess the margins on bandwidth must be quite significant for cloud service providers.

Re: Cloudflare Pages: the best way to build JAMstack websites

#86

Post by drewrbaker »

Posting this here hoping someone from Cloudflare sees this. Your team features suck. Impossible to grant access to a single “site” or transfer ownership of a single site. Until you improve that, hard for an agency like ours to use this new Pages feature.

Also while your here, youR pricing is a mess across the platform. You have so many add-on extra costs per site and it’s really hard to understand how they interact with the different monthly plans.

Re: Cloudflare Pages: the best way to build JAMstack websites

#87

Post by jgrahamc »

drewrbaker wrote: post #86

Posting this here hoping someone from Cloudflare sees this. Your team features suck. Impossible to grant access to a single “site” or transfer ownership of a single site. Until you improve that, hard for an agency like ours to use this new Pages feature. Also while your here, youR pricing is a mess across the platform. You have so many add-on extra costs per site and it’s really hard to understand how they interact w…

You can always email me (jgc @ cloudflare) with feedback and I will get it to the right people.

Re: Cloudflare Pages: the best way to build JAMstack websites

#88

Post by Can_Not »

saagarjha wrote: post #83
parhamn wrote: post #37

CloudFlare has leveraged the fact that they are pretty close to the sole provider of DDoS (which 99% of people don't need to worry about) beautifully. Once your in for the DNS/DDoS/Nginx-as-a-service adding anything else is a matter of hop/latency minimization. Like I love and use Netlify but I'm always happy to reduce hops where I can.

> sole provider of DDoS I should hope not…

At the hobbyist/self-funded budget, they are by a longshot.

Re: Cloudflare Pages: the best way to build JAMstack websites

#89

Post by nojvek »

rita3ko wrote: post #82
nojvek wrote: post #81

This is huge! "It’ll work the exact same way Pages does: just write your code, git push, and we’ll deploy it for you. The only difference is, it won’t just be your frontend, it’ll be your backend, too. And just to be clear: this is not just for stateless functions. With Workers KV and Durable Objects, we see a huge opportunity to really enable any web application to be built on this platform." The three primitives to…

Genuinely curious — what would you expect to get from containers that you can't get from building on Workers + Pages as described above?

Containers allow any programming language. Any sets of apt-get installed dependencies.

Workers and pages only work with js at a very specific version of v8. Many node native modules don’t work with it, so in that sense it’s quite limited

Post reply on HN