**Looking to run high-volume distributed tasks?**

[Render Workflows](/content/docs/workflows/index.html) provides an all-in-one worker model with managed queuing, automatic retries, and rapid spin-up.

**Background workers** are services that run continuously (like a [web service](/content/docs/web-services/index.html) or a [private service](/content/docs/private-services/index.html)), but they don't receive any incoming network traffic. Instead, these services usually poll a task queue (such as one backed by a [Render Key Value](/content/docs/key-value/index.html) instance) and process new tasks as they come in:

Background workers help to keep your apps responsive by offloading long-running, asynchronous tasks from your services in the critical request path.

Common worker tasks include:

- Processing media files
- Generating reports
- Interacting with third-party APIs, such as Stripe, Twilio, or AI models

## Popular worker frameworks

You can use the frameworks below to simplify polling a task queue backed by a Redis®-like store (such as [Render Key Value](/content/docs/key-value/index.html)).

| Language | Framework |
| --- | --- |
| **Python** | Celery ( [see quickstart](/content/docs/deploy-celery/index.html)) |
| **Ruby** | Sidekiq ( [see quickstart](/content/docs/deploy-rails-sidekiq/index.html)) |
| **Node.js** | [BullMQ](https://bullmq.io/) |
| **Go** | [Asynq](https://github.com/hibiken/asynq) |
| **Elixir** | [Oban](https://hexdocs.pm/oban/Oban.html)<br>**Note:** This framework integrates with Render Postgres instead of Key Value. |
| **Rust** | [apalis](https://github.com/geofmureithi/apalis) |

###### [Background Workers](/content/docs/background-workers/index.html)

- [Popular worker frameworks](/content/docs/background-workers#popular-worker-frameworks/index.html)

# Ready to help.