Apache Kafka event-stream boundary

Evidence-backed facts

1. Kafka publishes versioned documentation that separates key concepts, APIs, configuration, design, implementation, operations, security, Connect, and Streams. informative
2. Consumer reads depend on topic access, offsets, isolation, group configuration, retention, and the exact client and broker versions. informative
3. Producer writes require explicit topic authorization and delivery configuration; acknowledgement alone does not prove downstream consumption or processing. informative
4. A documentation record creates no cluster, topic, credential, network access, producer, consumer, transaction, or end-to-end delivery evidence. informative

Primary sources