## The short version

Deploy a storefront built with Next.js on Ample using the transactional workflows 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`.

---

## WHAT WAS VERIFIED

Verified on Next.js: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

---

# INFRASTRUCTURE

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)  
- [Postgres](/content/discover/primitive/postgres/index.html): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.)

---

## PREREQUISITES

### Before you start

- A Next.js project that builds and starts with the documented commands (`next build` then `next start -H 0.0.0.0 -p $PORT` 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`

---

## STEP BY STEP

### How to do it

1. **Build and start**  
   `next build` then `next start -H 0.0.0.0 -p $PORT` 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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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.  
   
   ```
   ample deploy . --name <app-name> --public
   ```

4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (`/p/transactional-workflows`) 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
   ```

---

## EXAMPLES

### Tested examples

- **Next.js pattern fixture** (`tests/deploy-canaries/next-js-patterns`): Multi-pattern Next.js app whose transactional workflows module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

---

## SUCCESS CHECKS

### How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary next js patterns)
- transactional-workflows self-test (`/p/transactional-workflows` on the live URL, expect tx=ok history=2 conflict=rejected)

---

## COST

### Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD  
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

---

## EVIDENCE

### Verification evidence

- canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: Next.js pattern fixture deployed on Ample (`next build` then `next start -H 0.0.0.0 -p $PORT` on the node-22 template); checks passed for transactional-workflows and configuration-secrets. Pattern proof: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). (expires 2027-03-20T02:34:39Z)
- canary_run on 2026-09-20T01:54:51Z at revision `199ff1dfd52683832ae75d3f98b53a7a4bff7f96 (CLI e3181f5)`: The same Next.js app deployed with a `--release-command` migration; the marker it created was readable after activation. (expires 2027-03-19T01:54:51Z)

---

## EXECUTION

### Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: `servers:write`, `databases:read`.

---

## NEXT ACTIONS

### Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse Storefront (`GET /v1/catalog/nodes/workload%3Astorefront` on the api origin; authentication not required, approval not required)
- Browse Next.js (`GET /v1/catalog/nodes/stack%3Aframework-next-js` on the api origin; authentication not required, approval not required)
- Browse Transactional workflows (`GET /v1/catalog/nodes/pattern%3Atransactional-workflows` on the api origin; authentication not required, approval not required)
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required)

---

## ABOUT THIS RECIPE

### Identifiers and status

Recipe `page:recipes:storefront:next-js:relational-catalog`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/recipes/storefront/next-js/relational-catalog/index.html) | [Markdown](/content/recipes/storefront/next-js/relational-catalog.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Astorefront%3Anext-js%3Arelational-catalog)