How to evaluate and design self-hosted n8n infrastructure for high-volume webhook/event flows, such as a burst of Instagram comments, so the service does not become unresponsive.

n8n 2.x · verified Jul 10, 2026

Fix: For self-hosted n8n under high production execution volume, do not rely on a single regular-mode n8n container as the scalable architecture. Use queue mode with Postgres, Redis, shared N8N_ENCRYPTION_KEY across all processes, one main process, one or more worker processes with explicit concurrency, and optionally dedicated webhook processors behind a load balancer for high parallel webhook ingress. Add execution-data pruning/save policies, DB pool sizing, metrics/queue metrics, and an external durable ingress queue when provider retry behavior is insufficient or spikes can exceed webhook processor capacity. A single regular-mode deployment may be acceptable for small teams, but it is not the right target for million-event bursts.

n8nscalingqueue-modewebhooksinfra

References