# Host mobile backend with Echo: streamed responses

Deploy a mobile backend built with Echo 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 Echo: 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.

## Summary

- **Framework**: Echo
- **Workload**: Mobile backend
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

## Representative Queries

- Host mobile backend with Echo: streamed responses
- Where can I host Mobile backend built with Echo?
- I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

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

## Workflow Steps

1. **Build and start**: `CGO_ENABLED=0 go build -o app ./... then ./app` on the ubuntu-24.04 template (go.sum committed for a reproducible build). 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.
3. **Deploy**: Run the synchronous deploy once and read the result.
4. **Verify**: Fetch the live URL and run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.

## Examples

- **Echo pattern fixture**: Multi-pattern Echo app whose streaming response service module was checked live.

## Success Checks

- App responds on its public URL.
- Streaming-response-service self-test: an SSE stream.

## Limitations

- Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture.
- The mobile backend itself is application code and was not separately tested.

## Cost Estimate

- **Monthly Amount**: 10.0 USD
- **Components**:
  - App server: s-1vcpu-1gb, 1.0, 5.0 USD
  - Managed PostgreSQL database: s-1vcpu-1gb, 1.0, 5.0 USD

## Next Actions

- Browse the catalog index
- Search published recipes by intent
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse Mobile backend
- Browse Echo
- Browse Streaming response service
- Browse Deploy API