Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EDU-3663: Backporting 101 content | update definition of worker in encyclopedia for approachability #3239

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

EDU-3663: Backporting 101 content | update definition of worker in encyclopedia for approachability #3239

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4f12632
update definition of worker in encyclopedia
jsundai Dec 12, 2024
d059e1b
Update workers.mdx
jsundai Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion docs/encyclopedia/workers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,20 @@ tags:
- Concepts
---

There is a tight coupling between Temporal Task Queues and Worker Processes.
There is a close relationship between Temporal Task Queues and Worker Processes.

## What is a Worker? {#worker}

Workers, which are part of your application and provided by the Temporal SDK, carry out the tasks defined in your Workflow. The Worker itself is provided by the Temporal SDK, but your application will include code to configure and run it. Specifically, a Worker is an entity that polls a specific Task Queue on the Temporal Service, executes Workflow code in response, and returns the results of the execution back to the Temporal Server.

Since Workers execute your code, any Workflows you execute will make no progress unless one Worker is running.

There are typically three things you need in order to configure a Worker:

1. A **Temporal Client**, which is used to communicate with the Temporal Cluster
2. The **name of a Task Queue**, which is maintained by the Temporal Server and polled by the Worker
3. The **Workflow Definition class**, used to register the Workflow implementation with the Worker

In day-to-day conversations, the term Worker is used to denote either a [Worker Program](#worker-program), a [Worker Process](#worker-process), or a [Worker Entity](#worker-entity).
Temporal documentation aims to be explicit and differentiate between them.

Expand Down
Loading