Difference between revisions of "The analytical side of CCIL"
(→Execution) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
== Execution == | == Execution == | ||
| − | + | Typically you should provide two scripts - one for server mode, which starts a ''server daemon'' and one for ''application mode'' which does some processing and exits. | |
== Configuration == | == Configuration == | ||
| − | + | Since they use different services - ones for ''server mode'' are designated to ''serve'' but ones in the ''application mode'' are designated to ''execute'', applications are configured in separated config files. | |
| + | |||
| + | Yes, there is some overlap - logic should remain in ''services'' and be called by ''stages'' during the pipeline execution. | ||
| + | |||
| + | * In future versions we will introduce config file inclusion. | ||
Latest revision as of 08:57, 9 June 2017
CCIL can execute in two modes, each able to spawn the other. On can say it has two aspects:
- Analytical
- Serving
This article focuses on the first one. If you want to read about the serving, please visit The server side of CCIL.
In short, the analytical side of the framework consist of it allowing to define small units of processing logic - stages and organize them in a complex pipelines.
The unit which does the work is the stage, but the unit which delivers the value is the pipeline.
Execution
Typically you should provide two scripts - one for server mode, which starts a server daemon and one for application mode which does some processing and exits.
Configuration
Since they use different services - ones for server mode are designated to serve but ones in the application mode are designated to execute, applications are configured in separated config files.
Yes, there is some overlap - logic should remain in services and be called by stages during the pipeline execution.
- In future versions we will introduce config file inclusion.
