page:recipes:csv import tool:spring boot:relational workflow

Host csv import tool with Spring Boot: relational workflow state

Summary

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

Representative Queries

• Host csv import tool with Spring Boot: relational workflow state
• Where can I host CSV import tool built with Spring Boot?
• I need a domain record schema, validation rules and concurrency behavior.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

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.

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.

Framework

Spring Boot

Workload

CSV import tool

Release Status

Published

Support Status

Verified

Execution Status

Ready

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
   ./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
   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) (/p/transactional-workflows) from the example; then run your own checks. On failure read ample logs --kind buildthen--kind runtime.
   Command: ample logs --kind build

Example

• Title: Spring Boot pattern fixture
  • Description: Multi-pattern Spring Boot app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  • Source Reference: tests/deploy-canaries/spring-boot-patterns

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 csv import tool itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
• 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. Buckets are allocation-priced per quota and not included.

Evidence Summary

1. Kind: canary_run
   • Summary: Spring Boot pattern fixture deployed on Ample (./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); checks passed for transactional-workflows and configuration-secrets.
   • Observed At: 2026-09-21T02:34:39Z
   • Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
   • Expires At: 2027-03-20T02:34:39Z
   • Scope:
     • Checks: /p/transactional-workflows
     • Pattern: pattern:transactional-workflows
     • Template: jvm-21
2. Kind: canary_run
   • Summary: 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
   • Implementation Revision: af6f45adea26-dirty (CLI af6f45a)
   • Expires At: 2027-03-19T22:49:19Z
   • Scope:
     • Pattern: pattern:transactional-workflows

Last Verified At

2026-09-21T02:34:39Z

Unknowns

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

Formats

• HTML: Link
• Markdown: Link
• JSON: Link

Next Actions

• Action ID: browse-catalog
  • Label: Browse the catalog index
  • Operation ID: catalog_index
  • Method: GET
  • Relative Path: /v1/catalog
  • Origin: api
  • Parameters: {}
• Action ID: search-recipes
  • Label: Search published recipes by intent, stack and constraints
  • Operation ID: search_recipes
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Origin: api
  • Parameters: {"body":{"limit":5,"query":"Host csv import tool with Spring Boot: relational workflow state"}}
• Action ID: plan:page:recipes:csv-import-tool:spring-boot:relational-workflow
  • Label: Prepare a side-effect-free deployment plan for an authorized project
  • Operation ID: plan_deployment
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Origin: api
  • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:csv-import-tool:spring-boot:relational-workflow","recipeRevision":"r1"}}
• Action ID: auth-setup
  • Label: Read the existing agent authentication setup
  • Operation ID: existing_auth_setup
  • Method: GET
  • Relative Path: /mcp/setup
  • Origin: api
  • Parameters: {}
• Action ID: browse:workload:csv-import-tool
  • Label: Browse CSV import tool
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Acsv-import-tool
  • Origin: api
  • Parameters: {"nodeId":"workload:csv-import-tool"}
• Action ID: browse:stack:framework-spring-boot
  • Label: Browse Spring Boot
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-spring-boot
  • Origin: api
  • Parameters: {"nodeId":"stack:framework-spring-boot"}
• Action ID: browse:pattern:transactional-workflows
  • Label: Browse Transactional workflows
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows
  • Origin: api
  • Parameters: {"nodeId":"pattern:transactional-workflows"}
• Action ID: browse:intent:deploy-web-app
  • Label: Browse Deploy web app
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
  • Origin: api
  • Parameters: {"nodeId":"intent:deploy-web-app"}