71 docs tagged with "explanation"

This page compares a function execution in a traditional system and a Workflow Execution in Temporal.

A Child Workflow Execution is a Workflow Execution that is spawned from within another Workflow.

A Cloud Namespace Id is a globally unique identifier for a Namespace in Temporal Cloud.

A Cloud Namespace Name is a customer-supplied name for a Namespace in Temporal Cloud.

A Command is a requested action issued by a Worker to the Temporal Cluster after a Workflow Task Execution completes.

A Data Converter is a Temporal SDK component that encodes and decodes data entering and exiting a Temporal Server.

A Global Namespace is a Namespace that exists across Clusters when Multi-Cluster Replication is set up.

A Heartbeat Timeout is the maximum time between Activity Heartbeats.

A List Filter is the SQL-like string that is provided as the parameter to an Advanced Visibility List API.

A Local Activity is an Activity Execution that executes in the same process as the Workflow Execution that spawns it.

A Memo is a non-indexed user-supplied set of Workflow Execution metadata that is displayed with Filtered List results.

A Namespace is a unit of isolation within the Temporal Platform

If a Workflow Execution is a Child Workflow Execution, a Parent Close Policy determines what happens to the Workflow Execution if its Parent Workflow Execution changes to a Closed status (Completed, Failed, Timed out).

A Query is a synchronous operation that is used to report the state of a Workflow Execution.

A Retention Period is the amount of time a Workflow Execution Event History remains in the Cluster's persistence store.

A Retry Policy is a collection of attributes that instructs the Temporal Server how to retry a failure of a Workflow Execution or an Activity Task Execution.

A Run Id is a globally unique, platform-level identifier for a Workflow Execution.

A Schedule enables the scheduling of Workflow Executions.

A Schedule-To-Close Timeout is the maximum amount of time allowed for the overall Activity Execution, from when the first Activity Task is scheduled to when the last Activity Task, in the chain of Activity Tasks that make up the Activity Execution, reaches a Closed status.

A Schedule-To-Start Timeout is the maximum amount of time that is allowed from when an Activity Task is placed in a Task Queue to when a Worker picks it up from the Task Queue.

A Search Attribute is an indexed name used in List Filters to filter a list of Workflow Executions that have the Search Attribute in their metadata.

A Side Effect is a way to execute a short, nondeterministic code snippet, such as generating a UUID, that executes the provided function once and records its result into the Workflow Execution Event History.

A Signal is an asynchronous request to a Workflow Execution.

A Start-To-Close Timeout is the maximum time allowed for a single Activity Task Execution.

A Sticky Execution is a when a Worker Entity caches the Workflow Execution Event History and creates a dedicated Task Queue to listen on.

A Task Queue is a first-in, first-out queue that a Worker Process polls for Tasks.

A Task Token is a unique Id that correlates to an Activity Execution.

A Task is the context needed to make progress with a specific Workflow Execution or Activity Execution.

A Temporal Application is a set of Workflow Executions.

TODO

A Temporal Cloud Account Id is a unique identifier for a customer.

A Temporal Cluster is the Temporal Server paired with persistence.

A Temporal Cron Job is the series of Workflow Executions that occur when a Cron Schedule is provided in the call to spawn a Workflow Execution.

A Temporal SDK is a language-specific library that offers APIs to construct and use a Temporal Client to communicate with a Temporal Cluster, develop Workflow Definitions, and develop Worker Programs.

A Worker Entity is the individual Worker within a Worker Process that listens to a specific Task Queue.

A Worker Process is responsible for polling a Task Queue, dequeueing a Task, executing your code in response to a Task, and responding to the Temporal Server with the results.

A Worker Program is the static code that defines the constraints of the Worker Process, developed using the APIs of a Temporal SDK.

In day-to-day conversations, the term Worker is used to denote both a Worker Program and a Worker Process. Temporal documentation aims to be explicit and differentiate between them.

A Workflow Definition is the code that defines the constraints of a Workflow Execution.

A Workflow Execution Timeout is the maximum time that a Workflow Execution can be executing (have an Open status) including retries and any usage of Continue As New.

A Temporal Workflow Execution is a durable, scalable, reliable, and reactive function execution. It is the main unit of execution of a Temporal Application.

A Workflow Id Reuse Policy determines whether a Workflow Execution is allowed to spawn with a particular Workflow Id, if that Workflow Id has been used with a previous, and now Closed, Workflow Execution.

A Workflow Id is a customizable, application-level identifier for a Workflow Execution that is unique to an Open Workflow Execution within a Namespace.

This is the maximum amount of time that a single Workflow Run is restricted to.

A Workflow Task Execution is when a Worker picks up a Workflow Task and uses it to make progress on the execution of a Workflow function.

A Workflow Task Timeout is the maximum amount of time that the Temporal Server will wait for a Worker to start processing a Workflow Task after the Task has been pulled from the Task Queue.

A Workflow Task is a Task that contains the context needed to make progress with a Workflow Execution.

A Workflow Type is a name that maps to a Workflow Definition.

In day-to-day conversations, the term "Workflow" frequently denotes either a Workflow Type, a Workflow Definition, or a Workflow Execution.

Advanced Visibility, within the Temporal Platform, is the subsystem and APIs that enable the listing, filtering, and sorting of Workflow Executions through an SQL-like query syntax.

An Activity Definition is the code that defines the constraints of an Activity Task Execution.

An Activity Execution is the full chain of Activity Task Executions.

An Activity Heartbeat is a ping from the Worker that is executing the Activity to the Temporal Cluster. Each ping informs the Temporal Cluster that the Activity Execution is making progress and the Worker has not crashed.

A unique identifier for an Activity Execution.

An Activity Task Execution is the execution of an Activity Type.

An Activity Task contains the context needed to make an Activity Task Execution.

An Activity Type is the mapping of a name to an Activity Definition.

In day-to-day conversations, the term "Activity" frequently denotes either an Activity Type, an Activity Definition, or an Activity Execution.

An append log of Events that represents the full state a Workflow Execution.

Events are created by the Temporal Cluster in response to external occurrences and Commands generated by a Workflow Execution.

Archival is a feature that automatically backs up Event Histories from Temporal Cluster persistence to a custom blob store after the Closed Workflow Execution retention period is reached.

Asynchronous Activity Completion occurs when an external system provides the final result of a computation, started by an Activity, to the Temporal System.

Continue-As-New is the mechanism by which all relevant state is passed to a new Workflow Execution with a fresh Event History.

Multi-Cluster Replication is a feature which asynchronously replicates Workflow Executions from active Clusters to other passive Clusters, for backup and state reconstruction.

Standard Visibility, within the Temporal Platform, is the subsystem and APIs that list Workflow Executions by a predefined set of filters.

Task Routing is when a Task Queue is paired with one or more Worker Processes, primarily for Activity Task Executions.

Temporal Cloud is a managed, hosted Temporal environment that provides a platform for Temporal Applications.

Temporal is a scalable and reliable runtime for Reentrant Processes called Temporal Workflow Executions.

The Temporal Platform consists of a Temporal Cluster and Worker Processes.

The Temporal Server is a grouping of four horizontally scalable services.

Worker Versioning allows you to more easily deploy changes to Workflow Definitions.