GlobalKTable

Introduction

What is GlobalKTable? GlobalKTable replicates all partitions to each instance for lookup joins against reference data.

Understanding the topic

What happens — GlobalKTable:

• Build StreamsBuilder topology.
• Read from input topics.
• Transform: filter, map, join, aggregate.
• Write results to output topics.

Visual explanation

Pipeline view:

Input topic
  ↓
filter/map/join/window
  ↓
state store + changelog
  ↓
output topic

Step-by-step explanation

1. Define topology — builder.stream(), table(), join().
2. Process — Stateful/stateless ops.
3. Write output — to() sink topic.
4. Start — KafkaStreams.start().

Informative example

Example:

kafka-topics --bootstrap-server localhost:9092 --create --topic globalktable --partitions 6 --replication-factor 3
kafka-console-producer --bootstrap-server localhost:9092 --topic globalktable
kafka-console-consumer --bootstrap-server localhost:9092 --topic globalktable --from-beginning
kafka-consumer-groups --bootstrap-server localhost:9092 --describe --group globalktable-service

Execution workflow

Best practices

• Choose keys before joins and aggregations.
• Name internal topics and state stores clearly.
• Test topology with realistic ordering and late events.
• Monitor processing latency, commit rate, and restore time.

Common mistakes

• Unexpected repartition topics from wrong key choices.
• Ignoring late-arriving events in windows.
• Underestimating state-store disk and restore time.

Summary

GlobalKTable — Design topology around keys, state stores, window boundaries, changelog topics, and exactly-once needs.