goengine
Engine provides you all the capabilities to build an Event sourced application in go (by hellofresh)
eventually-rs
Event Sourcing for Rust (by eventually-rs)
| goengine | eventually-rs | |
|---|---|---|
| 1 | 3 | |
| 126 | 539 | |
| 0.0% | 0.7% | |
| 6.7 | 6.3 | |
| about 2 months ago | 16 days ago | |
| Go | Rust | |
| 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.
goengine
Posts with mentions or reviews of goengine.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-02.
-
eventually-go: Idiomatic Event Sourcing for Go
I took some inspiration from goengine (regarding Aggregates) and expanded on that, and now the library supports quite a number of features, such as: * Subscriptions * In-memory and PostgreSQL-based Event Store implementation (inspired by eventually-rs) * Command handling * Projections (both for long-running processes -- a.k.a. Process Managers -- and Read Models) * Correlation extension * Opentracing extension * Descriptive test scenarios support for TDD
eventually-rs
Posts with mentions or reviews of eventually-rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-11.
-
Best practices for designing traits in public crates?
While I like now that there is a single trait involved (which also makes it easier to write super-types), I don't like the requirement for those associated type names like type GetError and type SaveError. I also don't particularly like the idea of hiding everything behind a single Error type, as it kinda defeats the purpose of having such a nice type system like the one Rust has.
-
eventually-go: Idiomatic Event Sourcing for Go
But you can read it in the Rust version README! :D
What are some alternatives?
When comparing goengine and eventually-rs you can also consider the following projects:
eventually-go - Idiomatic Domain-driven Design, CQRS and Event Sourcing for Go
thalo - An Event Sourcing runtime with WebAssembly & embedded event store
saving-goals-go - Example Event-Sourced microservice using https://github.com/eventually-rs/eventually-go [Moved to: https://github.com/get-eventually/saving-goals-go]
eventsourcing - Event Sourcing in Go
sourcegraph - Code AI platform with Code Search & Cody
simd-json - Rust port of simdjson
rsfbclient - Rust Firebird Client
OpenDiablo2 - An open source re-implementation of Diablo 2
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀
goengine vs eventually-go
eventually-rs vs thalo
goengine vs saving-goals-go
eventually-rs vs eventsourcing
goengine vs sourcegraph
eventually-rs vs simd-json
goengine vs eventsourcing
eventually-rs vs rsfbclient
goengine vs OpenDiablo2
eventually-rs vs saving-goals-go
eventually-rs vs eventually-go
eventually-rs vs plotters