# Host rest api with Hono: Postgres-backed state

## Summary
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). Not separately tested: your job types, payload schema and retry policy; treat the rest api-specific behavior as your application code.

## Representative Queries
- Host rest api with Hono: Postgres-backed state
- Where can I host REST API built with Hono?
- I need a durable state schema and retry/recovery semantics implemented by application code.

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
### Compute
- **Label**: Compute  
- **Status**: verified  
- **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
- **Label**: Postgres  
- **Status**: verified  
- **Summary**: 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
Hono

## Workload
REST API

## Release Status
published

## Support Status
verified

## Execution Status
ready

## Prerequisites
- A Hono project that builds and starts with the documented commands (npm install and npm run start with @hono/node-server on the node-22 template)
- 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**: node-22  
- **Runtime**: node  
- **Size**: s-1vcpu-1gb  
- **Install**: npm install  
- **Build**: npm run build --if-present  
- **Start**: npm run start

## Workflow 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 blocked). Re-running with no change is a no-op.  
   - **Command**: ample deploy . --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  --kind build` then `--kind runtime`.  
   - **Command**: ample logs  --kind build

## Examples
- **Hono pattern fixture**  
  Multi-pattern Hono app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  - **Source Ref**: tests/deploy-canaries/hono-patterns

## Success Checks
- **App responds on its public URL**  
  - **Kind**: http_get  
  - **Path**: /  
  - **Expect**: ample canary hono patterns
- **Durable-job-state self-test**  
  - **Kind**: http_get  
  - **Path**: /p/durable-job-state  
  - **Expect**: job=done attempts=1 idempotent=true

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Hono major versions are not verified.
- The rest 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  
- **Authoritative**: true  
- **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, monthlyAmount=5.0
- **Managed PostgreSQL database**: size=s-1vcpu-1gb, quantity=1.0, monthlyAmount=5.0

**Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Hono pattern fixture** deployed on Ample; checks passed for durable-job-state and configuration-secrets.

## Next Actions
- **Browse the catalog index**  
 - **Action ID**: browse-catalog  
 - **Method**: GET  
 - **Relative Path**: /v1/catalog

- **Search published recipes by intent, stack and constraints**  
 - **Action ID**: search-recipes  
 - **Method**: POST  
 - **Relative Path**: /v1/catalog/search

- **Prepare a side-effect-free deployment plan for an authorized project**  
 - **Action ID**: plan:page:recipes:rest-api:hono:persistent-state  
 - **Method**: POST  
 - **Relative Path**: /v1/catalog/plan

- **Read the existing agent authentication setup**  
 - **Action ID**: auth-setup  
 - **Method**: GET  
 - **Relative Path**: /mcp/setup

- **Browse REST API**  
 - **Action ID**: browse:workload:rest-api  
 - **Method**: GET  
 - **Relative Path**: /v1/catalog/nodes/workload%3Arest-api

- **Browse Hono**  
 - **Action ID**: browse:stack:framework-hono  
 - **Method**: GET  
 - **Relative Path**: /v1/catalog/nodes/stack%3Aframework-hono

- **Browse Durable job state**  
 - **Action ID**: browse:pattern:durable-job-state  
 - **Method**: GET  
 - **Relative Path**: /v1/catalog/nodes/pattern%3Adurable-job-state

- **Browse Deploy API**  
 - **Action ID**: browse:intent:deploy-api  
 - **Method**: GET  
 - **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-api