I’m loving it. Cloudflare is a good and reliable service provider, I expect it to expand their cloud offerings in the future like drop-in S3 replacement, application logging, etc…
I would like to define a pipeline of Workers that get to act on the request / response and count the whole pipeline as a single Worker run as long as I stay within the limits for normal workers. That way I can write composable, reusable workers that perform very specific tasks (like pipes). There could even be a GUI to let me enable / disable parts of the pipeline.
I can do that right now by jamming everything into a single source file, but it would feel better (to me) as a pipeline. It would also be cool if I could stick (headless) Cloudflare apps that are glorified workers into a pipeline like that (at a specific position).
Something that I've found difficult in the Cloudflare ecosystem is understanding the order of execution for everything (access, cache, workers, apps, page rules, etc.). It would be useful to have a dedicated resource that lists that.
Also, the preview pages for every app I've looked at today give an unsafe content warning [1].
A single file is just the deployment, something you don't really have to worry about. Setup your project and source code to have a pipeline with multiple files and libraries as you want, and let the deployment step (with wrangler) wrap up everything and publish it.
I am wondering if Cloudflare is gearing up to be a true competitor to AWS a la GCP and Azure. All it'd take is an EC2-like offering for them to have everything many companies need. You can build out the rest of your managed services (e.g. RDS, ElastiCache, S3) slowly over time.
Cloudflare seems to have a much more cohesive vision for their cloud than AWS does, and I think it could be a competitive advantage for them.