~/talk

Building highly scalable IoT streaming solutions using Azure Event Hubs and MongoDB

links:none on file
slides:none on file

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

  1. 0:00Intro
  2. 3:09Azure lot Hub vs Azure Event Hubs
  3. 4:46What is MongoDB?
  4. 5:17Modelling a Basic "Thing"
  5. 6:16Strict Schema vs. Flexible Data Model
  6. 7:22Extensible at Runtime
  7. 11:03MongoDB & MongoDB Atlas
  8. 12:05Demo: Passing data through Azure Event Hubs
  9. 18:52Getting data to MongoDB
  10. 24:23What is Kafka Connect?
  11. 25:30MongoDB Kafka Connector
  12. 27:03Configuring Kafka Connect
  13. 35:00MongoDB within Azure IoT Ref Architecture
  14. 40:14MongoDB Atlas Online Archive
  15. 44:56Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.