go-streams
waggy
go-streams | waggy | |
---|---|---|
9 | 8 | |
1,754 | 38 | |
- | - | |
6.6 | 3.0 | |
18 days ago | about 1 year ago | |
Go | Go | |
MIT License | BSD 3-clause "New" or "Revised" 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.
go-streams
-
When is go not a good choice?
Have you looked at this streaming library? https://github.com/reugn/go-streams
-
Gorilla Web Toolkit is now in archive only mode
Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos
- Go-Streams v0.8.0 released, providing support for generic transformers and extended flow capabilities
- The most lightweight (zero-dependency core) yet comprehensive stream processing library for Go
- A powerful stream processing library with a modular architecture
- A flexible and powerful stream processing library for Go
- A flexible and powerful stream processing library for Go.
- A modular version of `go-streams` - the simple and powerful stream processing library, is released, with extended connector support.
waggy
-
what's your recommended router? chi, mux, something else?
Chi for work, my own router for personal projects
-
Waggy hits v0.8.0 with support for custom middleware, listening and serving on a specific host and port address, and more!!
And in that time, I’ve gotten the router I’ve been working on, Waggy, up to a new version of v0.8.0!! Along with some minor bug fixes, some refactoring, and restructuring changes, there is now full support for custom middleware and listening and serving on a specific host:port address.
-
What mux/router to use now a days?
For work, we’ve switched to Chi. For personal projects, I use a router I’ve been built and have been working on myself
-
Gorilla Web Toolkit is now in archive only mode
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
-
Waggy v0.3 Released!!
Waggy v0.3 is out now!! Along with some minor bug fixes, v0.3 comes with two major improvements, being the ability to configure loggers for WaggyRouters and WaggyHandlers alike, as well as a convenience wrapper for serving files as responses. One other big unplanned, but welcome improvement is the ability to use Waggy in conjunction with Fermyon’s Spin Go SDK for writing WAGI microservices that can also make outgoing HTTP calls.
-
Waggy v2 Release
Waggy has released v2!!
-
The best Go framework: no framework? (Three Dots Tech)
With the rising popularity of WASM, I’d probably use something like wazero coupled with the library I just wrote and released, waggy for writing the individual handlers for each route, though.
- Waggy: A dead simple library for writing WAGI API Handlers in Go
What are some alternatives?
RxGo - Reactive Extensions for the Go language.
gorilla-mux - A fork of gorilla/mux, the powerful HTTP router and URL matcher for building Go web servers with 🦍
stream - Go Stream, like Java 8 Stream.
httprouter - A high performance HTTP request router that scales well
machine - Machine is a workflow/pipeline library for processing data
jwtauth - JWT authentication middleware for Go HTTP services
goio - An implementation of IO, Stream, Fiber for golang inspired by cats and fs2
otelchi - OpenTelemetry instrumentation for go-chi/chi
cuelake - Use SQL to build ELT pipelines on a data lakehouse.
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
Benthos - Fancy stream processing made operationally mundane
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍