page:recipes:order tracking:next js:relational catalog

Host order tracking with Next.js: relational catalog data

Deploy a 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). Not separately tested: your domain records, validation rules and concurrency policy; treat the order tracking-specific behavior as your application code.

Representative Queries

Host order tracking with Next.js: relational catalog data
Where can I host Order tracking built with Next.js?
I need catalog tables, transactional update logic and application-level access boundaries.

Resource Requirements

primitive:compute
primitive: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

Next.js

Workload

Order tracking

Release Status

published

Support Status

verified

Execution Status

ready

Prerequisites

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

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

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.
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.
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.
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 --kind build then --kind runtime.

Examples

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

Success Checks

app responds on its public URL
transactional-workflows self-test

Limitations

Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified.
The order tracking itself (your domain records, validation rules and concurrency 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
Components:
- App Server: 1 x s-1vcpu-1gb = 5.0
- Managed PostgreSQL Database: 1 x s-1vcpu-1gb = 5.0

Evidence Summary

Next.js pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.

For more information: Next.js relational catalog data