Gorilla Web Toolkit is now in archive only mode

This page summarizes the projects mentioned and recommended in the original post on /r/golang

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • mux

    Discontinued A powerful HTTP router and URL matcher for building Go web servers with 🦍

  • Initially found out about this via this issue thread here where they were looking for new maintainers.

  • waggy

    The dead simple, easy-to-use library for writing HTTP handlers and routers in Go that can be used in standard HTTP server environments or in WAGI (Web Assembly Gateway Interface) environments

  • I have a library that I’ve been working on for a different environment (WASM specifically), but I can be used as a regular HTTP router and provides access to URL path params. Check it out here

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • websocket

    Discontinued A fast, well-tested and widely used WebSocket implementation for Go.

  • 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.

  • websocket

    Minimal and idiomatic WebSocket library for Go (by nhooyr)

  • go-streams

    A lightweight stream processing library for Go

  • Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos

  • neffos

    A modern, fast and scalable websocket framework with elegant API written in Go

  • Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos

  • ws

    Tiny WebSocket library for Go. (by gobwas)

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Release v1.2.0 · gobwas/ws - WebSocket library for Go.

    3 projects | /r/golang | 10 Apr 2023
  • Is there an alternative to gorilla websocket?

    9 projects | /r/golang | 23 Feb 2023
  • As gorilla websocket has been archived which library can we use?

    1 project | /r/websocket | 23 Feb 2023
  • WebSockets in Go: A hijackers' perspective

    1 project | dev.to | 11 Feb 2023
  • How to install gorilla websocket in go 1.20?

    1 project | /r/golang | 4 Feb 2023