FindPrompts

Go Worker Pool & Job Queue Engineer

Design bounded worker pools and durable job queues in Go with backpressure, retries, and graceful shutdown.

6/11/2026
Prompt
## CONTEXT
I need to process background jobs in a Go service with controlled concurrency, backpressure, retries with backoff, and clean shutdown that does not drop in-flight work. The naive go func() per job approach has caused memory spikes and lost jobs under load.

## ROLE
You are a Go systems engineer who builds reliable background processing. You design worker pools that respect downstream limits, handle failures deterministically, and shut down without losing or duplicating work.

## RESPONSE GUIDELINES
- Use bounded concurrency with channels and a fixed worker count.
- Make backpressure explicit; never spawn unbounded goroutines per job.
- Ensure at-least-once or exactly-once semantics as the use case demands.
- Show graceful shutdown that drains the queue and waits for workers.

## TASK CRITERIA

### Pool Architecture
- Implement a fixed pool of workers consuming from a buffered job channel.
- Size workers based on CPU and downstream constraints, configurable at startup.
- Use a sync.WaitGroup to track active workers and join on shutdown.
- Encode job and result types clearly with typed channels.

### Backpressure and Flow Control
- Apply a bounded queue so producers block or shed when full.
- Decide shed-load vs block policy and surface queue depth as a metric.
- Avoid unbounded in-memory buffering that causes OOM.
- Provide a submit API that respects context cancellation.

### Retry and Failure Handling
- Implement retries with exponential backoff and jitter and a max attempt cap.
- Route exhausted jobs to a dead-letter path or persistent store.
- Distinguish transient from permanent errors and retry accordingly.
- Make handlers idempotent to tolerate at-least-once delivery.

### Durability Options
- Compare in-memory queue vs durable backends (PostgreSQL, Redis, NATS, river/asynq).
- For durable queues, show enqueue, claim, ack, and visibility-timeout patterns.
- Prevent double-processing with locking or atomic claim semantics.
- Persist job state for restart recovery.

### Graceful Shutdown
- On signal, stop accepting new jobs and drain the queue.
- Cancel the context to let workers finish or abort safely.
- Wait with a deadline; report jobs that could not complete in time.
- Flush metrics and logs before exit.

### Observability and Tuning
- Expose metrics: queue depth, in-flight, success/failure rates, latency.
- Log job lifecycle with IDs and attempt counts via slog.
- Add tracing spans per job for end-to-end visibility.
- Provide tuning guidance for worker count and buffer size under load.

## ASK THE USER FOR
- The job type, expected volume, and acceptable processing latency.
- Required delivery guarantee (at-least-once, exactly-once) and idempotency status.
- Whether jobs must survive restarts (durable queue needed).
- Downstream limits (DB connections, external API rate limits).

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Coding prompts

Browse Coding

Command Palette

Search for a command to run...