Topic Compaction

Topic Compaction Overview

At its core, topic compaction is about doing one thing well inside your Apache Kafka project. Once you understand the pattern, you can apply it consistently across features and teams.

Good topic compaction pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

import { Kafka } from 'kafkajs';

const kafka = new Kafka({ clientId: 'admin', brokers: ['localhost:9092'] });
const admin = kafka.admin();

await admin.connect();
await admin.createTopics({
  topics: [{ topic: 'orders', numPartitions: 6, replicationFactor: 3 }],
});
await admin.disconnect();

The admin client creates topics with a chosen partition count and replication factor.

Topic Compaction Example

import { Kafka } from 'kafkajs';

const kafka = new Kafka({ clientId: 'app', brokers: ['localhost:9092'] });
const producer = kafka.producer();
const consumer = kafka.consumer({ groupId: 'group' });

• Start from a minimal Topic Compaction example and grow it only as needed.
• Keep configuration explicit so Topic Compaction behaves the same in every environment.
• Name things clearly so teammates understand your Topic Compaction at a glance.
• Add tests around Topic Compaction early to lock in expected behaviour.

Apache Kafka Cheatsheet

Handy KafkaJS reference related to topic compaction.

How Topic Compaction Works in Apache Kafka

Topic Compaction builds on Kafka's log-based design, where producers append events to partitioned topics and consumer groups read them independently, tracking their own offsets.

The admin client creates topics with a chosen partition count and replication factor.

• Topics are split into partitions for parallelism and ordering per key.
• Producers choose a partition, usually by message key.
• Consumer groups share partitions so work scales horizontally.
• Offsets record how far each group has read.

Practical Guidance for Topic Compaction

In production, topic compaction needs attention to delivery guarantees, retries, and observability. Make handlers idempotent and monitor consumer lag closely.

Common Mistakes

• Copying topic compaction snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up topic compaction.
• Leaving topic compaction untested, so regressions slip into production.
• Over-engineering topic compaction before you actually need the extra flexibility.

Key Takeaways

• Topic Compaction is a core part of working effectively with Apache Kafka.
• Start small and keep topic compaction focused on a single responsibility.
• Apply consistent patterns so topic compaction scales across your project.
• Test and document topic compaction to keep it maintainable over time.