session alternatives and similar packages
Based on the "Web Frameworks" category.
Alternatively, view session alternatives based on common mentions on social networks and blogs.
-
Gin
Gin is a high-performance HTTP web framework written in Go. It provides a Martini-like API but with significantly better performance鈥攗p to 40 times faster鈥攖hanks to httprouter. Gin is designed for building REST APIs, web applications, and microservices. -
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: -
Gorilla WebSocket
DISCONTINUED. A fast, well-tested and widely used WebSocket implementation for Go. -
GoFr
An opinionated GoLang framework for accelerated microservice development. Built in support for databases and observability. -
goa
Design-first Go framework that generates API code, documentation, and clients. Define once in an elegant DSL, deploy as HTTP and gRPC services with zero drift between code and docs. -
Huma
A modern, simple, fast & flexible micro framework for building HTTP REST/RPC APIs in Go backed by OpenAPI 3 and JSON Schema. -
Faygo
Faygo is a fast and concise Go Web framework that can be used to develop high-performance web app(especially API) with fewer codes. Just define a struct handler, faygo will automatically bind/verify the request parameters and generate the online API doc. -
go-server-timing
DISCONTINUED. Go (golang) library for creating and consuming HTTP Server-Timing headers -
goshs
Feature-rich single-binary file server for red teamers and developers. HTTP/S 路 WebDAV 路 FTP/SFTP 路 SMB 路 LDAP/S 路 NTLM hash capture 路 DNS/SMTP callbacks 路 TLS 路 Auth 路 Share links. A powerful python3 -m http.server replacement.
SaaSHub - Software Alternatives and Reviews
Do you think we are missing an alternative of session or a related project?
Popular Comparisons
README
Session
The Go standard library includes a nice http server, but unfortunately it lacks a very basic and important feature: HTTP session management.
This package provides an easy-to-use, extensible and secure session implementation and management. Package documentation can be found and godoc.org:
https://godoc.org/github.com/icza/session
This is "just" an HTTP session implementation and management, you can use it as-is, or with any existing Go web toolkits and frameworks.
Overview
There are 3 key players in the package:
Sessionis the (HTTP) session interface. We can use it to store and retrieve constant and variable attributes from it.Storeis a session store interface which is responsible to store sessions and make them retrievable by their IDs at the server side.Manageris a session manager interface which is responsible to acquire aSessionfrom an (incoming) HTTP request, and to add aSessionto an HTTP response to let the client know about the session. AManagerhas a backingStorewhich is responsible to manageSessionvalues at server side.
Players of this package are represented by interfaces, and various implementations are provided for all these players. You are not bound by the provided implementations, feel free to provide your own implementations for any of the players.
Usage
Usage can't be simpler than this. To get the current session associated with the http.Request:
sess := session.Get(r)
if sess == nil {
// No session (yet)
} else {
// We have a session, use it
}
To create a new session (e.g. on a successful login) and add it to an http.ResponseWriter (to let the client know about the session):
sess := session.NewSession()
session.Add(sess, w)
Let's see a more advanced session creation: let's provide a constant attribute (for the lifetime of the session) and an initial, variable attribute:
sess := session.NewSessionOptions(&session.SessOptions{
CAttrs: map[string]interface{}{"UserName": userName},
Attrs: map[string]interface{}{"Count": 1},
})
And to access these attributes and change value of "Count":
userName := sess.CAttr("UserName")
count := sess.Attr("Count").(int) // Type assertion, you might wanna check if it succeeds
sess.SetAttr("Count", count+1) // Increment count
(Of course variable attributes can be added later on too with Session.SetAttr(), not just at session creation.)
To remove a session (e.g. on logout):
session.Remove(sess, w)
Check out the session demo application which shows all these in action.
Google App Engine support
The package https://github.com/icza/gaesession provides support for Google App Engine (GAE) platform.
The gaesession implementation stores sessions in the Memcache and also saves sessions in the Datastore as a backup
in case data would be removed from the Memcache. This behaviour is optional, Datastore can be disabled completely.
You can also choose whether saving to Datastore happens synchronously (in the same goroutine)
or asynchronously (in another goroutine), resulting in faster response times.
For details and examples, please visit https://github.com/icza/gaesession.