Sequent
CQRS & event sourcing framework for Ruby (by zilverline)
Rails Event Store
A Ruby implementation of an Event Store based on Active Record (by RailsEventStore)
Our great sponsors
| Sequent | Rails Event Store | |
|---|---|---|
| 5 | 6 | |
| 534 | 1,375 | |
| 0.2% | 0.9% | |
| 8.9 | 9.7 | |
| 19 days ago | 12 days ago | |
| Ruby | 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.
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).
Rails Event Store
Posts with mentions or reviews of Rails Event Store.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-17.
-
Organize Business Logic in Your Ruby on Rails Application
That's not to say it's not an interesting pattern. You should use it if you have advanced reporting requirements, for example. If you want to learn more about it, look at Rails Event Store.
-
How would you build an audit log in Rails for a high-throughput API?
If you need something actually structured, you could use an Event Store
-
OOP vs. services for organizing business logic: is there a third way?
Rails Event Store – for an event-driven architecture
-
Event Store with Rails
Does anyone implemented or used a gem such as https://railseventstore.org to support Event Store in their Rails app?
-
What would you like to see in a Ruby web framework?
Events and CQRS are what rails event store deals with. I don't have any experience with it, though. It seems that they also support ROM and Sequel outside of Rails.
-
Yard Sale - event-driven e-commerce
This is a test project for Mongo Atlas hackathon. It uses RailsEventStore with PostgreSQL as an event store and MongoDB on Atlas for read models.
What are some alternatives?
When comparing Sequent and Rails Event Store you can also consider the following projects:
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
Cells - View components for Ruby and Rails.
Trailblazer - The advanced business logic framework for Ruby.
Clowne - A flexible gem for cloning models
Rectify - Build maintainable Rails apps
ActiveInteraction - :briefcase: Manage application specific business logic.
Responders - A set of Rails responders to dry up your application
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
dry-transaction - Business transaction DSL
Sequent vs SimpleCommand
Rails Event Store vs wisper
Sequent vs Cells
Rails Event Store vs Trailblazer
Sequent vs Clowne
Rails Event Store vs Rectify
Sequent vs Trailblazer
Rails Event Store vs ActiveInteraction
Sequent vs Responders
Rails Event Store vs u-service
Sequent vs dry-transaction
Rails Event Store vs dry-transaction