search

wasmerio / wasmer-edge-support

1 stars 0 forks source link

Running TCP/UDP Applications #1

Open syrusakbary opened 1 year ago

syrusakbary commented 1 year ago

If you want to run TCP or UDP applications (such as video server, a websockets application or more please let us know!).

TCP and UDP applications are currently supported in Wasmer Edge, but we haven't exposed the API as is still in alpha phase.

DrewRidley commented 1 year ago

I am very interested in UDP applications!

Would it also be possible with wasmer-edge to have long running applications such as databases or game servers? That is to say, if UDP ends up getting support, will there be some form of long-running sockets where the server can have its own update loop independent of whether it receives data from clients?

I guess to clarify, I understand that wasmer allows stateful execution, but to be more specific what I am looking for is some finer way to control how many instances are instantiated and to which instance a given client may connect to. One of my current projects is a game, and to properly orchestrate the services I would need some way to direct multiple clients to the same instance based on latency, workload and other constraints.

Is there going to be some better/more expressive APIs to orchestrate your deployments, or will wasmer take a very hands-off approach and make assumptions about use-cases like cloudflare has done with workers?

fanweixiao commented 1 year ago

Hi @syrusakbary, I need test UDP support.

DrewRidley commented 1 year ago

Glad to hear you guys are working on UDP! I am super excited about the future of wasm and specifically wasmer edge.

Is there any update on whether some unique orchestration workloads will be supported? I am specifically interested in some pretty fine grain control over when and where instances are spun up, and I think with a lot of UDP workloads instances cannot merely be spun up as requests come in.

I know its early on and I know a big portion of interested parties will be working on webservers and related technologies, but I think wasmer-edge can truly shine as a serverless provider if they offer more granular orchestration control that suites needs outside of the traditional "request >> instance" model that most serverless providers follow.

Thanks, Drew.

zzzej commented 6 months ago

Are websockets supported? Like for a signaling server?

jake-danton commented 6 months ago

We currently have multiple websocket based applications that use Cloudflare's Durable Objects but are looking for other edge services that could support our use case.

eric-crowell commented 3 months ago

This sounds great! I believe this would be a great capability to expose. First application I wanted to deploy with Wasmer Edge was some low-latency data feed with the blended benefits of WebAssembly.