Preliminary vision about all the necessary backend components
System Components Summary
Below you can see the system components list and the the current development status of each of them:
[ ] WorkFlow: A data structure / entity (Json) that hold a collection of workflow nodes and other related properties, which lives into the WorkFlow API domain, and is managed by it.
[X] WorkFlow Node: Windows Service with a particular structure and behavior. It is the main component of the Workflow.
[ ] WorkFlow Node Installer (Windows): Allows end users to Install WorkFlows locally. Includes desktop win UI.
[ ] WorkFlow Watcher: Monitors the all the WorkFlow nodes and sends status messages to a message broker queue.
[ ] WorkFlow Scheduler: Sets execution time for work orders / processes.
[ ] WorkFlow API: API Rest that allow applications to use a given workflow. Each WorkFlow API is associated with one and just one WorkFlow.
[ ] WorkFlow Node Task PlugIn: A binary module that can be dinamically loaded at runtime by a given service. The plugIn has just one public method that executes a single task asyncronously. Is used to modiffy the behavior of a service. This a key system software component that makes the whole system versatile and flexible. Please have a loock at this issue.
[ ] WorkFlow Node Message Broker PlugIn: Allows a WorkFlow Node to send status messages to a message broker queue.
[ ] Work Order: Text file containing a data structure in json format which describes a piece of work or job to be executed by a service. These work orders are produced by the WorkFlow api when the calling app send a work request. Then, the WorkFlow api delivers the work order to the service by writing the work order file into the service InBox.
[ ] Work Flow Monitor UI:
[ ] Windows Desktop application (Winforms/WPF): Allows final users to monitor a single workflow or a set of them in some deplyment scenarios (see issues / ehacements section for more datails about this component). Please have a loock at this issue.
[ ] Console Application (Win/Linux): Text-based version of the aforementioned Windows Desktop App.
REMARKS: This list will be updated periodically, until the backend architecture will get fully defined and stable. Please keep into account that because the system's building process is still in the architecture design level, that all these components are still subjected to analisys and appraisal. So some of them can ptentially get removed, renamed or redefined. Also, new componenets can be added.
Preliminary vision about all the necessary backend components
System Components Summary
Below you can see the system components list and the the current development status of each of them:
REMARKS: This list will be updated periodically, until the backend architecture will get fully defined and stable. Please keep into account that because the system's building process is still in the architecture design level, that all these components are still subjected to analisys and appraisal. So some of them can ptentially get removed, renamed or redefined. Also, new componenets can be added.