Litestar Queues
Litestar Queues lets a Litestar application persist work, run it in a worker, and inspect the result. Use it for work that should outlive the request that started it: sending email, importing files, refreshing reports, or calling a slow service.
Quickstart
Install the package:
pip install litestar-queues
Create app.py:
from litestar import Litestar, post
from litestar.di import NamedDependency
from litestar_queues import QueueConfig, QueuePlugin, QueueService, task
@task("accounts.sync", queue="accounts", timeout=30)
async def sync_account(account_id: str) -> dict[str, str]:
return {"account_id": account_id, "status": "synced"}
@post("/accounts/{account_id:str}/sync")
async def create_sync_job(account_id: str, queue_service: NamedDependency[QueueService]) -> dict[str, str]:
result = await queue_service.enqueue(sync_account, account_id)
return {"task_id": str(result.id), "status": result.status or "pending"}
app = Litestar(route_handlers=[create_sync_job], plugins=[QueuePlugin(config=QueueConfig())])
Run the application:
LITESTAR_APP=app:app litestar run --reload
Enqueue a task:
curl -X POST http://127.0.0.1:8000/accounts/acct-123/sync
The response contains a task ID and an initial status. QueueConfig() starts
one fresh queue-worker child for this litestar run invocation and shares a
private temporary SQLite file with it. No queue socket or port is exposed, and
the temporary queue is removed on normal shutdown; it is not durable across
server restarts.
Production boundary
Choose where tasks are stored separately from where they run. For durable deployments use a shared backend such as SQLSpec, Advanced Alchemy, Redis, or Valkey. Use standalone workers when the web app and task workers must scale separately. The process-local memory backend remains useful for inline tests or an explicitly single-ASGI-process worker. Cloud Run runs tasks; it does not store them.
Next steps
- Start here
- Understand the model
- Follow a how-to guide
- Choose backends
- Run an example
- Browse the API reference
Litestar Queues supports Python 3.10 through 3.14 and is licensed under MIT.
Release files for litestar-queues 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| litestar_queues-0.11.0.tar.gz | 1.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| litestar_queues-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / litestar_queues-0.11.0.tar.gz
| Download URL | litestar_queues-0.11.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2b88e1df95ee8526806b181f840883c4d7f6af6185d05b5f2e21cc24b299cf2
|
|
BLAKE2b-256 checksum How to use checksums |
de2ef59415bfeb5b4ec87f2329acc85e3ca73b3751395b7d87d0bfe2ce7772e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / litestar_queues-0.11.0-py3-none-any.whl
| Download URL | litestar_queues-0.11.0-py3-none-any.whl |
|---|---|
| Size | 402.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f45417c7200862d7b282ecc6506d919d77619c628a4ee0d74635f36e45e117a
|
|
BLAKE2b-256 checksum How to use checksums |
0a1191a3a3cad3ab61b89805b7acf95e3e760ddaeffc219fc0dd84e16af28bf9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency log