Our Workers platform can be used for a ton of useful purposes: for A/B testing, storage bucket authentication, coalescing responses from multiple APIs, and more. But Workers can also be put to use beyond "HTTP middleware": a Worker can effectively be a web application in its own right.
When we launched Workers much of the focus was on use cases surrounding websites running on origins that needed extra oomph. With Workers you can easily take a site and introduce a raft of personalization capabilities around a range of services.
At Cloudflare, we believe that getting new products and features into the hands of customers as soon as possible is the best way to get great feedback. The thing about releasing products early and often is that sometimes they might not be initially ready for your entire user base.
Share your Cloudflare Workers recipes with the Cloudflare Community. We’ve created a new tag “Recipe Exchange” in the Cloudflare Community Forum. We invite you to share your work, borrow / get inspired by the work of others, and upvote useful recipes written by others in the community.
We deployed a Cloudflare worker in front of www.cloudflare.com and api.cloudflare.com, that has since served over million requests. Here's what we learned about debugging and "failing open" when writing workers.