page:recipes:asset library:next js:relational workflow

Host asset library with Next.js: relational workflow state

Deploy an asset library 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 asset library-specific behavior as your application code.

Representative Queries

• Host asset library with Next.js: relational workflow state
• Where can I host Asset library built with Next.js?
• I need a domain record schema, validation rules and concurrency behavior.

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.

Framework

• Next.js

Workload

• Asset library

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

Workflow 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...
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.
4. Verify
   • Fetch the live URL and the pattern self-test route(s)...

Examples

1. 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.
   • Source Ref: tests/deploy-canaries/next-js-patterns

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 asset library itself is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  1. App server
     • Size: s-1vcpu-1gb
     • Quantity: 1.0
     • Monthly Amount: 5.0
  2. Managed PostgreSQL database
     • Size: s-1vcpu-1gb
     • Quantity: 1.0
     • Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes...