Doubt on workers for platform usecase
🔑KV
Workers
WorkersI’m exploring the idea of using WFP (workers for platform) to ship my code logic so it can be easily used by any website. The goal is to allow site owners to “enable” this functionality with a simple action, after which a Worker is attached to their site.
Once enabled, every incoming request should be handled by this Worker before reaching the website. The Worker would execute on the website’s own Cloudflare edge infrastructure, with minimal latency.
All the workers should be able to access a globally shared KV namespace.
I want to package and deliver this so it can be seamlessly attached to any site already using Cloudflare Edge Services.
I’m looking for guidance from the Cloudflare community to identify any gaps in this approach and, if possible, recommendations, resources, or best practices to help implement this architecture successfully.
Once enabled, every incoming request should be handled by this Worker before reaching the website. The Worker would execute on the website’s own Cloudflare edge infrastructure, with minimal latency.
All the workers should be able to access a globally shared KV namespace.
I want to package and deliver this so it can be seamlessly attached to any site already using Cloudflare Edge Services.
I’m looking for guidance from the Cloudflare community to identify any gaps in this approach and, if possible, recommendations, resources, or best practices to help implement this architecture successfully.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
