# Host graphql api with ASP.NET Core: worker execution and job state

Deploy a GraphQL API built with ASP.NET Core as a public web service plus a dedicated worker process on Ample. `ample plan --write` discovers both services and their shared database and writes ample.toml; `ample up` reconciles the topology: a managed PostgreSQL 16 database, a public web microVM and a private worker microVM (kind worker, no public URL), both reading DATABASE_URL. Verified on ASP.NET Core: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1). The GraphQL API-specific behavior (your job payloads, retry policy and scheduling) is your application code on that verified basis.

Verified November 5, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- A repository with the web app and the worker as separate service directories (the fixture uses apps/web and apps/worker), each building and starting with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT; the worker starts with dotnet of its own console project (plain Npgsql) and binds no port)

- Both services read DATABASE_URL at runtime and share one jobs table; the worker claims rows with SELECT ... FOR UPDATE SKIP LOCKED and marks them done once

- An Ample account token with servers:write and databases:write (ample up creates the database)

## Exact tested configuration

```
build dotenv publish -c Release -o out
runtime dotnet
sizes-1vcpu-1gb
start ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll
template dotnet-10
```

## Steps

1. **Plan the topology.** Run the planner once. It discovers the web and worker services, infers kind = "worker" for the process without a port, declares the database each service needs, and writes ample.toml. Exit 2 means it left questions in the manifest; answer them with --answer or by editing the file.
   
   ```
   $ ample plan --write .
   ```

2. **Share one database.** Keep a single [databases.main] with engine = "postgres", drop any per-service database the planner added, and set DATABASE_URL = { database = "main" } under both [services.web.env] and [services.worker.env].  
   
   ```
   $ ample plan --offline .
   ```

3. **Apply.** Reconcile the whole manifest in dependency order: the database first, then both services. It is idempotent and never destructive; exit 0 means everything applied, 2 needs input, 1 a failed resource (independent siblings still proceed and re-running resumes).  
   
   ```
   $ ample up .
   ```

4. **Verify.** Fetch the web service URL and its worker status route (/p/worker-queue/status in the example) and confirm the worker processed the enqueued job; on failure read the worker service's runtime logs.  
   
   ```
   $ ample logs <deployment_id> --kind runtime
   ```

## How it was checked

✓ web service responds on its public URL· http get/ → “ample canary asp net core patterns”  
✓ worker consumed the enqueued job· http get/p/worker-queue/status → “worker=done attempts=1 result=processed-by-worker”

## Evidence

1. November 5, 2026 · canary run  
   ASP.NET Core web service plus a separate ASP.NET Core worker process deployed on Ample with `ample plan --write` then `ample up` (dotnet publish -c Release -o out in the builder, then dotnet <entry>.dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); the web service enqueued a job that the private worker service consumed from the shared managed PostgreSQL database. Pattern proof: a separately deployed worker service (kind worker, no public URL) sharing a declared managed PostgreSQL database with the web service, consuming a jobs table with row locks and marking jobs done once (worker=done attempts=1).

## Tested examples

- **ASP.NET Core web + worker fixture.** An ASP.NET Core web app (apps/web) and a worker process (apps/worker) sharing one managed PostgreSQL database; the queue module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover  
- Verified on the dotnet-10 template at s-1vcpu-1gb for both services with the example fixture.
- The worker-queue check verified the platform side; the GraphQL API itself (your job payloads, retry policy and scheduling) is your application code.
- The worker is a long-running process supervised in its own microVM and wakes with the web service that feeds it; for scheduled work add an `ample job` (`[jobs.<name>]` in ample.toml).
- The worker service is private: it has no public URL and takes its jobs from the shared database; both services are placed with their database.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
