Dev
Generador de configuración de topic de Kafka
Used by developers, writers, and creators worldwide.
A Kafka topic config generator gives you a complete kafka-topics create command tuned for what the topic is actually for, so you provision it with the right partitions, replication, and retention instead of guessing. Name the topic and pick a use case — high-throughput events, a compacted changelog, low-latency small messages, or long-retention audit data — and it returns the full command with a sensible partition count, a replication factor of three for durability, and the config flags that matter, like compression, cleanup policy, and retention. Streaming engineers use it to create a topic correctly the first time and recall whether a changelog needs compaction. It runs in your browser and generates instantly. Paste it into a shell with your broker address, adjust the partition count to your throughput, and run it. Getting these settings right up front avoids a painful repartition or data-loss surprise later.
Read the complete guide — 5 min read
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Name the topic.
- Pick the use case that fits the data.
- Click Generate to produce the create command.
- Paste it into a shell, set your broker, and run it.
Use Cases
- •Creating a Kafka topic with the right partitions and replication
- •Choosing a compacted policy for a changelog topic
- •Setting retention to match an event or audit use case
- •Recalling the kafka-topics create command flags
- •Standardising topic configuration across a team
Tips
- →Size partitions for peak throughput — you cannot reduce them later.
- →Use compaction for changelog topics, deletion for event streams.
- →Keep replication at three in production for durability.
- →Match retention to how long consumers might need to replay.
FAQ
why replication factor three
Three replicas let the cluster tolerate a broker failure and still keep a quorum, which is the standard for production durability. Use one only for local development, where losing data on a restart does not matter.
when do I want a compacted topic
Use cleanup.policy=compact for changelog or state topics where you only care about the latest value per key. Compaction keeps the most recent record for each key and discards older ones, which is ideal for materialising state.
can I change partitions later
You can increase partitions but never decrease them, and increasing them changes key-to-partition mapping, which can break ordering guarantees. That is why it is worth sizing the partition count for your throughput up front.
You might also like
Popular tools from other categories that share themes with this one.