Cloud Native Event Streaming with Kafka & Open Standards
summary
Cloud-native event streaming here means a multi-protocol ingestion service that supports Kafka AMQP HTTPS WebSockets, exposes a single gateway, uses a three‑tier Gateway/Backend/Storage model with Service Fabric and VM scale sets, and a two‑tier storage pattern (NVMe local + blob offload). Benchmarks use OpenMessaging; measured end‑to‑end latency is <10 ms average, P99 ≈30 ms. Tiers are standard/premium/dedicated, with per‑application throttling and metadata/DR replication options.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:57Agenda
- 2:18Why event streaming?
- 4:13What is event streaming?
- 9:07Cloud native event streaming
- 12:01Key components of an event stream ingestion
- 25:10High performant streaming
- 41:40Azure Event Hubs under the hood
- 47:13Outro
related talks
25mOperating Cloud-Native Kafka
35mArchitectures and Trends for Event Stream Processing on Azure with Open Source Software
30mEvent Streaming and the Future of Applications
47mTackling Cloud Complexity - Recipes From Real World Projects
33mNATS: The Cloud-Native Challenger to Kafka's Messaging Throne
28mConnectivity Patterns for Cloud Native Applications
40mThinking Cloud Native, CloudEvents Future
43mAzure Messaging – Streams, Queues, and Pub Sub