Azure Event Hubs
High-throughput real-time data streaming platform and event ingestion service with native Apache Kafka multi-protocol support.
High-throughput real-time data streaming platform and event ingestion service with native Apache Kafka multi-protocol support.
Coming from Google Cloud?
Both are high-throughput real-time streaming platforms, but Event Hubs uses partitioned append-only commit logs (Kafka style) while Pub/Sub uses dynamic serverless topics with per-message ACKs.
- Ingest millions of real-time events per second with sub-second latency.
- Zero-code automated landing into cloud storage (Event Hubs Capture vs Pub/Sub GCS Subscriptions).
- Partition / Ordering keys to guarantee in-order message delivery per entity.
- Architecture: Event Hubs uses fixed partitioned logs; Pub/Sub is a dynamic serverless queue where messages are deleted when ACKed.
- Kafka Compatibility: Event Hubs has native port 9093 Kafka protocol support; GCP requires Managed Service for Apache Kafka.
- Replay: Event Hubs retains streaming logs up to 90 days for multi-consumer replay; Pub/Sub retains unacknowledged messages up to 7 days.
What is Azure Event Hubs?
Azure Event Hubs is a cloud-native real-time data streaming platform capable of ingesting millions of events per second with sub-100 millisecond latency. It uses a partitioned consumer log architecture and provides a 100% native Apache Kafka 1.0+ multi-protocol endpoint, allowing Kafka applications to stream data into Azure without managing ZooKeeper or Kafka brokers.
Decision Guide: When to Choose This Service
Use Azure Event Hubs for real-time telemetry ingestion, IoT sensor streaming, application log collection, financial event feeds, and zero-code automated landing into ADLS Gen2.
Do NOT use Event Hubs for enterprise service bus messaging requiring per-message transactions, dead-letter queues, and complex pub/sub topic filters (use Azure Service Bus instead).
Core Architectural Pillars
Append-only commit logs providing horizontal concurrency and strict FIFO ordering per entity.
1 TU = 1 MB/s Ingress / 2 MB/s Egress with dynamic auto-scaling.
100% native Apache Kafka endpoint on port 9093 with SASL_SSL.
Zero-code automated delivery into ADLS Gen2 in Avro/Parquet format.