Trail Run Tracker — Event-Driven Checkpoint Monitoring
Checkpoint monitoring for trail running events built as microservices on Kafka: guards log runners at each checkpoint, emergencies trigger WhatsApp alerts, and organisers follow progress live, with database sync across servers.
Screenshots
Overview
What this system does.
Trail Run Tracker follows runners along a mountain route. Checkpoint guards log each bib number as it passes and report danger when a runner needs help; organisers and administrators see participants, checkpoints, check-ins, guards, and emergencies per event.
An API gateway authenticates requests with JWT and publishes events to Kafka. User, event, checkpoint, notification, and analytics services consume them, so a checkpoint pass or a danger report flows to statistics and WhatsApp alerts without the gateway waiting. A database-sync service replicates changes between servers over Kafka so each site can keep running if another goes down. The React front end gives each role — administrator, event organiser, and guard — its own dashboard, with Socket.IO for live updates.
This was a team project with Subani, my co-founder, and two teammates; I worked on the gateway, services, and dashboards.
Feature inventory
Highlights
12 capabilities verified against the project source.
- Role dashboards for administrator, organiser, and guard
- Events with checkpoints and participants
- Guard assignment per checkpoint
- Runner check-in by bib number
- Danger reports with severity
- WhatsApp emergency notifications
- Per-event statistics and progress
- API gateway with JWT
- Kafka topics between microservices
- Multi-server database sync over Kafka
- Live updates with Socket.IO
- Public participant registration
Tech stack
Built with 10 technologies.
- Node.js
- Express
- Apache Kafka
- KafkaJS
- React
- Tailwind CSS
- Socket.IO
- MySQL
- JWT
- Docker
Common questions
What people usually ask.
Why Kafka for a race?
Checkpoints, alerts, and statistics are separate concerns. Publishing events lets each service react on its own, and a slow notification never delays a check-in.
What happens if one server goes down?
Each server keeps its own database, and the sync service replays changes from Kafka so the others stay current.
Was this built alone?
No. It was a four-person team including my co-founder Subani; I worked on the gateway, services, and dashboards.
Same field
Related projects.
namakamu.cv — Free ATS Resume Builder in the Browser
A free Jadiin Online service for ATS-friendly resumes. No account and no application server: the resume stays in the browser, an ATS check flags problems, and the PDF or Word file is generated on the device.
HTML · JavaScript (ES modules) · jsPDF · Node.js · +2
SIJAGAD NU — PCNU Cilacap Integrated Platform
One platform for Nahdlatul Ulama in Cilacap: a single organisation tree from branch to sub-branch, one member registry, tiered digital decrees, meetings with quorum, instructions with receipts, and a leadership dashboard.
Laravel 13 · PHP 8.4 · Blade · Tailwind CSS · +5
Reservasi.info — Hiking & Nature Tourism Reservations
A hiking and nature-tourism reservation platform with participant quotas, group and equipment records, Tripay payments, a wallet balance, rescheduling, check-in and check-out, and visitor reports.
Laravel 12 · Filament 3 · Blade · Tailwind CSS 4 · +5