Taxi-hailing App - API / gRPC Issue Fixing - Used Tech: GCP and NodeJS
Budget: €750 – €1,500 EUR
We have a taxi-hailing app. We are trying to create a product with the simplest structure possible, using Google Maps API, live location tracking, and user ride requests.
The backend is completely based on Google Cloud Platform. In the gRPC section, our services are prepared on Cloud Run and in Node JS language (Serverless Architecture).
The front end uses Flutter. Our team includes 2 Flutter experts. We are only looking for a backend engineer. It is also important to be proficient in Node JS. If not, you can have a teammate who works with it in your network.
There are only some issues with the rides section. What’s going wrong:
The root cause is how the backend handles driver stream connections, disconnections, and ride status transitions.
When a driver completes a ride, they are not being properly re-added to the pool of available drivers in Redis or Firestore.
If a driver’s app disconnects (closes or loses connection), the server doesn't cleanly remove or recover their state — so they become invisible on the map.
Some ride requests fail to reach drivers because their connection is either lost or not registered correctly in the system.
There may also be race conditions where Redis and Firestore fall out of sync, especially under load or during frequent driver state changes.
We need an experienced expert for back-end of our mobile app.
The backend is completely based on Google Cloud Platform. In the gRPC section, our services are prepared on Cloud Run and in Node JS language (Serverless Architecture).
The front end uses Flutter. Our team includes 2 Flutter experts. We are only looking for a backend engineer. It is also important to be proficient in Node JS. If not, you can have a teammate who works with it in your network.
There are only some issues with the rides section. What’s going wrong:
The root cause is how the backend handles driver stream connections, disconnections, and ride status transitions.
When a driver completes a ride, they are not being properly re-added to the pool of available drivers in Redis or Firestore.
If a driver’s app disconnects (closes or loses connection), the server doesn't cleanly remove or recover their state — so they become invisible on the map.
Some ride requests fail to reach drivers because their connection is either lost or not registered correctly in the system.
There may also be race conditions where Redis and Firestore fall out of sync, especially under load or during frequent driver state changes.
We need an experienced expert for back-end of our mobile app.