Making Wasmer Edge open source would convince me to use Wasmer instead of the other options! I can see that this is on the roadmap. Any ETA you can already share?
Also I would be interested in restricting specific requests to certain regions.
Good point! I believe none of the other Edge platforms are fully open source yet (I don't mean their runtime being OSS, but the Edge Platform itself). Clouflare Workers is the only one that gets there half way with Workerd (they are missing KV, other APIs and the glue-code).
Right now the Wasmer Edge product usage is not in a stable enough point to make it open-source. I'd love to share the timelines, but anything that I say now will likely be wrong (as we are still iterating hard on the product).
> I would be interested in restricting specific requests to certain regions
I can see this being an issue if you plug the workload with data that is located in a specific region (for example, via a DB connection or doing API calls to an API in a specific region). Is that your use case?
6 comments
[ 2.9 ms ] story [ 22.5 ms ] thread0: https://fermyon.com
1: https://cosmonic.com
2: https://fastly.com
How do you think they compare against other Edge providers leveraging on Wasm such as Cloudflare Workers [1] and Wasmer Edge [2]?
In my opinion, they have way worse developer experience... but that may be my taste. I'd love to hear your thoughts!
[1] https://developers.cloudflare.com/workers/
[2] https://wasmer.io/products/edge
Right now the Wasmer Edge product usage is not in a stable enough point to make it open-source. I'd love to share the timelines, but anything that I say now will likely be wrong (as we are still iterating hard on the product).
> I would be interested in restricting specific requests to certain regions
I can see this being an issue if you plug the workload with data that is located in a specific region (for example, via a DB connection or doing API calls to an API in a specific region). Is that your use case?