Github/temporal
1
0
Fork 0
mirror of https://github.com/temporalio/temporal.git synced 2026-08-30 18:41:49 -07:00
Code Issues Packages Projects Releases Wiki Activity

Document some high-level CHASM terminology (#8657)

Browse Source
This commit is contained in:
Dan Davison
2025-11-20 17:20:40 -05:00
committed by GitHub
parent aa3fa5a54f
commit cfd96c40fe
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/architecture/chasm.md Normal file
View File

@@ -0,0 +1,15 @@
# Terminology
- The Temporal server implements abstractions such as `Workflow`, `Activity`, and `Scheduler`.
- Each of these abstractions is an `Archetype`.
- An instance of an `Archetype` is an `Execution` (e.g. a workflow execution, an activity execution).
- An execution possesses a `BusinessID` that should typically be meaningful in the user’s own systems. It is guaranteed to be unique among executions within a namespace that are in a non-terminal state.
- A single `Execution` may consist of multiple non-overlapping runs (e.g. successive non-overlapping invocations of an `Activity` or `Workflow` that share the same `businessID`, successive non-overlapping invocations of a `Workflow` by a `Scheduler`).
- An `Execution` has a tree structure in which each subtree is a `Component`. A component, and thus an execution, may be a tree comprising one node only.
- A `ComponentRef` contains an `ExecutionKey`, a `ComponentPath`, and additional information identifying (uniquely across all clusters when there is a multi-cluster configuration with failovers) a specific transition in execution history. Together these identify a component within an execution.