page:recipes:mobile backend:express:response streaming

Host mobile backend with Express: streamed responses

Deploy a mobile backend built with Express 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 Express: 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 mobile backend-specific behavior as your application code.

Prerequisites

Resource Requirements

Tested Configuration

Workflow Steps

  1. Build and start: npm install, npm run build --if-present, npm run start 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: the observed behavior matches the aforementioned expectations. 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 routes and run your own checks. On failure read ample logs --kind build then --kind runtime.
    • Command: ample logs --kind build

Success Checks

Limitations

Cost Estimate

Evidence Summary

Next Actions