I will build a realtime iot data pipeline in go


About this gig
I design and build real-time IoT data pipelines in Go engineered to handle continuous device data without falling over at scale.
I architected a telematics platform processing real-time GPS data from over 20,000 devices transmitting continuously. I built a custom reliable-UDP protocol to prevent data loss on unstable connections, and a cost-efficient cold-storage architecture (S3 + indexed lookups) that avoided runaway database costs as data volume grew.
I've also applied this same expertise in healthcare: leading the redesign of a monolithic health IoT platform integrating device data from Dexcom, Medtronic, and other connected devices into a scalable microservices architecture, including a FHIR implementation in Go for clinical data interoperability. This is a rare combination, since most FHIR tooling in the market is Java or Python-based.
Whether your devices are vehicles, sensors, wearables, or medical hardware, I can design the ingestion, storage, and retrieval architecture to handle real-world scale reliably, and without unnecessary cost.
Let's talk about what your device data actually needs.
Get to know Aafaq Z
- FromPakistan
- Member sinceJul 2023
- Avg. response time1 hour
Languages
Urdu, English, Punjabi
My Portfolio
FAQ
Do you work with both vehicle/sensor telematics and healthcare IoT?
Yes — I've built production systems in both domains. The core engineering challenge is the same: reliable ingestion of continuous device data at scale. I bring healthcare-specific experience (FHIR, Dexcom/Medtronic integration) when that's relevant to your project.
What happens if my devices lose connection mid-transmission?
I design for this explicitly. I've built custom protocols to prevent data loss on unstable connections, so dropped packets don't mean lost data.
My database costs are growing fast as device volume increases — can you help?
Yes, this is a common problem at scale. I've built cold-storage architectures (e.g., S3-backed with indexed lookups) that significantly reduce database costs while preserving full historical data access.
Do you need my existing codebase to get started?
Not necessarily for architecture design (Basic package), but for pipeline implementation (Standard/Premium), access to your existing data model and any current integration points speeds things up significantly.
Is FHIR compliance included by default?
It's included in the Premium package if your project involves healthcare data. For non-healthcare IoT projects, it's not applicable and won't affect pricing.
