centrifuge
ws
centrifuge | ws | |
---|---|---|
13 | 14 | |
982 | 5,958 | |
1.9% | - | |
8.4 | 5.9 | |
2 days ago | 4 months ago | |
Go | Go | |
MIT License | MIT License |
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.
centrifuge
-
Centrifugo v5 - new major release of real-time messaging server written in Go
BTW, Centrifugo is based on https://github.com/centrifugal/centrifuge Go library which may provide much more control and flexibility for Gophers than a standalone server and can be embedded to any Go app leveraging all Centrifugo client SDKs.
-
Websocket memory usage
There are libraries which provide more advanced APIs for creating real-time applications, for example https://github.com/centrifugal/centrifuge
- Centrifuge - multi-transport real-time messaging library with built-in scalability
-
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
- Millions of Active WebSockets with Node.js
-
Best way for broadcast message un websocket
What https://github.com/centrifugal/centrifuge does:
-
Gorilla/websocket or Melody?
Have you considered https://github.com/centrifugal/centrifuge? It also uses Gorilla WebSocket for WebSocket transport at the moment – but it's hidden inside and may be replaced if needed since Transport interface is pluggable. It's more heavyweight though than both Melody and Gorilla WebSocket but provides much more functionality out-of-the-box.
-
What libraries are missing?
Not a Socket.IO compatible but maybe you will find it useful/interesting: https://github.com/centrifugal/centrifuge
-
Centrifugo v4 released – with own WebSocket emulation layer, optimized client protocol, unified SDK behavior, experimental HTTP/3 and WebTransport support
Thanks! BTW, Centrifugo's core is based on https://github.com/centrifugal/centrifuge Go library - which theoretically can be more flexible and extensible solution for Go developers than Centrifugo server since server dictates some auth/permission/channel/api rules.
-
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.
ws
-
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.
What are some alternatives?
Socket.io - Realtime application framework (Node.JS server)
1m-go-websockets - handling 1M websockets connections in Go
websocket - A fast, well-tested and widely used WebSocket implementation for Go.
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.
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
beaver - 💨 A real time messaging system to build a scalable in-app notifications, multiplayer games, chat apps in web and mobile apps.
websocket - Minimal and idiomatic WebSocket library for Go
jetstream - JetStream Utilities
kcptun - A Stable & Secure Tunnel based on KCP with N:M multiplexing and FEC. Available for ARM, MIPS, 386 and AMD64。N:M 多重化と FEC を備えた KCP に基づく安定した安全なトンネル。 N:M 다중화 및 FEC를 사용하는 KCP 기반의 안정적이고 안전한 터널입니다. Un tunnel stable et sécurisé basé sur KCP avec multiplexage N:M et FEC.
fast - Check your internet speed/bandwidth right from your terminal. Built on Golang using chromedp