saving-goals-go VS eventually-rs

Compare saving-goals-go vs eventually-rs and see what are their differences.

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] (by eventually-rs)
Golang golang-application golang-examples event-sourcing Cqrs cqrs-es Microservice

DISCONTINUED

Suggest alternative
Edit details

eventually-rs

Event Sourcing for Rust (by eventually-rs)
event-sourcing Rust rust-crate Ddd Cqrs Aggregate Eventstore
Source Code
Suggest alternative
Edit details
WorkOS
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
saving-goals-go eventually-rs
1 3
6 538
- 1.7%
5.4 6.4
about 3 years ago 9 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.

saving-goals-go

Posts with mentions or reviews of saving-goals-go. 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-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?
    3 projects | /r/rust | 11 Dec 2023
    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
    6 projects | /r/golang | 2 Feb 2021
    But you can read it in the Rust version README! :D

What are some alternatives?

When comparing saving-goals-go and eventually-rs you can also consider the following projects:

goengine - Engine provides you all the capabilities to build an Event sourced application in go

thalo - An Event Sourcing runtime with WebAssembly & embedded event store

eventsourcing - Event Sourcing in Go

Go-EventSourcing-CQRS - Go Event Sourcing CQRS Microservice

simd-json - Rust port of simdjson

eventually-go - Idiomatic Domain-driven Design, CQRS and Event Sourcing for Go

rsfbclient - Rust Firebird Client

saving-goals-go - Example Event-Sourced microservice using https://github.com/eventually-rs/eventually-go

plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀

saving-goals-go vs goengine eventually-rs vs thalo saving-goals-go vs eventsourcing eventually-rs vs eventsourcing saving-goals-go vs Go-EventSourcing-CQRS eventually-rs vs simd-json saving-goals-go vs eventually-go eventually-rs vs rsfbclient saving-goals-go vs saving-goals-go eventually-rs vs eventually-go eventually-rs vs goengine eventually-rs vs plotters