Light Service
wisper
Our great sponsors
Light Service | wisper | |
---|---|---|
5 | 6 | |
813 | 3,229 | |
- | - | |
0.6 | 1.5 | |
5 months 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.
Light Service
-
The Decree Design Pattern (Ruby on Rails)
check out the `light-service` gem - it lets you create services that use this pattern and compose them into complex flows: https://github.com/adomokos/light-service
-
How to avoid if/else with different ramifications
Similar to the above recommendations of Railway Orientated Programming and the Interactor gem, I use the Light Service gem. While it can sometimes be a bit verbose it excels in code reuse, testability, and composition.
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
-
Ten Ruby gems for Rails you should definitely know about
LightService
-
The Ruby Unbundled Series: Services vs. Objects - The Battle for Decomposition and Reuse
You can implement the service pattern as a PORO, but it helps to use one of the gems available to aid in code structure, orchestration, and error handling. The LightService gem provides a nice implementation without adding hardly any overhead. It’s design is very simple, as shown in the diagram below. An organizer is used to define the sequential workflow, which is made up of one or more actions. An error in any of the actions will short-circuit the entire workflow.
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?
Interactor - Interactor provides a common interface for performing complex user interactions.
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Rectify - Build maintainable Rails apps
Trailblazer - The advanced business logic framework for Ruby.
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
ActiveInteraction - :briefcase: Manage application specific business logic.
Cells - View components for Ruby and Rails.
Mutations - Compose your business logic into commands that sanitize and validate input.
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model