Re:Cloudflare Pages: the best way to build JAMstack websites
by rita3ko on Thursday December 17, 2020 @09:18PM
(#25463066)
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
by nojvek on Tuesday December 22, 2020 @02:54AM
(#25504005)
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
"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.