Host order tracking with Next.js: relational catalog data · Ample Computer

Host order tracking with Next.js: relational catalog data

Deploy an order tracking 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. 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). The order tracking-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

supportverifiedreleasepublishedagent runready

VerifiedNovember 5, 2026

What it runs on

You need

Exact tested configuration

buildnpm run build --if-present
installnpm install
runtimenode
sizes-1vcpu-1gb
startnpm run start
templatenode-22

Steps

  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 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public
  1. 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

How it was checked

✓app responds on its public URL· http get/ → “ample canary next js patterns”
✓transactional-workflows self-test· http get/p/transactional-workflows → “tx=ok history=2 conflict=rejected”

Evidence

  1. November 5, 2026 · canary run
    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).

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

Tested examples

What it doesn’t cover