|
|
|
|
|
|
by tomhallett
456 days ago
|
|
|
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).“ |
|
|
Yes. The library makes sure that your app retries failed workflows. Or if you use the commercial products, takes care of that for you.