Loading content
Durable workflow engine for minutes-to-hours processes; deterministic replay and automatic retries. Best suited: Long-running, stateful orchestration that must survive crashes and resume exactly where it left off. Watch out: General-purpose workflow infrastructure, not agent-native — you bring the LLM / agent layer yourself.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Temporal is a platform for reliable execution of long-running and distributed workflows.
Temporal emerged in 2019 from Uber’s workflow team after its Cadence system was continued as an open-source project. Maxim Fateev and Samar Abbas founded Temporal to develop this workflow technology independently.
A workflow describes durable execution, while activities encapsulate individual steps. Temporal stores state and events; workers execute activities and can resume after failures.
It describes a deterministic, durable process.
It performs a potentially failure-prone external action.
Workers poll for tasks and execute them.
Temporal suits business processes and integrations that must remain reliable across long durations, retries, and system failures.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.