Host graphql api with ASP.NET Core: streamed responses

Deploy a graphql api built with ASP.NET Core on Ample using the streaming response service 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: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true). Not separately tested: your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured; treat the graphql api-specific behavior as your application code.

Representative Queries

• Host graphql api with ASP.NET Core: streamed responses
• Where can I host GraphQL API built with ASP.NET Core?
• I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

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

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 streaming response service: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true). 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.
   ample deploy . --name <app-name> --public
4. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/streaming-response-service) from the example; then run your own checks. On failure read ample logs <app-name> --kind build then --kind runtime.
   ample logs <app-name> --kind build

Success Checks

• app responds on its public URL
  Check: GET /
  Expect: ample canary asp net core patterns
• streaming-response-service self-test
  Check: GET /p/streaming-response-service
  Expect: an SSE stream: data: id=, then chunk events one interval apart (read incrementally: first chunk within seconds, chunks spread over the interval), then data: done; /status?id= reports sent=N disconnected=true|false done=true|false

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 graphql api itself (your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured) 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

• 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

• Canary Run:
  • Summary: ASP.NET Core pattern fixture deployed on Ample.
  • Observed At: 2026-09-21T01:15:54Z
• Canary Run:
  • Summary: The same ASP.NET Core app deployed with a --release-command migration.
  • Observed At: 2026-09-20T23:34:47Z

Next Actions

• Browse the catalog index
  • Method: GET
  • Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Parameters:
    • Body: {"limit":5,"query":"Host graphql api with ASP.NET Core: streamed responses"}
• Prepare a side-effect-free deployment plan for an authorized project
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Parameters:
    • Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:graphql-api:asp-net-core:response-streaming","recipeRevision":"r1"}
• Read the existing agent authentication setup
  • Method: GET
  • Relative Path: /mcp/setup
• Browse GraphQL API
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Agraphql-api
• Browse ASP.NET Core
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-asp-net-core
• Browse Streaming response service
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Astreaming-response-service
• Browse Deploy API
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-api