sharonpaula76's avatar

Building a Scalable Uber-Like Taxi Platform – Architecture & Feature Discussion

Hi everyone 👋,

I’d like to start a discussion around building a scalable Uber-like taxi platform for startups. I’ve been analyzing the SpotnRides Uber clone model and would love to exchange ideas about architecture, performance, and feature implementation from a Laravel perspective.

The platform concept includes:

Real-time ride tracking

Intelligent driver-to-rider matching

Dispatch system logic

Wallet and multi-payment integration

Route optimization

Business analytics dashboard

From a technical standpoint, I’m particularly interested in discussing:

Best practices for implementing driver matching logic efficiently (queue jobs? broadcasting? websockets?).

Handling real-time ride status updates (Requested → Accepted → Ongoing → Completed) without performance bottlenecks.

Structuring payment flows securely with wallet systems.

Scaling the dispatch system as ride volume increases.

Designing an analytics dashboard that remains performant with large datasets.

If you’ve worked on ride-hailing, logistics, or real-time matching systems in Laravel, I’d really appreciate insights on architecture decisions, tools, or common pitfalls.

Looking forward to learning from the community. Thanks! 🚖

1 like
2 replies
meenachinmay's avatar

Amm Good one. So are you planning to build completely with Laravel?

1 like
vincent15000's avatar

If you need a realtime application, I recommend using Laravel only for the backend and use for example VueJS for the frontend ... or better a mobile application, so using Laravel for the backend in API mode and React Native or why not NativePHP for the frontend.

Using websockets seems to be unavoidable for realtime functionality. Broadcasting and websockets work together, so broadcasting too. You can do that with Reverb or any other event broadcaster.

Please or to participate in this conversation.