Real-time systems
that keep moving.

Modernizing a real-time ride-hailing backend.

I worked on the modernization of a legacy taxi ride-hailing backend, leading an event-driven refactor and introducing a Node.js WebSocket layer for live ride tracking.

A legacy system slowing down product development.

Too much engineering time was being spent reacting to production issues instead of building new product functionality. The existing backend had become difficult to evolve reliably.

The challenge went beyond adding live tracking. The system needed clearer real-time behavior that could support ongoing development.

Moving toward event-driven flows.

I led a refactor of the backend toward an event-driven model and added a Node.js WebSocket layer to deliver live ride-tracking updates to connected clients.

The flow below is a conceptual explanation of real-time updates, rather than an inventory of internal architecture components.

1. Ride state

   • A ride changes state

2. Backend event

   • The backend handles the change

3. WebSocket layer

   • Node.js delivers the update

4. Real-time update

   • Live tracking information

5. Client

   • Connected clients receive the update

My contribution.

Event-driven refactor

Led the modernization of the legacy backend toward event-driven flows, making its real-time behavior easier to reason about and extend.

Real-time tracking

Added a Node.js WebSocket layer enabling live ride tracking and real-time communication with connected clients.

Production stabilization

Worked through legacy backend constraints and recurring production issues as part of the modernization.

System ownership

Worked across architecture and implementation, treating tracking as part of the backend system.

Real-time as part of the architecture.

Ride-state changes needed a path through the backend that could reach connected clients as they happened.

Event-driven flows and a WebSocket layer created that path while supporting the modernization of the surrounding legacy system.

From firefighting to forward motion.

The modernization helped shift the team's engineering work away from repeatedly firefighting legacy backend issues and toward shipping new product features.

• Node.js
• NestJS
• WebSockets