Host GraphQL API with NestJS: Streamed Responses

Summary

Deploy a GraphQL API built with NestJS on Ample using the streaming response service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on NestJS: 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 NestJS: streamed responses
• Where can I host GraphQL API built with NestJS?
• I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

Resource Requirements

• primitive:compute
• primitive: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 NestJS project that builds and starts with the documented commands (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)
• 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: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template. 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.
3. Deploy: Run the synchronous deploy once and read the result.
4. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

Cost Estimate

• Monthly Amount: $10.00
  • App server: 1 x s-1vcpu-1gb = $5.00
  • Managed PostgreSQL database: 1 x s-1vcpu-1gb = $5.00

Limitations

• Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes and templates are not verified.
• The GraphQL API itself (your event schema, reconnection strategy) is application code and was not separately tested.

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan: POST /v1/catalog/plan
• Read the existing agent authentication setup: GET /mcp/setup
• Browse GraphQL API: GET /v1/catalog/nodes/workload%3Agraphql-api