Designing a telemetry stack for hurling forced us to treat a 70mm sliotar moving at 120 km/h as a real-time distributed systems problem.
When our team started Building a live analytics platform for a county-level hurling squad, we assumed existing GPS-based sports tracking would translate. It did not. Hurling combines field dimensions of roughly 145 by 90 meters, 30 players, a stick called a hurley, and a small leather ball called a sliotar that regularly moves faster than many engineers' test traffic. The on-premise realities of a GAA stadium-variable lighting, wind, rain. And dense player clusters-quickly exposed every assumption we had about video pipelines, telemetry buses. And data modeling.
This article breaks down the systems architecture, computer vision, edge infrastructure. And data engineering decisions that emerged from that project. Whether you're building real-time sports analytics, industrial machine vision. Or low-latency event pipelines, the constraints in hurling provide a useful stress test.
Why Hurling Demands a Different Telemetry Architecture
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →