Workflow
Ruby finite-state-machine-inspired API for modeling workflow (by geekq)
AASM
AASM - State machines for Ruby classes (plain Ruby, ActiveRecord, Mongoid, NoBrainer, Dynamoid) (by aasm)
| Workflow | AASM | |
|---|---|---|
| - | 4 | |
| 1,776 | 5,101 | |
| 0.1% | 0.4% | |
| 6.3 | 8.6 | |
| about 1 year ago | 26 days 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.
Workflow
Posts with mentions or reviews of Workflow.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Workflow yet.
Tracking mentions began in Dec 2020.
AASM
Posts with mentions or reviews of AASM.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-21.
-
The New Three-Tier Application
When they get to what their implementation is, I’m not even sure what it is. Like how is the following different from a library, like acts-as_state_machine (https://github.com/aasm/aasm). Are they auto running the retries - in a background job which they handle (like “serverless” background job)?
“Implementing orchestration in a library connected to a database means you can eliminate the orchestration tier, pushing its functionality into the application tier (the library instruments your program) and the database tier (your workflow state is persisted to Postgres).“
-
Code review of an Order object implemented as a state machine
AASM gem is great too! Easy to use and actively maintained.
-
RoR Gems: Pin To Plane For Developing RoR Application
6. AASM
-
Validate state transition easily without any gem
You can use state machine gems, such as aasm to write validation. But the gem introduces new DSL to write state transition. It's too much just for validation.
What are some alternatives?
When comparing Workflow and AASM you can also consider the following projects:
FiniteMachine - A minimal finite state machine with a straightforward syntax.
State Machine - Adds support for creating state machines for attributes on any Ruby class
Statesman - A statesmanlike state machine library.
state_machines - Adds support for creating state machines for attributes on any Ruby class