Group :: Desenvolvimento/Ruby
RPM: gem-dynflow
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 1.6.10-alt1.1
Data da compilação: 11 abril 2023, 12:25 ( 54.5 weeks ago )
Tamanho:: 587.28 Kb
Home page: https://github.com/Dynflow/dynflow
Licença: MIT
Sumário: DYNamic workFLOW orchestration engine
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 11 abril 2023, 12:25 ( 54.5 weeks ago )
Tamanho:: 587.28 Kb
Home page: https://github.com/Dynflow/dynflow
Licença: MIT
Sumário: DYNamic workFLOW orchestration engine
Descrição:
Dynflow [DYN(amic work)FLOW] is a workflow engine written in Ruby that allows
to:
* keep track of the progress of running process
* run the code asynchronously
* resume the process when something goes wrong, skip some steps when needed
* detect independent parts and run them concurrently
* compose simple actions into more complex scenarios
* extend the workflows from third-party libraries
* keep consistency between local transactional database and external services
* suspend the long-running steps, not blocking the thread pool
* cancel steps when possible
* extend the actions behavior with middlewares
* define the input/output interface between the building blocks (planned)
* define rollback for the workflow (planned)
* have multiple workers for distributing the load (planned)
Dynflow doesn't try to choose the best tool for the jobs, as the right tool
depends on the context. Instead, it provides interfaces for persistence,
transaction layer or executor implementation, giving you the last word in
choosing the right one (providing default implementations as well).
Mantenedor currente: Ruby Maintainers Team to:
* keep track of the progress of running process
* run the code asynchronously
* resume the process when something goes wrong, skip some steps when needed
* detect independent parts and run them concurrently
* compose simple actions into more complex scenarios
* extend the workflows from third-party libraries
* keep consistency between local transactional database and external services
* suspend the long-running steps, not blocking the thread pool
* cancel steps when possible
* extend the actions behavior with middlewares
* define the input/output interface between the building blocks (planned)
* define rollback for the workflow (planned)
* have multiple workers for distributing the load (planned)
Dynflow doesn't try to choose the best tool for the jobs, as the right tool
depends on the context. Instead, it provides interfaces for persistence,
transaction layer or executor implementation, giving you the last word in
choosing the right one (providing default implementations as well).
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- dynflow
- gem-dynflow
- gem-dynflow-devel
- gem-dynflow-doc