Host rest api with Hono: Postgres-backed state · Ample Computer

Host rest api with Hono: Postgres-backed state

Deploy a REST API built with Hono 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 Hono: 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). The REST API-specific behavior (your job types, payload schema and retry policy) is your application code on that verified basis.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. npm install and npm run start with @hono/node-server on the node-22 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 needs an answer first). Re-running with no change is a no-op.

    $ ample deploy . --name <app-name> --public
    
  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 <deployment_id> --kind build then --kind runtime.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL· http get/ → “ample canary hono patterns”
✓ durable-job-state self-test· http get/p/durable-job-state → “job=done attempts=1 idempotent=true”

Evidence

  1. November 6, 2026 · canary run
    Hono pattern fixture deployed on Ample (npm install and npm run start with @hono/node-server on the node-22 template); checks passed for durable-job-state and configuration-secrets. Pattern proof: 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).

  2. November 6, 2026 · canary run
    The same Hono app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover