Message Processing

Message Processing sits at the heart of kafka consumers in Apache Kafka. This guide walks through the concept step by step, with examples, a cheatsheet, and common mistakes to avoid.

Message Processing Overview

Message Processing lets you structure Apache Kafka work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep message processing focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { Kafka } from 'kafkajs';

const kafka = new Kafka({ clientId: 'orders', brokers: ['localhost:9092'] });
const consumer = kafka.consumer({ groupId: 'order-processors' });

await consumer.connect();
await consumer.subscribe({ topic: 'orders', fromBeginning: false });

await consumer.run({
  eachMessage: async ({ topic, partition, message }) => {
    const order = JSON.parse(message.value.toString());
    console.log({ partition, key: message.key?.toString(), order });
  },
});

A consumer joins a group and processes messages from the partitions it is assigned.

Message Processing 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 Message Processing example and grow it only as needed.
Keep configuration explicit so Message Processing behaves the same in every environment.
Name things clearly so teammates understand your Message Processing at a glance.
Add tests around Message Processing early to lock in expected behaviour.

Apache Kafka Cheatsheet

Handy KafkaJS reference related to message processing.

Task	Example	Purpose
Create client	`new Kafka({ clientId, brokers })`	Connect to the cluster
Produce	`producer.send({ topic, messages })`	Publish events
Consume	`consumer.run({ eachMessage })`	Process events
Subscribe	`consumer.subscribe({ topic })`	Choose topics to read
Group	`kafka.consumer({ groupId })`	Scale consumers
Admin	`admin.createTopics(...)`	Manage topics
Commit offset	auto-commit or `commitOffsets`	Track progress

How Message Processing Works in Apache Kafka

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

A consumer joins a group and processes messages from the partitions it is assigned.

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 Message Processing

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

Concern	Recommendation
Ordering	Key related events so they land on one partition
Reliability	Use acks=all and idempotent producers
Idempotency	Handle duplicate deliveries safely
Monitoring	Track consumer lag and error rates

Common Mistakes

Skipping error handling and edge cases when wiring up message processing.
Leaving message processing untested, so regressions slip into production.
Over-engineering message processing before you actually need the extra flexibility.
Ignoring documentation, which makes message processing hard for the next developer to change.

Key Takeaways

Message Processing is a core part of working effectively with Apache Kafka.
Start small and keep message processing focused on a single responsibility.
Apply consistent patterns so message processing scales across your project.
Test and document message processing to keep it maintainable over time.

Pro Tip

When you get stuck on message processing, reduce it to the smallest reproducible example first — most Apache Kafka issues become obvious once the noise is gone.