websocket VS wstest

Compare websocket vs wstest and see what are their differences.

websocket

A fast, well-tested and widely used WebSocket implementation for Go. (by gorilla)

wstest

go websocket client for unit testing of a websocket handler (by posener)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
websocket wstest
44 0
18,557 102
- -
5.3 0.0
over 1 year ago about 3 years ago
Go Go
BSD 2-clause "Simplified" 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.

websocket

Posts with mentions or reviews of websocket. 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
    8 projects | /r/golang | 24 May 2023
    What I can say is that if you will use Gorilla Websocket (https://github.com/gorilla/websocket) (it's archived now unfortunately, but still super robust) - then you can go to sth like 15-20kb per connection - see https://github.com/FZambia/go_websocket_memory - to achieve this you need to reduce read buffer size, reuse write buffers, use goroutine after hijacking connection (following chat example in Gorilla WebSocket repo).
  • Is there an alternative to gorilla websocket?
    9 projects | /r/golang | 23 Feb 2023
    No Bugs? https://github.com/gorilla/websocket/issues Even if that were true at the time of stoping development, "No bugs" is something that can never be said for any software. I really wish this community stopped recomending to use abandoned libraries if only for the potential Security issues. A not maintained Library is a very lucrative target for vulnerability hunting.
    9 projects | /r/golang | 23 Feb 2023
  • gorilla fork
    2 projects | /r/golang | 21 Feb 2023
    The Gorilla WebSocket License says:
  • Polygon: Json Database System designed to run on small servers (as low as 16MB) and still be fast and flexible.
    7 projects | /r/golang | 29 Jan 2023
    As for Websockets, (https://github.com/gorilla/websocket) it uses ws.NextReader() to handle heavy loads of connections.
  • Best way for broadcast message un websocket
    2 projects | /r/golang | 1 Jan 2023
  • Gorilla/websocket or Melody?
    5 projects | /r/golang | 24 Dec 2022
    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.
  • any alternatives to gorilla websockets?
    5 projects | /r/golang | 11 Dec 2022
    github.com/gorilla/websocket is still very good. Most of the issues are questions and feature requests. It is used by 77,466 repositories on github. Just because it's archived doesn't mean you can't continue to use it.
  • Gorilla Web Toolkit is now in archive only mode
    8 projects | /r/golang | 9 Dec 2022
    I guess speaking to what I perceive as the Node perspective, I kinda don't get the idea that every library, no matter what it does, needs to have commits coming in every week to be "fresh" or it's bad. Me, I see a project with 311 commits that visibly isn't changing every week, and has a very positive community reputation, I see a library I'm more likely to use than the one that is still apparently in constant churn. Why should these codebases be seeing constant churn? What value would they be bringing to me? The standards haven't changed. The web hasn't changed. net/http hasn't changed. Nothing has changed that would necessitate them being in constant churn.
  • Sending 50-60 messages per minute from server to client with Websockets
    2 projects | /r/golang | 14 Aug 2022

wstest

Posts with mentions or reviews of wstest. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning wstest yet.
Tracking mentions began in Dec 2020.

What are some alternatives?

When comparing websocket and wstest you can also consider the following projects:

Fiber - ⚡️ Express inspired web framework written in Go

go-socket.io - socket.io library for golang, a realtime application framework.

Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications

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.

chi - lightweight, idiomatic and composable router for building Go HTTP services

Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.

centrifuge - Real-time messaging library for Go. The simplest way to add feature-rich and scalable WebSocket support to your application. The core of Centrifugo server.

RxGo - Reactive Extensions for the Go language.

go-kit - A standard library for microservices.

go-rabbitmq-example

Beego - beego is an open-source, high-performance web framework for the Go programming language.

kratos - Your ultimate Go microservices framework for the cloud-native era.