...
- High Priority Duplication Queue: receives tasks generated by content/space changes in a DuraCloud account which are detected upon processing of AuditTasks.
- Low Priority Duplication Queue: receives tasks generated by the Looping Duplication Task Producer.
- Bit Integrity Queue: receives bit integrity check tasks generated by the Looping Bit Task Producer
- Bit Error Queue: receives bit integrity check errors generated by BitIntegrityCheckTaskProcessors.
- Bit Report Queue: receives bit report tasks generated by the Looping Bit Task Producer
- Audit Queue: receives tasks generated by the AuditStorageProvider decorator.
- Dead Letter Queue: the landing zone for any tasks which cannot be processed, despite multiple attempts. These tasks are reviewed by DuraCloud staff directly.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Queue Monitors
Each queue in the system is monitored for size. All of these monitors are configured in AWS CloudWatch. Both the High Priority Queue and the Low Priority Queue have monitors for high and low queue volume, which are used in combination with Auto Scaling to ensure that the correct number of worker instances are in place to handle the current load. The Dead Letter Queue monitor simply sends notifications when the queue is not empty.
...
Now, a key point to consider: Workman can process any number of different kinds of tasks. When a task is passed to a task worker, the worker delegates the creation of a task processor to a task processor factory. The task processor factory is responsible for recognizing tasks and providing an appropriate processor for that task. So as the system develops, new types of tasks can be handled simply by adding a new task processor and registering the related factory with the RootTaskProcessorFactor (see diagram below).
Gliffy Diagram