eventstore
Event store using PostgreSQL for persistence (by commanded)
Sequent
CQRS & event sourcing framework for Ruby (by zilverline)
| eventstore | Sequent | |
|---|---|---|
| 2 | 5 | |
| 1,010 | 535 | |
| 0.9% | 0.2% | |
| 7.5 | 8.8 | |
| 7 days ago | 26 days ago | |
| Elixir | Ruby | |
| 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.
eventstore
Posts with mentions or reviews of eventstore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-10.
-
Using CQRS in a simple Phoenix API with Commanded
Since I already had a Postgres database running, I decided to use EventStore rather than installing and babysitting EventStoreDB. To initialize the database and tables, I ran mix event_store.init and mix event_store.create.
-
Phoenix LiveView, but event-sourced
My goal is to use LiveView to update a price chart as trades are executed by the system. A LiveView process is a lot like a GenServer, with a bespoke process for each client, executing handle_* functions as the client does things. The first step to real-time chart updates is to trigger one of these handler functions in my LiveView controller when a trade is executed. I'm using Commanded's own EventStore library to dispatch and store my events, so their documentation is the place to start.
Sequent
Posts with mentions or reviews of Sequent.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-06.
-
OOP vs. services for organizing business logic: is there a third way?
Sequent – CQRS and event sourcing
-
Event Store with Rails
Co-author of the Sequent gem (https://www.sequent.io) here. Can confirm that it’s a great gem to build event sourced applications with (as long as you’re using PostgreSQL). It’s very battle tested as it has been extracted from/used in a web based accounting system that currently holds about 1 billion events in the event store.
- Accessing point in time data when data changes over time
-
Using CQRS in a simple Phoenix API with Commanded
I have been curious about the concepts of event sourcing and CQRS for a while— obsessively reading books like Practical Microservices (Garofolo) and Architecture Patterns with Python (Percival, Gregory), along with documentation for libraries like Sequent (Ruby), Commanded (Elixir).
What are some alternatives?
When comparing eventstore and Sequent you can also consider the following projects:
rethinkdb - Rethinkdb client in pure elixir (JSON protocol)
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
ecto - A toolkit for data mapping and language integrated query.
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
amnesia - Mnesia wrapper for Elixir.
Cells - View components for Ruby and Rails.
postgrex - PostgreSQL driver for Elixir
Clowne - A flexible gem for cloning models
extreme - Elixir Adapter for EventStore
Trailblazer - The advanced business logic framework for Ruby.
mongo - MongoDB driver for Elixir
Responders - A set of Rails responders to dry up your application