wisper
A micro library providing Ruby objects with Publish-Subscribe capabilities (by krisleech)
Rails Event Store
A Ruby implementation of an Event Store based on Active Record (by RailsEventStore)
| wisper | Rails Event Store | |
|---|---|---|
| 6 | 6 | |
| 3,301 | 1,445 | |
| 0.4% | 1.0% | |
| 4.2 | 9.5 | |
| 9 months ago | 19 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.
wisper
Posts with mentions or reviews of wisper.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-21.
-
Publish/Subscribe with Sidekiq
Wisper: A Ruby gem providing a decoupled communication layer between different parts of an application -> I personally dislike wisper. I used it in the past and dislike the way of defining subscribers in a global way. I wanted topics to be arbitrary and each class to define what to subscribe for itself.
-
OOP vs. services for organizing business logic: is there a third way?
Wisper – the Publish-Subscribe design pattern
-
Event Store with Rails
I haven't used it, but we're also considering it in our app for quite some time. Our main issue is mostly that our codebase is super coupled, especially some older code, and using events as a means of communication between different modules of the app can be nice way of decoupling things. I think this is the most common usecase, and for this you don't necessarily even need to persist the events, and also something like wisper might be useful https://github.com/krisleech/wisper.
-
Rails Google Cloud PubSub options
Whisper (not updated since 2020)
-
How to avoid if/else with different ramifications
I would use events. Every services broadcast its results and everything that needs to listen for them. It also great to decouple dependencies between services. I like the Wisper gem : https://github.com/krisleech/wisper
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
We follow the interactor pattern to store our business logic. So we mainly have skinny controllers, skinny models and then interactors. We also don't use ActiveRecord callbacks very much, we primarily use Wisper to broadcast events and then various domains can subscribe to the events they care about and respond accordingly.
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 wisper and Rails Event Store you can also consider the following projects:
Cells - View components for Ruby and Rails.
Sequent - CQRS & event sourcing framework for Ruby
Interactor - Interactor provides a common interface for performing complex user interactions.
Mutations - Compose your business logic into commands that sanitize and validate input.
Light Service - Series of Actions with an emphasis on simplicity.
Rectify - Build maintainable Rails apps