Event streaming

An append-only log of events kept for days or forever, that many consumers read at their own pace and can replay. It becomes the backbone that feeds caches, search, analytics and other services.

Where it shows up in real systems

  • Event log

    Events are kept for the retention period, so new consumers can replay history. Order is guaranteed only within a partition, and a consumer group can use at most one consumer per partition: partitions cap your parallelism.

    In production: Apache Kafka (Confluent, Amazon MSK), Amazon Kinesis, Redpanda, Azure Event Hubs, Apache Pulsar

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox