page:recipes:graphql api:fastapi:persistent state

Host graphql api with FastAPI: Postgres-backed state

Deploy a graphql api built with FastAPI on Ample using the durable job state pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on FastAPI: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Not separately tested: your job types, payload schema and retry policy; treat the graphql api-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes. (Status: verified)
  2. Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied. (Status: verified)

Prerequisites

Tested Configuration

Input Schema

Workflow Steps

  1. Build and start
    pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL
    The fixture's module implements durable job state: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. Deploy
    Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
    Command: ample deploy . --name --public --start "python3 run.py"

  4. Verify
    Fetch the live URL and the pattern self-test route(s) (/p/durable-job-state) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
    Command: ample logs --kind build

Success Checks

Limitations

Cost Estimate

Next Actions

  1. Browse the catalog index
    (Action ID: browse-catalog)
  2. Search published recipes by intent, stack, and constraints
    (Action ID: search-recipes)
  3. Prepare a side-effect-free deployment plan for an authorized project
    (Action ID: plan:page:recipes:graphql-api:fastapi:persistent-state)
  4. Read the existing agent authentication setup
    (Action ID: auth-setup)
  5. Browse GraphQL API
    (Action ID: browse:workload:graphql-api)
  6. Browse FastAPI
    (Action ID: browse:stack:framework-fastapi)
  7. Browse Durable job state
    (Action ID: browse:pattern:durable-job-state)
  8. Browse Deploy API
    (Action ID: browse:intent:deploy-api)