How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
The main features of itsubaki/gostream are: Data Processing and Streams.
Projects with overlapping indexed features include: jeffail/benthos — Benthos is a declarative stream processor and data integration pipeline used to route, transform, and filter… reugn/go-streams — A lightweight stream processing library for Go. s8sg/goflow — A Golang based high performance, scalable and distributed workflow framework. threedotslabs/watermill — Watermill is a Go library for building event-driven applications. It provides a framework for implementing… uber/cadence — Cadence is a distributed workflow orchestration engine designed to execute long-running, asynchronous business logic…
Benthos is a declarative stream processor and data integration pipeline used to route, transform, and filter information between disparate services. It functions as an at-least-once message broker and change data capture engine, using a transaction model to guarantee message delivery despite system crashes or server faults. The system is defined by an observability-first approach, featuring built-in HTTP health probes, performance metrics export, and distributed request flow tracing. It utilizes a plugin architecture that allows the core engine to be extended with custom binaries for new inpu
A lightweight stream processing library for Go
A Golang based high performance, scalable and distributed workflow framework
Watermill is a Go library for building event-driven applications. It provides a framework for implementing event-driven architectures through a consistent interface for message publishing and subscribing, featuring a pub/sub message router and event stream processing pipelines. The library uses interface-based abstractions to decouple message producers and consumers from the underlying message broker. This allows different messaging technologies to be swapped via plugin-based broker integration. It employs a router-driven dispatch system and middleware-based pipelines to manage cross-cutting