Consumer Lag

Consumer Lag Overview

Consumer Lag is a building block you will reach for often in Apache Kafka. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn consumer lag properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real Apache Kafka projects.

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.

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

Apache Kafka Cheatsheet

Handy KafkaJS reference related to consumer lag.

How Consumer Lag Works in Apache Kafka

Consumer Lag 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 Consumer Lag

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

Common Mistakes

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

Key Takeaways

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