Building highly scalable IoT streaming solutions using Azure Event Hubs and MongoDB
summary
Shows a concrete pipeline: MongoDB’s Kafka connector reads change streams from Atlas and writes to Azure Event Hubs, then a sync task consumes the hub back into an Atlas collection. Demo uses a Python producer for fictitious stock ticks, Docker-hosted Kafka Connect (Azure preview), topic creation, publishFullDocument=true, and REST POST connector configs to achieve a round trip. Highlights operational fits: Kafka Connect preview, Atlas online archive with federated warm+cold queries, and real customers with 25 terabytes from 6,000 turbines.
AI-written summary · about
chapters (15)
- 0:00Intro
- 3:09Azure lot Hub vs Azure Event Hubs
- 4:46What is MongoDB?
- 5:17Modelling a Basic "Thing"
- 6:16Strict Schema vs. Flexible Data Model
- 7:22Extensible at Runtime
- 11:03MongoDB & MongoDB Atlas
- 12:05Demo: Passing data through Azure Event Hubs
- 18:52Getting data to MongoDB
- 24:23What is Kafka Connect?
- 25:30MongoDB Kafka Connector
- 27:03Configuring Kafka Connect
- 35:00MongoDB within Azure IoT Ref Architecture
- 40:14MongoDB Atlas Online Archive
- 44:56Summary
related talks
26mConnecting distributed data with Apache Kafka
14mSolving Data Engineering Challenges
26mConnecting distributed data to Azure CosmosDB with Apache Kafka
15mAzure IoT from the edge to ADX
03h 00mStream Processing, Going Beyond Pub/Sub with Kafka Streams and...
34mBuilding and Scaling Robust Zero-code IoT Streaming Data Pipelines
53mApache Kafka and KSQL in Action : Lets Build a Streaming Data Pipeline!
40mA Data Mesh Of Streams
