"Just as a wise leader knows that sometimes the best action is to do nothing, so too does this code demonstrate the power of non-action. Without any purpose or function, it exists in a state of effortless ease, free from the entanglements of attachment and expectation, uncoupled to any business logic."
Lao Tse,
... maybe
This lib offers an extensible API for Dynamic Chained Computations defined as a YAML string graph.
The User Defined DSL should be placed in the service layer along with a YAML decoder for the type needed. This way the features are decoupled from the definition improving maintainability and re-usability (features in the code / business logic in the YAML).
id: ...
name: ...
env: ...
version: ...
tasks:
<key_1>: # uuid
type: <component> # User defined task name
config: # configuration for the component
<attribute>: <value>
...
<key_n>:
type: <component>
from: <Other_key> # pointer to previous task
config:
<attribute>: <value>
...
When the US perimeter is changing faster than you can sprint.
This code follows the path of Lao Tse for the non-action. Allowing you to code only the features that are needed and letting you define/change the business logic in an Imperative way from a config file, avoiding unnecessary minors versions/hotfixes and speeding up CD.
(it's really just dependency injection with a lot of meme)
Males with active driving licenses
A YAML Plan as a graph of tasks which yields the function composititon below
result = writter( inner( filter( col_A ), trans( col_B ) ) )