Restaurants: product catalog using Next.js · Ample Computer
Restaurants: product catalog using Next.js
A product catalog blueprint for restaurants built with Next.js on Ample. Domain schema: menu_items (sku, name, section, price, allergens, active): the menu as a SKU catalog; stock_movements (sku, delta, reason, moved_at): ingredient and prepared-item stock; orders (order_no, service_type, status, placed_at): dine-in, pickup and delivery orders; order_lines (order_no, sku, qty, modifiers): order contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: menu with allergens and prices, locations, hours and reservations contact, catering information. Kept out of scope until handling is reviewed: customer contact and payment details, staff schedules. Allergen information must be kept accurate by the operator; nothing here validates food-safety claims. Technical basis 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).
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from
ample bucket createpassed as encrypted S3_* environment variables - A review of which restaurants data classes may be handled at all; this blueprint models public information only
Exact tested configuration
buildnpm run build --if-present
installnpm install
runtimenode
sizes-1vcpu-1gb
startnpm run start
templatenode-22
Steps
Model the restaurants domain. Create the tables menu_items, stock_movements, orders, order_lines, events. The menu as a SKU catalog lives in menu_items; keep the sensitive classes (customer contact and payment details, staff schedules) out of this schema.
Workflow step 1. Model the SKU catalog with versioned updates
Workflow step 2. Record every catalog change as an event in the same transaction
Workflow step 3. Reject stale concurrent updates
Workflow step 4. Deploy and verify history and conflict handling
Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
- Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the restaurants workflow.
$ 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 from the example· http get/p/transactional-workflows → “see the pattern fixture checks”
Evidence
- 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); the transactional workflows checks passed: 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 blueprint's Restaurants schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified transactional workflows basis for this blueprint.
What it doesn’t cover
- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the restaurants schema and workflow are an original design for this blueprint, built on that basis.
- Allergen information must be kept accurate by the operator; nothing here validates food-safety claims.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.