Setsy
Settings for classes backed by a database with defaults. (by joshmn)
Sequent
CQRS & event sourcing framework for Ruby (by zilverline)
Setsy | Sequent | |
---|---|---|
- | 5 | |
37 | 535 | |
- | 0.2% | |
0.0 | 8.8 | |
almost 6 years ago | 28 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.
Setsy
Posts with mentions or reviews of Setsy.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Setsy yet.
Tracking mentions began in Dec 2020.
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 Setsy and Sequent you can also consider the following projects:
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Clowne - A flexible gem for cloning models
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
Apotomo - MVC Components for Rails.
Cells - View components for Ruby and Rails.
Responders - A set of Rails responders to dry up your application
Trailblazer - The advanced business logic framework for Ruby.
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.