submitqueue/

SubmitQueue Services

Runnable wiring for the SubmitQueue domain's two services — the Gateway (entry point for land requests) and the Orchestrator (coordinates the pipeline) — wired with MySQL-backed extensions and runnable via Docker Compose.

Starting

Docker Compose (recommended)

make local-submitqueue-start   # builds binaries and starts all services
make local-submitqueue-ps      # verify services are running
make local-submitqueue-logs    # view logs

Standalone

Each service requires two MySQL databases (app and queue) and is configured via environment variables:

export MYSQL_DSN='root:root@tcp(127.0.0.1:3306)/submitqueue?parseTime=true'
export QUEUE_MYSQL_DSN='root:root@tcp(127.0.0.1:3307)/submitqueue?parseTime=true'

# Start gateway (default :8081)
go run ./service/submitqueue/gateway/server

# Start orchestrator (default :8082)
go run ./service/submitqueue/orchestrator/server

Stopping

Both services handle SIGINT (Ctrl+C) and SIGTERM gracefully:

1. The gRPC server stops accepting new connections and drains in-flight RPCs.
2. The orchestrator additionally stops its queue consumers (30s timeout).
3. The process exits with a code reflecting the outcome (see below).

To stop Docker Compose services:

make local-stop

Exit Codes

When shutdown itself encounters errors (e.g. the gRPC server returns an error during graceful stop, or queue consumers time out), those override the signal exit code and the process exits with code 1. The actual errors are printed to stderr.