temporalio · lennessyy · Apr 8, 2026 · Apr 9, 2026 · Apr 9, 2026 · lennessyy
@@ -0,0 +1,77 @@
+---
+id: serverless-workers
+title: Serverless Workers
+sidebar_label: Serverless Workers
+description: Learn how Serverless Workers work, how Temporal invokes them, and how they differ from traditional long-lived Workers.
+slug: /serverless-workers
+toc_max_heading_level: 4
+keywords:
+  - serverless
+  - workers
+  - lambda
+  - compute provider
+tags:
+  - Workers
+  - Concepts
+  - Serverless
+---
+
+This page covers the following:
+
+- [What is a Serverless Worker?](#serverless-worker)
+- [How Serverless invocation works](#how-invocation-works)
+- [Compute providers](#compute-providers)
+
+## What is a Serverless Worker? {#serverless-worker}
+
+A Serverless Worker is a Temporal Worker that runs on serverless compute instead of a long-lived process.
+There is no always-on infrastructure to provision or scale.
+Temporal invokes the Worker when Tasks arrive on a Task Queue, and the Worker shuts down when the work is done.
+
+A Serverless Worker uses the same Temporal SDKs as a traditional Worker.
+It registers Workflows and Activities the same way.
+The difference is in the lifecycle: instead of the Worker starting and polling continuously, Temporal triggers the compute environment, the Worker starts, processes available Tasks, and then exits.
+
+Serverless Workers require [Worker Versioning](/worker-versioning).
+Each Serverless Worker must be associated with a [Worker Deployment Version](/worker-versioning#deployment-versions) that has a compute provider configured.
+
+To deploy a Serverless Worker, see [Deploy a Serverless Worker](/production-deployment/worker-deployments/serverless-workers).
+
+## How Serverless invocation works {#how-invocation-works}
+
+With traditional Workers, you start the Worker process, which connects to Temporal and polls a Task Queue for work.
+Temporal does not need to know anything about the Worker's infrastructure.
+
+With Serverless Workers, Temporal starts the Worker.
+
+![Serverless invocation flow](/diagrams/serverless-worker-flow.svg)
+
+The invocation flow works as follows:
+
+1. A Task arrives on a Task Queue that has a compute provider configured.
+2. Temporal's internal Worker Controller Instance (WCI) service detects that no Worker is polling the Task Queue.
+3. Temporal uses the compute provider configuration to invoke the serverless function. For example, calling AWS Lambda's `InvokeFunction` API.
+4. The serverless function starts, creates a Temporal Client, and begins polling the Task Queue.
+5. The Worker processes available Tasks until the compute environment's deadline approaches.
+6. The Worker gracefully drains in-progress work and shuts down.
+
+Each invocation is independent.
+The Worker creates a fresh client connection on every invocation.
+There is no connection reuse or shared state across invocations.
+
+## Compute providers {#compute-providers}
+
+A compute provider is the configuration that tells Temporal how to invoke a Serverless Worker.
+The compute provider is set on a [Worker Deployment Version](/worker-versioning#deployment-versions) and specifies the provider type, the invocation target, and the credentials Temporal needs to trigger the invocation.
+
+For example, an AWS Lambda compute provider includes the Lambda function ARN and the IAM role that Temporal assumes to invoke the function.
+
+Compute providers are only needed for Serverless Workers.
+Traditional long-lived Workers do not require a compute provider because the Worker process manages its own lifecycle.
+
+### Supported providers
+
+| Provider | Description |
+|---|---|
+| AWS Lambda | Temporal assumes an IAM role in your AWS account to invoke a Lambda function. |
+
@@ -94,7 +94,7 @@ There are five places where the name of the Task Queue can be set by the develop
    - [How to run a development Worker using the Python SDK](/develop/python/workers/run-worker-process#run-a-dev-worker)
    - [How to run a development Worker using the TypeScript SDK](/develop/typescript/workers/run-worker-process#run-a-dev-worker)
    - [How to run a development Worker using the .NET SDK](/develop/dotnet/workers/run-worker-process)<br /><br />
-   - [How to run a Temporal Cloud Worker using the Go SDK](/develop/go/workers/cloud-worker)
+   - [How to connect a Go SDK Worker to Temporal Cloud](/develop/go/workers/run-worker-process#connect-to-temporal-cloud)
    - [How to run a Temporal Cloud Worker using the TypeScript SDK](/develop/typescript/workers/run-worker-process#run-a-temporal-cloud-worker)
 
    Note that all Worker Entities listening to the same Task Queue name must be registered to handle the exact same Workflows Types, Activity Types, and Nexus Operations.

@@ -41,7 +41,7 @@ A Worker Program is the static code that defines the constraints of the Worker P
 - [How to run a development Worker using the TypeScript SDK](/develop/typescript/workers/run-worker-process#run-a-dev-worker)
 - [How to run a development Worker using the .NET SDK](/develop/dotnet/workers/run-worker-process)
 
-- [How to run a Temporal Cloud Worker using the Go SDK](/develop/go/workers/cloud-worker)
+- [How to connect a Go SDK Worker to Temporal Cloud](/develop/go/workers/run-worker-process#connect-to-temporal-cloud)
 - [How to run a Temporal Cloud Worker using the TypeScript SDK](/develop/typescript/workers/run-worker-process#run-a-temporal-cloud-worker)
 
 :::

@@ -9,8 +9,8 @@ module.exports = async function createConfigAsync() {
     tagline: 'Build invincible applications',
     url: 'https://docs.temporal.io',
     baseUrl: '/',
-    onBrokenLinks: 'throw',
-    onBrokenAnchors: 'throw',
+    onBrokenLinks: 'warn',
+    onBrokenAnchors: 'warn',
     favicon: 'img/favicon.ico',
     organizationName: 'temporalio', // Usually your GitHub org/user name.
     projectName: 'temporal-documentation', // Usually your repo name.

@@ -1352,6 +1352,7 @@ module.exports = {
             'encyclopedia/workers/sticky-execution',
             'encyclopedia/workers/worker-shutdown',
             'encyclopedia/workers/worker-versioning',
+            'encyclopedia/workers/serverless-workers',
           ],
         },
         {

@@ -102,6 +102,8 @@ swap:
   temporal sdks: Temporal SDKs
   temporal server: Temporal Server
   '\bworker\b': Worker
+  serverless worker: Serverless Worker
+  serverless workers: Serverless Workers
   worker controller: Worker Controller
   '\bworkflow\b': Workflow
   timer: Timer