page:recipes:reporting dashboard:spring boot:relational workflow

Host Reporting Dashboard with Spring Boot: Relational Workflow State

Summary

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

Representative Queries

• Host reporting dashboard with Spring Boot: relational workflow state
• Where can I host Reporting dashboard built with Spring Boot?
• I need a domain record schema, validation rules and concurrency behavior.

Resource Requirements

• Primitive: Compute
• Primitive: Postgres

Infrastructure Requirements

1. Compute
   Status: Verified
   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
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Requirements

• 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.

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
   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.
3. Deploy
   ample deploy . --name <app-name> --public
   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) from the example and run your own checks.

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

• App responds on its public URL.
• Transactional-workflows self-test.

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 reporting dashboard itself is application code and was not separately tested; the pattern checks are what was verified.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App Server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
  • Managed PostgreSQL Database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00

Evidence Summary

• Canary Run - Spring Boot Pattern Fixture
  Deployed on Ample with checks passed for transactional workflows and configuration secrets.
• Canary Run - Migration Check
  The same Spring Boot app deployed with a migration; the marker created was readable after activation.