eventually-go
Idiomatic Domain-driven Design, CQRS and Event Sourcing for Go (by eventually-rs)
wtf
WTF Dial is an example application written in Go. (by hallgren)
| eventually-go | wtf | |
|---|---|---|
| 3 | 2 | |
| 85 | 4 | |
| - | - | |
| 8.0 | 0.0 | |
| 8 days ago | about 3 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.
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
wtf
Posts with mentions or reviews of wtf.
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
A reason for the post is to get traction and others to use it to figure stuff like this out. When I ported the wtf-dial project to use this pkg the Timestamp property is used https://github.com/hallgren/wtf/blob/main/es_dial.go#L84 to set the last updated property. Reason and Timestamp is related to the event itself (it enrich the event) Correlation id relates to the the command that triggers the event and belongs in metadata. That sad this is my opinion and I can be dead wrong :)
What are some alternatives?
When comparing eventually-go and wtf you can also consider the following projects:
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
eventually-rs - Event Sourcing for Rust
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]