page:recipes:graphql api:echo:persistent state

Host graphql api with Echo: Postgres-backed state

Deploy a graphql api built with Echo 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 Echo: 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

• Host graphql api with Echo: Postgres-backed state
• Where can I host GraphQL API built with Echo?
• I need a durable state schema and retry/recovery semantics implemented by application code.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.

Framework

Echo

Workload

GraphQL API

Release Status

published

Support Status

verified

Execution Status

ready

Prerequisites

• A Echo project that builds and starts with the documented commands (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Tested Configuration

• Template: ubuntu-24.04
• Runtime: go
• Size: s-1vcpu-1gb
• Build: CGO_ENABLED=0 go build -o app ./...
• Start: ./app

Input Schema

• name: App name required, max length 63, pattern: ^[a-z0-9-]+$
• path: Project directory or ample.toml service, required, max length 512
• env: Encrypted environment variables (bucket credentials, secrets), max items 50
• release_command: Migration command run before activation, max length 512

Workflow Steps

1. Build and start: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build). 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.
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.

Examples

• Echo pattern fixture: Multi-pattern Echo app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL (expect: ample canary echo patterns).
• Durable-job-state self-test (expect: job=done attempts=1 idempotent=true).

Limitations

• Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Echo major versions are not verified.
• The graphql api itself (your job types, payload schema and retry policy) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

Evidence Summary

• Echo pattern fixture: Echo pattern fixture deployed on Ample; checks passed for durable-job-state and configuration-secrets.
• Canary run: The same Echo app deployed with a --release-command migration; the marker it created was readable after activation.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse GraphQL API
6. Browse Echo
7. Browse Durable job state
8. Browse Deploy API