Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
Loading the challenge…
While this loads — quick one
Every subscriber must get each event. A queue, or pub/sub?
A ride-hailing app shows riders the drivers near them and matches each ride request to a close, available driver. Every active driver's phone reports its location every few seconds, which means hundreds of thousands of position updates a second at peak, and each one matters only until the next arrives. A rider asking for nearby drivers must get an answer in well under a second, and the answer must reflect where drivers are now, not where they were a minute ago. Completed trips, fares and payments, on the other hand, must be recorded exactly and kept for years, and a match must never assign the same driver to two riders.
Every system design question opens with an account. Your design is scored the same way every time, with the reason behind each requirement, and your attempts are kept so you can see what you found hard.