Work Item Type
Feature Request
Description
Similar to: https://community.fabric.microsoft.com/t5/Eventstream/Bind-IoT-Hub-Data-Sources-to-separate-streams/... but a different approach
Propose a topic model for IoT Hub sources. IoT Hub writes to topics per Data Source. EventStream acts as the consumer and subscribes to one or more topics.
User Story
Raj manages an industrial robotics line. He needs telemetry data for performance analytics, twin changes for configuration tracking, and lifecycle events for predictive maintenance. Today, all event types arrive in one stream, forcing him to filter, re-route, and risk dropping messages. With topic-based subscriptions, Raj could point analytics jobs directly at the telemetry topic, dashboards at twin-change, and alerting at lifecycle, reducing cost and ensuring clean separation of workloads.
Note
EventHubs and EventStreams are efficient, full-featured, and scalable. However, in many IoT scenarios, a lightweight Pub/Sub architecture with MQTT brokers and clients is desirable for simpler routing, lower cost, and better alignment with device-oriented patterns. It would be valuable to allow configuration of user topics in addition to the built-in “events,” so telemetry can be routed automatically without extra processing.
