wisper
A micro library providing Ruby objects with Publish-Subscribe capabilities (by krisleech)
dry-transaction
Business transaction DSL (by dry-rb)
Our great sponsors
wisper | dry-transaction | |
---|---|---|
6 | 2 | |
3,229 | 463 | |
- | 0.9% | |
1.5 | 6.4 | |
about 2 months 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.
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.
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 wisper 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.
Trailblazer - The advanced business logic framework for Ruby.
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
Cells - View components for Ruby and Rails.
SimpleCommand - A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
Light Service - Series of Actions with an emphasis on simplicity.
wisper vs Rails Event Store
dry-transaction vs Interactor
wisper vs Interactor
dry-transaction vs Trailblazer
wisper vs Rocketman
dry-transaction vs Waterfall
wisper vs Cells
dry-transaction vs SimpleCommand
wisper vs Light Service
dry-transaction vs Rails Event Store
wisper vs Waterfall
dry-transaction vs Cells