> simply expose containers to the world directly - without having to go via workers.
I run workers and containers and am curious what you mean. Do you have specific use cases in mind outside of the worker invocation model? If so, I'm curious what you'd want to run on Cloudflare. Otherwise, workers don't have to be much of a "lockin" if treated as a thin layer, more like configuration.
> You have other amazing parts of the stack anyway (D1, durable objects, a great object store).
Instead, if you mean accessing these resources from containers, it's a bit clunky [0] but it's there - you should be able to access worker bindings from containers through those outbound handlers.
Hi, I'm the hiring manager for the Flag Delivery team at LaunchDarkly. We're building and scaling the Flag Delivery Network - a globally distributed, high-throughput system that delivers hundreds of thousands to millions of real-time feature flag updates per second to SDKs across web, mobile, and server environments.
We work on challenges like streaming delivery, edge caching, global state synchronization, and operational excellence at scale. If you enjoy designing, building and running distributed systems that need to be fast, reliable, and observable - we'd love to hear from you.
I run workers and containers and am curious what you mean. Do you have specific use cases in mind outside of the worker invocation model? If so, I'm curious what you'd want to run on Cloudflare. Otherwise, workers don't have to be much of a "lockin" if treated as a thin layer, more like configuration.
> You have other amazing parts of the stack anyway (D1, durable objects, a great object store).
Instead, if you mean accessing these resources from containers, it's a bit clunky [0] but it's there - you should be able to access worker bindings from containers through those outbound handlers.
[0] https://developers.cloudflare.com/containers/platform-detail...