Thank you very very much. Still one point how can I calculate nearest driver to the client. I watched your video on geocach coding but I can’t find the right way to do calculations for target (a taxi driver for exemple) in movement .
one of the ways could be using google-matrix-api where you will get optimised route given the driver and target location. it can also handle multiple location and get the optimised routes.
at 3.32, Does the notification service wait for the replies from these services ? What happens if say routing service takes long to return ? Doesn't that affect the response time of our services overall ? Can we use some kind of asynchronous system there ? btw, good explanation. Keep continuing such vids
Yes. That does affect the overall system latency. That's why you want most of the common routes to be cached on the Routing Service. For other routes, you should have "some system" to precompute at least parts of the route so that they can be put together very quickly upon every request. I don't think we can use any asynchronous system here. We need to send the client the list of routes ASAP as a response to the initial HTTP request.
How do I implement a navigation system that would track a delivery driver that the user can see in real-time? I don't need the app to show delays since its just the customer viewing the delivery drivers route in real-time.
In short: You can have the "driver's" app ping the backend with coordinates, and then your backend pushes the update to the customer's app through an open web socket connection.
underrated channel.
Thats a clear and crisp video. You have such structured system design videos of why you chose which design. Thanks for the great work!
You got a unique skill of explaining design in a very simple and concise manner, keep up the great work, looking for more SD videos
I appreciate the feedback and suggestions. Will work on it.
This is really nice, learning alot from your videos
Thank you! Glad you found it valuable.
Thank you very very much. Still one point how can I calculate nearest driver to the client. I watched your video on geocach coding but I can’t find the right way to do calculations for target (a taxi driver for exemple) in movement .
one of the ways could be using google-matrix-api where you will get optimised route given the driver and target location. it can also handle multiple location and get the optimised routes.
at 3.32, Does the notification service wait for the replies from these services ? What happens if say routing service takes long to return ? Doesn't that affect the response time of our services overall ? Can we use some kind of asynchronous system there ?
btw, good explanation. Keep continuing such vids
Yes. That does affect the overall system latency. That's why you want most of the common routes to be cached on the Routing Service. For other routes, you should have "some system" to precompute at least parts of the route so that they can be put together very quickly upon every request.
I don't think we can use any asynchronous system here. We need to send the client the list of routes ASAP as a response to the initial HTTP request.
shouldn't we have used websocket instead of REST call ?
hey i have learnt a lot thanks to your channel
Glad to hear that!
How do I implement a navigation system that would track a delivery driver that the user can see in real-time? I don't need the app to show delays since its just the customer viewing the delivery drivers route in real-time.
In short: You can have the "driver's" app ping the backend with coordinates, and then your backend pushes the update to the customer's app through an open web socket connection.
BTW, where is the precomputed map is stored which is used by routing service ?? That is not clear in this design.
If your precomputed maps are static, you can use any blob storage.
💪🏼💪🏼
Thank you!
can you make a video for what star schema is?(base-design for snowflake,databricks) thank you for your effort. easiest understandable channel.
Yes I can. I will add it to my content backlog, but can't promise anything soon.
Glad you find the content easy to understand.