Worker

The worker will process payloads as indicated below,

sequenceDiagram
    autonumber

    participant bus
    participant cache
    participant worker
    participant middleware

    bus->>worker: payload
    activate worker
    worker->>cache: get input
    worker--)middleware: interface
    middleware--)worker: interface
    worker->>cache: store response
    deactivate worker

1. retrieve the payload from the bus on the queue/topic that the worker has subscribed to.
2. retrieve the arguments object from the cache at key arugmentId
3. perform work while storing progress in the cache at location id as an artifact response. Microservices will leverage the middleware as needed to perform work. The flow of process work can be modified via worker hooks
4. store the solution/response at location id in cache.

id is an optional string that represents the arguments object and the state of the system.

block-beta
    columns 5

    block:inputs
        columns 1
        system(("System"))
        payload(("Payload"))
    end
    space

    worker
    space
    answer(("response"))

    inputs --> worker
    worker --> answer

If the state of the system and the payload is the same, then the reponse should be the same and thus the message will not be sent over the bus. The force parameter when true will ensure that the message is sent on the bus regardless if there is a completed response in the cache or not.