Hanami::Model
Ruby persistence framework with entities and repositories (by hanami)
Light Service
Series of Actions with an emphasis on simplicity. (by adomokos)
| Hanami::Model | Light Service | |
|---|---|---|
| 1 | 5 | |
| 445 | 813 | |
| 0.0% | - | |
| 0.0 | 0.6 | |
| 4 months ago | 5 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.
Hanami::Model
Posts with mentions or reviews of Hanami::Model.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-20.
-
Utilizando o padrão interactor no Ruby on Rails
Hanami::Model - Persistence with entities, repositories and data mapper
Light Service
Posts with mentions or reviews of Light Service.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-03.
-
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.
What are some alternatives?
When comparing Hanami::Model and Light Service you can also consider the following projects:
ROM - Data mapping and persistence toolkit for Ruby
Interactor - Interactor provides a common interface for performing complex user interactions.
ActiveRecord
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
Sequel - Sequel: The Database Toolkit for Ruby
Rectify - Build maintainable Rails apps
Mongoid - The Official Ruby Object Mapper for MongoDB
Trailblazer - The advanced business logic framework for Ruby.
Redis-Objects - Map Redis types directly to Ruby objects
ActiveInteraction - :briefcase: Manage application specific business logic.
MongoMapper - A Ruby Object Mapper for Mongo
Mutations - Compose your business logic into commands that sanitize and validate input.
Hanami::Model vs ROM
Light Service vs Interactor
Hanami::Model vs ActiveRecord
Light Service vs wisper
Hanami::Model vs Sequel
Light Service vs Rectify
Hanami::Model vs Mongoid
Light Service vs Trailblazer
Hanami::Model vs Redis-Objects
Light Service vs ActiveInteraction
Hanami::Model vs MongoMapper
Light Service vs Mutations