Skip to content

    Apache Kafka

    Reading time: 2 min.Editorially reviewed on:
    ← All terms

    Definition

    Apache Kafka continuously processes event data and provides it to multiple applications.

    Apache Kafka is a distributed platform for event streams. It can publish events, store them durably, and process them during or after ingestion.

    Simply explained

    Like a distributed conveyor belt with labeled packages. Unlike a real belt, Kafka can retain events and replay them.

    Why it matters in practice

    For a Kafka architecture, event format, retention, and responsible consumers should be defined before implementation.

    Example from business

    Possible example: multiple internal applications process the same shared order status via separate Kafka consumers.

    Limits and pitfalls

    • Kafka does not automatically produce semantically correct events. Data quality and access rules remain tasks of the connected systems.

    Origin & history

    The Apache documentation describes Kafka as a distributed platform for reading, writing, storing, and processing event streams.

    Use in mid-sized companies

    • Possible use cases include decoupling internal applications and processing continuous operational events.

    Frequently asked questions

    Is Kafka just a queue?

    No, the platform also stores and processes event streams.

    Does Kafka replace semantic data validation?

    No, the meaning and quality of events must be secured separately.

    Sources

    Editorially reviewed on:

    On this page

    Next step

    Put knowledge into practice