Host order tracking with Spring Boot: relational catalog data

Deploy a order tracking built with Spring Boot 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 Spring Boot: 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 Spring Boot: relational catalog data
• Where can I host Order tracking built with Spring Boot?
• 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.

Workflow Steps

1. Build and start: ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.
2. Implement the pattern on PostgreSQL: 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.
   • Command: ample deploy . --name --public
4. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.
   • Command: ample logs --kind build

Success Checks

• App responds on its public URL: expect: ample canary spring boot patterns
• Transactional-workflows self-test: expect: tx=ok history=2 conflict=rejected

Limitations

• Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot major versions are not verified.
• The order tracking itself is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Monthly Amount: $10.00
  • App Server: s-1vcpu-1gb, Quantity: 1, Monthly Amount: $5.00
  • Managed PostgreSQL Database: s-1vcpu-1gb, Quantity: 1, Monthly Amount: $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Canary Run 1: Spring Boot pattern fixture deployed on Ample...
  • Observed At: 2026-09-21T02:34:39Z
• Canary Run 2: The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.
  • Observed At: 2026-09-20T22:49:19Z

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes: POST /v1/catalog/search
• Prepare a deployment plan: POST /v1/catalog/plan
• Read existing agent authentication setup: GET /mcp/setup
• Browse Order tracking: GET /v1/catalog/nodes/workload%3Aorder-tracking
• Browse Spring Boot: GET /v1/catalog/nodes/stack%3Aframework-spring-boot
• Browse Transactional workflows: GET /v1/catalog/nodes/pattern%3Atransactional-workflows
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app