Elsa 4 target architecture: one platform, multiple execution models Four layers. Shared authoring and operations in Elsa Studio. Three execution models, native workflows, BPMN processes and ETL pipelines, plus an extension slot. A shared durable runtime foundation. Hosting and distributed work, with execution coordination and work execution. ELSA 4 · ROADMAPOne platform.Multiple execution models.TARGET ARCHITECTUREProposed or possibleTarget capability 1 SHARED AUTHORING & OPERATIONSElsa Studio · design · inspect · operateWorkflow designerBPMN modelerPipeline designerCustom editor 2 EXECUTION MODELSNative workflowsSequenceFlowchartStateMachineAgent collaborationBpmnProcess activityEach composition owns its sequencing,routing and joining rules.BPMN processesDirect hostEmbedded via activityOne shared interpreterOwns tokens, events,gateways and scopes.ETL pipelinesPartition workersBatch & continuousOwns partitions,checkpoints, backpressureand data processing.Additionalexecution modelsExtension pointPlugs in as aseparate package. 3 SHARED DURABLE RUNTIME FOUNDATIONShared contracts and infrastructure. Each model keeps its own state and semantics.Execution identityand lifecycleDurable stateand deliveryTimers, correlationand recoveryWork dispatchand observability 4 HOSTING & DISTRIBUTED WORKDecides placement and coordination, never model semantics.Execution coordinationOne actor or virtual actor per execution, not per activity.Built-in hostOrleansProto.Actorpossible adaptersWork executionRuns dispatched work and reports completion.Local workersExternal tasksETL partition workersdispatchcompletion runs on

Target architecture

Select a layer or an execution model to highlight it and read what it owns. Selecting a model zooms in. Use the buttons or Ctrl/Cmd with the wheel to zoom, drag to pan, Esc to reset.

Speaker notes (about 45 seconds)

Elsa 4 is one platform with several execution models.

At the top, Elsa Studio is one place to design, inspect and operate, with an editor that fits each model.

Below are the execution models. Native workflows compose with Sequence, Flowchart or agent collaboration, and each composition owns its own routing and joins. BPMN keeps its own token and gateway semantics, and runs directly or embedded in a workflow on the same interpreter. ETL pipelines own partitions and checkpoints. The dashed slot leaves room for more.

They all share one durable foundation for identity, state, timers and recovery.

Hosting places and coordinates executions, one actor per execution, while workers do the work. Orleans and Proto.Actor are possible adapters. This is the target, not today's release.