melody
ws
| melody | ws | |
|---|---|---|
| 4 | 14 | |
| 3,560 | 5,958 | |
| - | - | |
| 6.4 | 5.9 | |
| 16 days ago | 4 months ago | |
| Go | Go | |
| BSD 2-clause "Simplified" 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.
melody
-
Release v1.2.0 · gobwas/ws - WebSocket library for Go.
I just recently started using melody (https://github.com/olahol/melody), which claims to be like gorilla websockets. I found it pretty quick to understand, but I haven't used it for anything that complicated. Has anyone used both melody and gobwas/ws? I'm mostly interested in ergonomics, not performance.
-
websockets
I recommend https://github.com/olahol/melody It is based on gorilla websocket but abstracts the tedious part. I have used it in my distributed chat side project
-
Gorilla/websocket or Melody?
I'm looking to build a game server that uses web sockets to communicate with clients, I've looked into some of the libraries and the main ones seem to be gorilla websockets and melody.
-
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
I like github.com/olahol/melody which is based on gorilla/webscocket very much and use it in some of my projects which do not have too many online connections.
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?
go-socket.io - socket.io library for golang, a realtime application framework.
1m-go-websockets - handling 1M websockets connections in Go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
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.
Fiber - ⚡️ Express inspired web framework written in Go
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
Iris - The fastest HTTP/2 Go Web Framework. New, modern and easy to learn. Fast development with Code you control. Unbeatable cost-performance ratio :rocket:
websocket - Minimal and idiomatic WebSocket library for Go
rye - A tiny http middleware for Golang with added handlers for common needs.
websocket - A fast, well-tested and widely used WebSocket implementation for Go.
Beego - beego is an open-source, high-performance web framework for the Go programming language.
fast - Check your internet speed/bandwidth right from your terminal. Built on Golang using chromedp