u-service
Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code. (by serradura)
flow
Write modular and reusable business logic that's understandable and maintainable. (by Freshly)
u-service | flow | |
---|---|---|
3 | 2 | |
514 | 80 | |
- | - | |
3.1 | 0.0 | |
6 months ago | about 1 year 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.
u-service
Posts with mentions or reviews of u-service.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-13.
- Should I use service objects?
-
Utilizando o padrão interactor no Ruby on Rails
Version Documentation unreleased https://github.com/serradura/u-case/blob/main/README.md 4.5.1 https://github.com/serradura/u-case/blob/v4.x/README.md 3.1.0 https://github.com/serradura/u-case/blob/v3.x/README.md 2.6.0 https://github.com/serradura/u-case/blob/v2.x/README.md 1.1.0 https://github.com/serradura/u-case/blob/v1.x/README.md
flow
Posts with mentions or reviews of flow.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-13.
-
Should I use service objects?
My company invented Flow for this: https://github.com/Freshly/flow
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
What are some alternatives?
When comparing u-service and flow you can also consider the following projects:
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
actor-rails - Actor Rails provides Rails support to the Actor service objects
Interactor - Interactor provides a common interface for performing complex user interactions.
router - Ruby/Rack HTTP router
Pathway - Define your business logic in simple steps
validations - Validation mixin for Ruby objects
wisper - A micro library providing Ruby objects with Publish-Subscribe capabilities
actor - Composable Ruby service objects
Light Service - Series of Actions with an emphasis on simplicity.
Rectify - Build maintainable Rails apps
Hanami::Utils - Ruby core extentions and class utilities for Hanami