Normalizing GPS telemetry from 8k vehicles across half a dozen sources
Polished APIs, flaky devices, customer-internal feeds — what cross-source GPS normalization actually looks like in production.
// distributed systems
GPS normalization
8–10k vehicles · 40–80M events/day
Stub. Full post body to follow.
Every fleet customer brought their own tracking stack — some with polished HTTP APIs, some with devices that still spoke a custom binary protocol over 2G. Add in customer-internal trip-management systems and third-party carrier APIs, and “normalization” stops being a string-transform exercise and starts being a noise-filtering + state-machine problem.
// RELATED
2026-03-20 · 11 min · DISTRIBUTED SYSTEMS
Building a CDC pipeline with Debezium — without breaking the source
Lessons from tailing a multi-tenant Mongo oplog into Kafka without putting the source database under more load than it already had.
2026-02-02 · 9 min · DISTRIBUTED SYSTEMS
OpenTelemetry: trace, log, metric — one stack, three signals
What it actually costs to consolidate observability onto OTel + Grafana + Loki + Tempo + VictoriaMetrics, and what you get back.