SuperModule
wisper
Our great sponsors
| SuperModule | wisper | |
|---|---|---|
| - | 6 | |
| 137 | 3,229 | |
| - | - | |
| 0.0 | 1.5 | |
| over 2 years ago | about 2 months ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
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.
SuperModule
We haven't tracked posts mentioning SuperModule yet.
Tracking mentions began in Dec 2020.
wisper
-
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.
What are some alternatives?
simple_active_link_to - Simple rails view helper to manage "active" state of a link
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
EasilyTypable - Ruby module that facilitates English-like type checking in an inheritance hierarchy via "type_name?" methods
Interactor - Interactor provides a common interface for performing complex user interactions.
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
Responders - A set of Rails responders to dry up your application
Cells - View components for Ruby and Rails.
Mutations - Compose your business logic into commands that sanitize and validate input.
Light Service - Series of Actions with an emphasis on simplicity.
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!