Sequent
CQRS & event sourcing framework for Ruby (by zilverline)
dry-transaction
Business transaction DSL (by dry-rb)
Our great sponsors
| Sequent | dry-transaction | |
|---|---|---|
| 5 | 2 | |
| 534 | 463 | |
| 0.2% | 0.9% | |
| 8.9 | 6.4 | |
| 20 days ago | 3 months 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).
dry-transaction
Posts with mentions or reviews of dry-transaction.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-13.
-
Introducing StepSequencer: A Non-Monadic Take on Railway-Oriented Programming in Ruby
While there are other libraries out there like Dry-Transaction and Interactor, StepSequencer stands out in its simplicity and flexibility. Here's why:
-
OOP vs. services for organizing business logic: is there a third way?
dry-transaction
What are some alternatives?
When comparing Sequent and dry-transaction you can also consider the following projects:
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Interactor - Interactor provides a common interface for performing complex user interactions.
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
Trailblazer - The advanced business logic framework for Ruby.
Cells - View components for Ruby and Rails.
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
Clowne - A flexible gem for cloning models
Responders - A set of Rails responders to dry up your application
Sequent vs Rails Event Store
dry-transaction vs Interactor
Sequent vs SimpleCommand
dry-transaction vs Trailblazer
Sequent vs Cells
dry-transaction vs Waterfall
Sequent vs Clowne
dry-transaction vs SimpleCommand
Sequent vs Trailblazer
dry-transaction vs Rails Event Store
Sequent vs Responders
dry-transaction vs Cells