Architecture Diagram

Jump to bottom

Adina Shanholtz edited this page May 2, 2023 · 8 revisions

Architecture Diagram for Cromwell on Azure

Quick and Dirty

Step 1

Workflow calls Cromwell on Azure (hosted on AKS) directly using REST API OR
Workflow is uploaded to Azure Storage container, kicking off the Trigger Service (hosted on AKS) which calls Cromwell on Azure (hosted on AKS)

Step 2

CoA's backend is TES (hosted on AKS)
TES sends tasks to Azure Batch to break up and run the workflow

Step 2.5

CoA and TES use PostgreSQL on Azure as its database to store TesTasks as JSON
TriggerService and TES both sends logs/is monitored by Application Insights

Step 3

Azure Batch has one pool / one node per task (allowing each task to run sandboxed in parallel)
Azure Batch nodes will pull images from ACR (or external container registries) as defined in your WDL/CDL
Azure Batch has its own Azure Storage for its lifetime

Step 4

Your completed (or failed) workflow results will be deposited in the appropriate Azure Storage container