added-diagram

Author: mia303

src/assets/images/workflows/dynamic-workflows.png

@@ -37,6 +37,8 @@ This setup has two parts:
 - **Worker Loader**: Worker which receives the request and creates (or loads) the Dynamic Worker.
 - **Workflow class**: Your registered Workflow class which receives the persisted params, reloads the same Dynamic Worker code, and calls its `run()` method with the `WorkflowStep` object.
 
+![Dynamic Workers and Workflows architecture diagram](/src/assets/images/workflows/dynamic-workflows.png)
+
 Once the Worker Loader has [loaded the Dynamic Worker](/dynamic-workers/getting-started/#run-a-dynamic-worker), the Dynamic Worker calls `env.WORKFLOW.create()` to trigger an instance of the Workflow. The Worker Loader then stores the `workerId` of the Dynamic Worker in case the isolate spins down during the Workflow's exeuction.
 
 If the instance is long-running -- for example, if it includes a step.waitForEvent() -- then the Workflow engine may hibernate, and the Dynamic Worker isolate will shut down until the event occurs. When the Workflow resumes, the Worker Loader reloads its code using the workerId of the `Dynamic Worker`.