page:recipes:marketplace:next js:relational catalog

Host marketplace with Next.js: relational catalog data

Summary

Deploy a marketplace 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 marketplace-specific behavior as your application code.

Representative Queries

• Host marketplace with Next.js: relational catalog data
• Where can I host Marketplace 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
  Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
• PostgreSQL
  Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

Framework

Next.js

Workload

Marketplace

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

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

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: expected response is ample canary next js patterns
• Transactional-workflows self-test: expected response is tx=ok history=2 conflict=rejected

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 marketplace itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

1. Canary Run
   Next.js pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
2. Canary Run
   The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.

Platforms and Resources

Formats

• HTML: https://ample.computer/recipes/marketplace/next-js/relational-catalog
• Markdown: https://ample.computer/recipes/marketplace/next-js/relational-catalog.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amarketplace%3Anext-js%3Arelational-catalog

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 Marketplace.
• Browse Next.js.
• Browse Transactional workflows.
• Browse Deploy web app.