eventually-rs
Event Sourcing for Rust (by eventually-rs)
eventually-go
Idiomatic Domain-driven Design, CQRS and Event Sourcing for Go (by eventually-rs)
eventually-rs | eventually-go | |
---|---|---|
3 | 3 | |
539 | 85 | |
0.7% | - | |
6.3 | 8.0 | |
20 days ago | 8 days ago | |
Rust | 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.
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
eventually-go
Posts with mentions or reviews of eventually-go.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-11.
-
Event sourcing a year later
Check out eventually to get a better idea: https://github.com/eventually-rs/eventually-go
- eventually-go: Idiomatic Event Sourcing for Go
What are some alternatives?
When comparing eventually-rs and eventually-go you can also consider the following projects:
thalo - An Event Sourcing runtime with WebAssembly & embedded event store
goengine - Engine provides you all the capabilities to build an Event sourced application in go
eventsourcing - Event Sourcing in Go
Go-EventSourcing-CQRS - Go Event Sourcing CQRS Microservice
simd-json - Rust port of simdjson
rsfbclient - Rust Firebird Client
wtf - WTF Dial is an example application written in Go.
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]
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀
eventually-rs vs thalo
eventually-go vs goengine
eventually-rs vs eventsourcing
eventually-go vs Go-EventSourcing-CQRS
eventually-rs vs simd-json
eventually-go vs eventsourcing
eventually-rs vs rsfbclient
eventually-go vs wtf
eventually-rs vs saving-goals-go
eventually-go vs saving-goals-go
eventually-rs vs goengine
eventually-rs vs plotters