page:recipes:storefront:next js:relational catalog

Host storefront with Next.js: relational catalog data

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. 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 storefront-specific behavior as your application code.

Representative Queries

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

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

1. 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.
2. 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.

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

Workflow Steps

1. Build and start
   • Command: 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
   • Body: 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
   • Command: ample deploy . --name <appName> --public
4. Verify
   • Command: ample logs --kind build

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.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  1. App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
  2. Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Examples

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

Success Checks

1. App responds on its public URL:
   • Kind: http_get
   • Path: /
   • Expect: ample canary next js patterns
2. Transactional-workflows self-test:
   • Kind: http_get
   • Path: /p/transactional-workflows
   • Expect: tx=ok history=2 conflict=rejected

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Storefront
• Browse Next.js
• Browse Transactional workflows
• Browse Deploy web app