Host storefront with Spring Boot: relational catalog data

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

Representative Queries

• Host storefront with Spring Boot: relational catalog data
• Where can I host Storefront built with Spring Boot?
• 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 Spring Boot project that builds and starts with the documented commands (./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.
• 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.

Tested Configuration

• Template: jvm-21
• Runtime: java
• Size: s-1vcpu-2gb
• Build: ./mvnw -q -DskipTests package
• Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

Workflow Steps

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

Examples

• Spring Boot pattern fixture: Multi-pattern Spring Boot 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 spring boot patterns
2. transactional-workflows self-test
   • Kind: http_get
   • Path: /p/transactional-workflows
   • 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 storefront specific behavior (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
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

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

Evidence Summary

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

Unknowns

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML: https://ample.computer/recipes/storefront/spring-boot/relational-catalog
• Markdown: https://ample.computer/recipes/storefront/spring-boot/relational-catalog.md
• JSON: https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Astorefront%3Aspring-boot%3Arelational-catalog

Next Actions

1. Browse the catalog index
   • Operation: GET /v1/catalog
   • Requires Authentication: false
2. Search published recipes by intent, stack and constraints
   • Operation: POST /v1/catalog/search
   • Requires Authentication: false
3. Prepare a side-effect-free deployment plan for an authorized project
   • Operation: POST /v1/catalog/plan
   • Requires Authentication: true

Note: You can continue to explore related options or modify your deployment plan as needed.