[1]: https://blog.cloudflare.com/container-platform-preview/
The reason aws is dominant is because it’s the default and a known quantity. But developers and cost conscious organizations will look at alternatives. Not saying it would be easy but the prize would be huge. Plus AWS seems in chaos with a lack of sensible leadership.
I'm guessing it's just because they're so extremely all-in on every single of their products being on the edge, and you can't make that work with VMs without becoming far more expensive than any of their customers would pay.
Or maybe I'm clueless. But it sure looks that way from the outside.
You need at the very least containers and persistent volumes to be interesting to me at least.
Rust is still a wasm target. Not everything easily works. It doesn’t have all the Cloudflare sdk features js/ts has either.
And yes, you can test your local Rust code. It works nicely on your machine, but breaks with a really nasty error on their platform.
The target is `wasm32-unknown-unknown`, which allows you to use `fetch` as your only source of IO. Ok, their workers has a hacky socket implementation nowadays. Non-standard of course. And most of the ecosystem won't work really without forking everything and fixing the bugs by yourself.
We pivoted to a native Rust project. We still have one worker running in Cloudflare. We isolated that code from the workspace so that renovate updates will not touch it. You know, a random version upgrade might break the service...