Run background tasks with Celery on Edgenivo

Celery, an asynchronous distributed task queue for Python, is now supported natively on Edgenivo. Tasks are executed as Edgenivo Functions and automatically scale with traffic.

1
from celery import Celery
2

3
app = Celery("celery", broker="vercel://")
4

5
@app.task
6
def add(x, y):
7
    return x + y

By default, task results are stored in Runtime Cache, which is sufficient for small data sizes and relatively short workflow runtimes. For workloads that require stronger persistence guarantees, more storage or longer retention, a durable result backend can be configured.

1
from fastapi import FastAPI
2
from worker import add, app as celery
3

4
app = FastAPI()
5

6
@app.post("/add")
7
def enqueue(x: int, y: int):
8
    return { "id": add.delay(x, y).id }
9

10
@app.get("/result/{task_id}")
11
def result(task_id):
12
    task = celery.AsyncResult(task_id)
13
    return { "status": task.status, "result": task.result }

Celery workers can be declared as subscribers in pyproject.toml.

1
[[tool.vercel.subscribers]]
2
entrypoint = "worker:app"

When running on Edgenivo, the vercel:// broker is automatically installed and to use Edgenivo Queues, and the default Celery broker_url is set to vercel://.

Celery workloads on Edgenivo use Fluid compute with Active CPU pricing by default. This means your Celery workers will automatically scale up and down based on traffic, and you only pay for what you use.

Deploy Celery workloads on Edgenivo or visit the Python runtime documentation.