Hacker News new | ask | show | jobs
by anilgulecha 2 hours ago
If eastdakota/jgc are here.

- simply expose containers to the world directly - without having to go via workers.

- You have other amazing parts of the stack anyway (D1, durable objects, a great object store). These aren't considered "lockin".

- workers is "lockin" - not similar enough to lambda/cloud functions and so becomes CF specific.

Not having a simple container based compute piece has made me hesitate in taking up CF. (Fly or firebase won out)
2 comments
jgrahamc 1 hour ago
I am here but I retired from being CTO of Cloudflare in March 2025 [1] and the current CTO is Dane Knecht (dknecht here). What advantage does decoupling Cloudflare Containers from Cloudflare Workers have?

[1] https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...

link
htrp 32 minutes ago
quick piece of feedback, the workers architecture is a little bit annoying when converting from Lambda but hooking up to cloudflare MCP solves 90% of the issues
link
yodon 2 hours ago
>Not having a simple container based compute piece made me hesitate in taking up CF

Agreed. I wish CF had something like Azure's new fast-starting Express containers.

link