Table of Contents
- A.2.1. Approach Basics
- A.2.2. High Availability / HA
- A.2.3. Scaling
- A.2.4. Task Handlers
- A.2.5. Implementation Notes
- A.2.6. Concurrency/Locking Notes
- A.2.7. Disallowing Concurrent Execution and Serialized Executions in the Cluster
- A.2.8. QoS / Transactionality
- A.2.9. Sub-tasks and Grouping
- A.2.10. Scheduling
- A.2.11. API
The purpose of the distributed task mechanism is to allow for scaling and fail-over capabilities.
The implementation utilizes the existing shared infrastructure of the cluster nodes in the form of the shared repository (e.g. database) rather than adding another shared mechanism to install and administer. This mechanism is suitable for medium frequency/coarse grained jobs. If a need arises for fine grained/very frequent task distribution, utilizing an existing mechanism such as the http front-end is a possibility.
