### Host product catalog with ASP.NET Core: relational catalog data

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

#### Representative Queries
- Host product catalog with ASP.NET Core: relational catalog data
- Where can I host Product catalog built with ASP.NET Core?
- I need catalog tables, transactional update logic and application-level access boundaries.

#### Resource Requirements
- **Compute**
- **Postgres**

#### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are 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.

#### 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

#### Tested Configuration
- **Template**: dotnet-10
- **Runtime**: dotnet
- **Size**: s-1vcpu-1gb
- **Build**: dotnet publish -c Release -o out
- **Start**: ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

#### Workflow Steps
1. **Build and start**
   - Command: dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to 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
- **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 Ref: tests/deploy-canaries/asp-net-core-patterns

#### Success Checks
- App responds on its public URL
   - **Kind**: http_get
   - **Path**: /  
   - **Expect**: ample canary asp net core patterns
- 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 product catalog 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
- **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.

##### 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

#### Formats
- [HTML Format](/content/recipes/product-catalog/asp-net-core/relational-catalog/index.html)
- [Markdown Format](/content/recipes/product-catalog/asp-net-core/relational-catalog.md)
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproduct-catalog%3Aasp-net-core%3Arelational-catalog)