IoT
Event-driven IoT telemetry pipeline
Modernizing data ingestion from connected devices with messaging, asynchronous processing and geolocation — while leading the team technically.
- Architecture
- Event-driven systems
- Technical leadership
Context
Connected devices streamed telemetry continuously, and several business systems depended on that data. The existing ingestion pipeline had to keep up with a growing device fleet and the reliability requirements of downstream systems.
Challenge
- Receive messages from many devices without losing data during spikes or failures.
- Decouple ingestion from processing and from consuming systems.
- Serve fast geolocation queries.
Approach
I led the pipeline’s modernization with an asynchronous, event-driven architecture:
- MQTT at the edge for device communication.
- Azure Service Bus as the messaging backbone, decoupling ingestion, processing and consumers, with failure handling and reprocessing.
- C#/.NET services for processing, and MongoDB geospatial indexes for geolocation features.
- Contributed to architecture decisions on performance, scalability and availability, and mentored the team on solution design and code quality.
Outcome
- Decoupled, more resilient ingestion, ready for a growing device fleet.
- New geolocation features built on native geospatial queries.
- A team with more consistent design and code-quality practices.