| ws | jetstream | |
|---|---|---|
| 14 | 2 | |
| 5,969 | 428 | |
| - | - | |
| 5.6 | 8.4 | |
| 4 days ago | almost 3 years ago | |
| Go | Dockerfile | |
| MIT License | Apache License 2.0 |
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.
ws
Posts with mentions or reviews of ws.
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
Then take a look at this article - https://www.freecodecamp.org/news/million-websockets-and-go-cc58418460bb/ - using external from Go std lib epoll implementation and https://github.com/gobwas/ws lib it's possible to reduce memory usage per connection drastically. Though keep in mind that this approach is not obvious to implement right and you better to go with STD lib.
-
Elixir or golang which wiil be good for large websocket connections.
Yes, but there are two excelent libs for golang websockets - https://github.com/gobwas/ws - https://github.com/centrifugal/centrifuge
- WebSocket library for Go – gobwas/ws – Release v1.2.0
- Release v1.2.0 · gobwas/ws - WebSocket library for Go.
-
Is there an alternative to gorilla websocket?
Yes, I find https://github.com/gobwas/ws to be far superior. It has a lot more ability to customize and get high performance as well as a utility package that is much higher level and makes it easy to use. It doesn't have some of the problems of gorilla because they didn't have to support people already depending on it
- Gorilla Web Toolkit is now in archive only mode
-
Gorilla toolkit maintainers are stepping down and have been looking for new maintainers. The project could otherwise be archived.
There's https://github.com/gobwas/ws and https://github.com/nhooyr/websocket but neither have seen a commit in over a year
-
Centrifugo v4 released – with own WebSocket emulation layer, optimized client protocol, unified SDK behavior, experimental HTTP/3 and WebTransport support
Oh, thanks! And sorry for still not switching to https://github.com/gobwas/ws :)
-
TCP or websockets for chat server
Hello, +1 to WebSockets. If you need to choose WS library – go with https://github.com/gorilla/websocket or https://github.com/gobwas/ws. You can also look at Centrifugo server (https://centrifugal.dev/, supports WebSocket, SockJS bidi transports, also EventSource, HTTP-streaming, GRPC unidirectional transports and many builtin features) or https://github.com/centrifugal/centrifuge Go library.
-
How does TCP connection in net package handle disconnects?
I prefer gobwas/ws because it has the high level "easy mode" (though some things will still be a small learning curve if you are used to REST mostly) and a low level API that you can dive into if you need very high performance and don't mind getting deeply into the details. It has the advantage of being written much after the most popular Gorilla websocket implementation which has some complexity and other issues that it can't totally remove in order to keep compatibility for all of its many users. It's also battle-tested via mail.ru. See A Million Websocket and Go for more details on its inception.
jetstream
Posts with mentions or reviews of jetstream.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-20.
-
Centrifugo v4 released – with own WebSocket emulation layer, optimized client protocol, unified SDK behavior, experimental HTTP/3 and WebTransport support
Centrifugo can use Nats as PUB/SUB broker. I also tried to use Jetstream to implement Centrifugo history/recovery semantics – unfortunately Jetstream does not fit us very well as streams must be created over a separate call to admin API, and it's not possible to iterate/paginate over Jetstream streams to be suitable to current Centrifugo message history and recovery semantics (I asked about support for this – unfortunately the issue was closed and required API not implemented - https://github.com/nats-io/jetstream/issues/266, suggested solution is far from optimal for our use case).
- ZooKeeper-free Kafka is out. First Demo
What are some alternatives?
When comparing ws and jetstream you can also consider the following projects:
1m-go-websockets - handling 1M websockets connections in Go
Apache Kafka - Mirror of Apache Kafka
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.
liftbridge - Lightweight, fault-tolerant message streams.
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
websocket - Minimal and idiomatic WebSocket library for Go
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
websocket - A fast, well-tested and widely used WebSocket implementation for Go.
kafkacat - Generic command line non-JVM Apache Kafka producer and consumer [Moved to: https://github.com/edenhill/kcat]
fast - Check your internet speed/bandwidth right from your terminal. Built on Golang using chromedp
jepsen - A framework for distributed systems verification, with fault injection