Building Cabree: Architectural Decisions for Sub-Second Taxi Dispatching

Calvinburns — Fri, 28 Aug 2026 10:46:08 +0000

Building real-time logistics software requires balancing instant job allocation with low operational latency across high-concurrency mobile clients.

We built Cabree, a cloud-native cab dispatch system designed to give taxi operators and private hire fleets a fast alternative to legacy software.

Here is a breakdown of our core tech stack, architectural choices, and the technical challenges we solved.

Key Tech Stack

Backend Engine: Microservices architecture deployed via isolated Docker containers.
Geospatial Processing: PostgreSQL with the PostGIS extension for dynamic boundary matching, zone prioritization, and spatial queries.
Real-Time Layer: Redis pub/sub and WebSocket streams for low-latency GPS tracking and live dispatch wallboard state sync.
Mobile Clients: Cross-platform mobile applications optimized for efficient background location tracking without draining driver device batteries.

Core Engineering Challenges

1. Sub-Second Auto-Allocation Engine

Job assignment requires evaluating multiple dynamic variables in real time—driver proximity, traffic conditions, zone queues, and priority rules. By using spatial indexing ($R$-Tree / GiST) paired with cached Redis driver states, we reduced allocation calculations to under two seconds.

2. Managing High-Frequency Telemetry Pings

Active drivers continuously stream location updates. Writing every raw GPS ping directly to primary persistent storage causes severe database $I/O$ bottlenecks. We routed high-frequency location updates into a fast in-memory Redis layer, writing persistent snapshots to PostgreSQL only during active job state changes or trip completions.

3. Zero-Downtime State Synchronization

Operators, drivers, and passengers require real-time visibility without reliance on constant API polling. Implementing persistent bidirectional WebSockets keeps network overhead minimal while delivering immediate UI state sync across all active endpoints.

Explore the platform live at cabree.co.uk.

How do you handle high-throughput geospatial streams or real-time event distribution in your applications? Let's discuss in the comments below!

Building a Real-Time Cab Dispatch System: Architecture, Challenges, and Lessons Learned

Calvinburns — Tue, 11 Aug 2026 10:58:02 +0000

Building real-time logistics and dispatch software requires balancing sub-second auto-allocation with rock-solid reliability across high-concurrency mobile clients.

We recently built Cabree, a cloud-native cab dispatch system designed to give independent taxi and private hire operators a fast, modern alternative to legacy platforms.

Here is a breakdown of our core tech stack, architectural choices, and the technical challenges we solved.

Key Tech Stack

Backend: Microservices architecture deployed via Docker containers.
Database & Spatial Queries: PostgreSQL + PostGIS extension for boundary matching, spatial indexing, and dynamic distance calculations.
Real-time Layer: Redis pub/sub and WebSocket channels for sub-second GPS tracking updates and live dispatch status sync.
Frontend Apps: Cross-platform mobile clients with native location services to ensure low battery overhead during extended driver shifts.

Core Engineering Challenges

1. Sub-Second Auto-Allocation

Matching an incoming ride request isn't just about picking the nearest driver by radius. We had to calculate optimal driving routes considering live traffic, driver status, and queue prioritization. Using PostGIS spatial indexing paired with cached Redis driver states allowed us to cut allocation processing down to under two seconds.

2. Managing High-Frequency GPS Pings

Driver apps continuously broadcast location updates. Writing every ping directly to primary persistent storage causes massive DB I/O bottlenecks. We routed high-frequency location streams into a lightweight Redis layer, flushing state snapshots to PostgreSQL only when required for analytics or job completion auditing.

3. Seamless State Synchronization

When an operator updates a job dispatch wallboard, drivers, passengers, and dispatchers need to see those status changes instantly without pulling heavy poll requests. Implementing WebSocket event streams kept network overhead minimal while delivering immediate UI state syncs across all endpoints.

Check out the platform live at cabree.co.uk.

What strategies do you use for managing high-throughput geospatial data or real-time event distribution in your projects? Let's discuss in the comments below!

DEV Community: Calvinburns

Building Cabree: Architectural Decisions for Sub-Second Taxi Dispatching

Key Tech Stack

Core Engineering Challenges

1. Sub-Second Auto-Allocation Engine

2. Managing High-Frequency Telemetry Pings

3. Zero-Downtime State Synchronization

Building a Real-Time Cab Dispatch System: Architecture, Challenges, and Lessons Learned

Key Tech Stack

Core Engineering Challenges

1. Sub-Second Auto-Allocation

2. Managing High-Frequency GPS Pings

3. Seamless State Synchronization