Min hardware spec

GatewayConsole
RAM4 GB3 GB
CPU cores22
Disk spaceN/A5 GB

Gateway requirements

Conduktor Gateway is provided as a Docker image and a Helm chart.

Minimum setup

For light usage per Gateway node:
  • 2 CPU cores
  • 4 GB of RAM
Each Gateway instance should support around 20–30 MB/s of sustained throughput with minimal latency impact.
For medium to high usage per Gateway node:
  • 4 CPU cores
  • 8 GB of RAM
This setup supports ~40–50 MB/s throughput. For production, run at least 3 Gateway instances. Scale horizontally as needed.

Local storage requirements

While Gateway doesn’t use local storage directly, some interceptors like large message handling might.

Scaling Gateway

Gateway is designed to scale horizontally or vertically. It’s mostly CPU-bound unless caching is enabled. Monitor metrics to scale effectively.

Interceptor impact

Interceptors add CPU load. Interceptors doing heavy inspection (e.g. encryption) require:
  • More CPU
  • More memory (recommend 4 GB RAM per CPU)

Kafka requirements

  • Kafka version 2.5.0 or higher (but lower than 4.0.0)
  • Gateway must connect as an admin user with rights to:
    • Manage topics, groups, and cluster info
    • Commit offsets

Console requirements

Conduktor Console is provided as a single Docker container.

Production requirements

For production deployments, ensure: If deploying via Helm, check the install guide for detailed requirements.

Hardware requirements

Use container CGroup limits for resource control.

Minimum

  • 2 CPU cores
  • 3 GB RAM
  • 5 GB disk
  • 4+ CPU cores
  • 4+ GB RAM
  • 10+ GB disk
Configure env variables or get started with Docker.

Memory configuration

Note: RUN_MODE is deprecated. JVM now respects container limits (up to 80%).
-XX:+UseContainerSupport -XX:MaxRAMPercentage=80