wasmws
wasmws: Webassembly (WASM) Websockets for Go applications (by tarndt)
nbio
Pure Go 1000k+ connections solution, support tls/http1.x/websocket and basically compatible with net/http, with high-performance and low memory cost, non-blocking, event-driven, easy-to-use. (by lesismal)
| wasmws | nbio | |
|---|---|---|
| 5 | 10 | |
| 61 | 2,012 | |
| - | - | |
| 0.0 | 9.3 | |
| over 2 years ago | 5 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wasmws
Posts with mentions or reviews of wasmws.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-23.
-
Is there an alternative to gorilla websocket?
Thanks for writing this! I found it really great to use when I wrote https://github.com/tarndt/wasmws
-
Goomerang 🪃 A protocol buffers over websockets communications library
Before looking at the readme, I thought this was an alternative to using https://github.com/tarndt/wasmws which lets you use gRPC over websockets so that you can use gPRC via WASM without needing an http to gRPC gateway. Now I'm understanding a bit differently. It looks like this uses protobufs but doesn't have anything to do with gRPC at all, instead implementing some of the communication parts of gRPC while ignoring the generation of services but instead focusing a bit more on message routing and pub/sub that you would probably still need NATS.io for if you were using gRPC.
-
Even More Minor Features in Go 1.18
The hijacking a websocket works very well, live in the future today! https://github.com/tarndt/wasmws
-
Migrating from nodejs to go codebase using gopherjs
Everything said above is valid, but if you do think you have a need to transpile... consider running any Go frontend code as WASM rather than Javascript. A few years ago I started doing my frontends and backends all in Go and its been wonderful. I even wrote a library so I could use gRPC from my WASM/Go frontends rather than REST: https://github.com/tarndt/wasmws . Extra wonderful, at least for my tastes. Once caveat is if your brotli compressed, CDN/browser cached, etagged Go WASM is still to big, you can usually make it even smaller by using tinygo rather than the std tool chain for the compiling to WASM.
-
Go and gRPC is just so intuitive. Here's a detailed full-stack flow with gRPC-Web, Go and React. Also, there is a medium story focused on explaining how such a setup might boost efficiency and the step-by-step implementation.
A while back I was writing a pure Go frontend app (WASM) and I wrote this so I could use gRPC rather than REST to talk to my backend: https://github.com/tarndt/wasmws
nbio
Posts with mentions or reviews of nbio.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-24.
-
Websocket memory usage
There is also https://github.com/lesismal/nbio library
- Is there an alternative to gorilla websocket?
- Gorilla/websocket or Melody?
- nbio's new features to keep balance between performance and
-
Pure Go 1000k+ connections solution, support tls/http1.x/websocket and basically compatible with net/http, with high-performance and low memory cost, non-blocking, event-driven, easy-to-use
There were already some other poller frameworks before nbio, such as evio, easygo, gev, gnet.
- Websocket server design
-
Lightweight Websocket library a simple game server?
I was using gobwas and then switched to https://github.com/lesismal/nbio.
-
A netpoll alternative that works on Windows?
Since you seem to know the space, may I ask you what your opinion on https://github.com/lesismal/nbio is and if you think that is also a good option for websocket usage?
What are some alternatives?
When comparing wasmws and nbio you can also consider the following projects:
goomerang - A small communications library based on protocol buffers over websockets
websocket - Minimal and idiomatic WebSocket library for Go
wombat - Cross platform gRPC client
fullproxy - Proxy toolkit including SOCKS5, HTTP, port forward and reverse base proxying
grpc-web - gRPC for Web Clients
gnet - 🚀 gnet is a high-performance, lightweight, non-blocking, event-driven networking framework written in pure Go./ gnet 是一个高性能、轻量级、非阻塞的事件驱动 Go 网络框架。
goja - ECMAScript/JavaScript engine in pure Go
httpproxy - HTTP proxy handler and dialer
ws - Tiny WebSocket library for Go.
ote - ote updates a packages' go.mod file with a comment next to all dependencies that are test dependencies; identifying them as such.
fasthttp - Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http