go-bench-stream
🌊 Go Benchmarks for Stream Processing (by nikolaydubina)
tabc
Time-Aware Bytestream Consolidator for Go (by thejerf)
go-bench-stream | tabc | |
---|---|---|
2 | 2 | |
2 | 1 | |
- | - | |
0.0 | 10.0 | |
almost 2 years ago | over 5 years ago | |
Go | Go | |
MIT License | MIT License |
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.
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-bench-stream
Posts with mentions or reviews of go-bench-stream.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-25.
-
Question on Stream Processing patterns in Go
Check the diagram if you are interested what I meant on Iterators! (basically transforming Read([]byte) calls into Next() MyType calls https://github.com/nikolaydubina/go-bench-stream
tabc
Posts with mentions or reviews of tabc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-25.
-
Question on Stream Processing patterns in Go
I do have one complicated one at thejerf/tabc, which takes an intermittent series of read events (like from users typing, as opposed to a file reading) and breaks it up by time. (This is technically not a decator, though, as it consumes an io.Reader but presents a different interface.) I have one that I've never written but have been tempted to write that would align incoming io.Reader byte streams on unicode boundaries, so that users of this decorator can assume that they're always receiving a complete Unicode value and take appropriate actions, though that raises a whole world of issues around the definition of "complete Unicode value" you want to use (codepoint, "glyph", etc.).
-
looking for examples of a "batch release threshold" pattern
I have this: https://github.com/thejerf/tabc
What are some alternatives?
When comparing go-bench-stream and tabc you can also consider the following projects:
Benthos - Fancy stream processing made operationally mundane
go-ml-benchmarks - ⏱ Benchmarks of machine learning inference for Go
compare-go-json - A comparison of several go JSON packages.
fpmoney - 🧧 Fixed-Point Decimal Money
watermill - Building event-driven applications the easy way in Go.