# Host order tracking with ASP.NET Core: relational catalog data

## Summary
Deploy a order tracking built with ASP.NET Core 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 ASP.NET Core: 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 ASP.NET Core: relational catalog data
- Where can I host Order tracking built with ASP.NET Core?
- I need catalog tables, transactional update logic and application-level access boundaries.

## Resource Requirements
- primitive:compute
- primitive: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.

## Prerequisites
- A ASP.NET Core project that builds and starts with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to 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**: dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to 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 build` then `--kind runtime`.
   - Command: ample logs  --kind build

## Examples
- **Title**: ASP.NET Core pattern fixture  
  **Description**: Multi-pattern ASP.NET Core app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Reference**: tests/deploy-canaries/asp-net-core-patterns

## Success Checks
- **Description**: app responds on its public URL  
  **Kind**: http_get  
  **Path**: /  
  **Expect**: ample canary asp net core patterns
- **Description**: transactional-workflows self-test  
  **Kind**: http_get  
  **Path**: /p/transactional-workflows  
  **Expect**: tx=ok history=2 conflict=rejected

## Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.
- The order tracking 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  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
  - **Name**: app server  
    - **Size**: s-1vcpu-1gb  
    - **Quantity**: 1.0  
    - **Monthly Amount**: 5.0  
  - **Name**: 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
- **Kind**: canary_run  
  **Summary**: ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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).  
  **Observed At**: 2026-09-21T01:15:54Z  
  **Implementation Revision**: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)  
  **Expires At**: 2027-03-20T01:15:54Z  
  **Scope**: {"checks":["/p/transactional-workflows"],"pattern":"pattern:transactional-workflows","template":"dotnet-10"}

## Last Verified At
2026-09-21T01:15:54Z