Host mobile backend with Starlette: worker execution and job state · Ample Computer
Host mobile backend with Starlette: worker execution and job state
Deploy a mobile backend built with Starlette as a public web service plus a dedicated worker process on Ample. ample plan --write discovers both services and their shared database and writes ample.toml; ample up reconciles the topology: a managed PostgreSQL 16 database, a public web microVM and a private worker microVM (kind worker, no public URL), both reading DATABASE_URL. Verified on Starlette: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1). The mobile backend-specific behavior (your job payloads, retry policy and scheduling) is your application code on that verified basis.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
A repository with the web app and the worker as separate service directories (the fixture uses apps/web and apps/worker), each building and starting with the documented commands (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template; the worker starts with python3 worker.py and binds no port)
Both services read DATABASE_URL at runtime and share one jobs table; the worker claims rows with SELECT ... FOR UPDATE SKIP LOCKED and marks them done once
An Ample account token with servers:write and databases:write (ample up creates the database)
Exact tested configuration
installpython3 -m pip install --target .ample/python -r requirements.txt
runtimepython
sizes-1vcpu-1gb
startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
templatepython-3.12
Steps
- Plan the topology. Run the planner once. It discovers the web and worker services, infers kind = "worker" for the process without a port, declares the database each service needs, and writes ample.toml. Exit 2 means it left questions in the manifest; answer them with --answer or by editing the file.
$ ample plan --write .
```
2. **Share one database.** Keep a single \[databases.main\] with engine = "postgres", drop any per-service database the planner added, and set DATABASE_URL = { database = "main" } under both \[services.web.env\] and \[services.worker.env\]. Python services also need an explicit start command in the manifest (the fixture sets start for both services).
```bash
$ ample plan --offline .
```
3. **Apply.** Reconcile the whole manifest in dependency order: the database first, then both services. It is idempotent and never destructive; exit 0 means everything applied, 2 needs input, 1 a failed resource (independent siblings still proceed and re-running resumes).
```bash
$ ample up .
```
4. **Verify.** Fetch the web service URL and its worker status route (/p/worker-queue/status in the example) and confirm the worker processed the enqueued job; on failure read the worker service's runtime logs.
```bash
$ ample logs <deployment_id> --kind runtime
```
## How it was checked
✓ web service responds on its public URL· http get/ → “ample canary starlette patterns”
✓ worker consumed the enqueued job· http get/p/worker-queue/status → “worker=done attempts=1 result=processed-by-worker”
## Evidence
1. November 5, 2026 · canary run
Starlette web service plus a separate Python worker process deployed on Ample with `ample plan --write` then `ample up` (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template); the web service enqueued a job that the private worker service consumed from the shared managed PostgreSQL database. Pattern proof: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1).
## Tested examples
- **Starlette web + worker fixture.** A Starlette web app (apps/web) and a worker process (apps/worker) sharing one managed PostgreSQL database; the queue module is under tests/deploy-canaries/_pattern-modules.
## What it doesn’t cover
- Verified on the python-3.12 template at s-1vcpu-1gb for both services with the example fixture.
- The worker-queue check verified the platform side; the mobile backend itself (your job payloads, retry policy and scheduling) is your application code.
- The worker is a long-running process supervised in its own microVM and wakes with the web service that feeds it; for scheduled work add an `ample job` (`[jobs.<name>]` in ample.toml).
- The worker service is private: it has no public URL and takes its jobs from the shared database; both services are placed with their database.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.