Head in the Zed Cloud

Re:Head in the Zed Cloud by ashwindharne on Monday November 10, 2025 @11:07PM (#45884016)

I think performance takes a hit due to WASM, and I imagine pricing is worse at big qps numbers (where you can saturate instances), but I've found that deploying on CF workers is great for little-to-no devops burden. Scales up/down arbitrarily, pretty reasonable set of managed services, no cold start times to deal with, etc.

Only issue is that some of the managed services are still pretty half-baked, and introduce insane latency into things that should not be slow. KV checks/DB queries through their services can be double-to-triple digit ms latencies depending on configs.

[ Parent | on HN ]

Re:Head in the Zed Cloud by jarjoura on Tuesday November 11, 2025 @03:45AM (#45885315)

I ended up using container service on azure for a small rust project that I built in a docker container and published to GitHub. GitHub actions publishes to the azure service and in the 3 years I have been running it, it's basically been almost entirely free.

[ Parent | on HN ]

Re:Head in the Zed Cloud by ashishb on Tuesday November 11, 2025 @04:15AM (#45885454)

I have a similar experience except I use Go+GitHub Actions+Google Cloud Run.

[ Parent | on HN ]

Re:Head in the Zed Cloud by yencabulator on Friday November 21, 2025 @04:39PM (#46009297)

The performance hit is less because of WASM but because the Workers platform is fundamentally defined in terms of Javascript and WASM is just a thing the JS engine has as a feature, so everything has to be proxied through JS objects and code, serialized into byte arrays, handed to the WASM, and same story in reverse.

We need WASM-native interfaces to get common to get rid of JS.

[ Parent | on HN ]