educative.io

QuadTree tech stack

Hi @Shaheryaar_Kamal & @Design_Gurus,

so for these 3 components as shown in the figure in this chapter:

QuadTree Index
QuadTree server
Driver Location Server

which tech stacks would you choose to actually build them? I think that would help me to understand this architecture better.

Hi @milo_t

Most of the Map Services runs on a primarily Java-based stack, so it is always preffered.

But for each process we can divide the app as following:

Below we have compiled the technology stack that you’ll need to make your traveling app :

  • Kotlin – For Android apps)
  • Swift – For iOS apps)
  • io – For providing a seamless playing experience.
  • APNS – For push notifications.
  • Firebase – For building your mobile application.
  • Facebook SDK – For analyzing how people interact with your app.
  • Google Maps – For routing and navigation.
  • Google Places – For directions and location fetching.
  • js for back-end development.
  • Elastic Email – An Email delivery engine.
  • io – For in-app chatting/messaging.
  • Google Directions – For routing.
  • Amazon EC2 – For cloud hosting experience.
  • Amazon S3 – For cloud storage.
  • Braintree/Stripe – For online transactions (payment).
  • Twilio – For SMS notification.

The above-mentioned technology stack is an idea of what you need to develop your Uber-like app. However, keep in mind that the technology stack may change concerning the business objectives, features, functionality, and platform.

thanks @Shaheryaar_Kamal, that’s quite an exhaustive list of all technologies available. my question was in a way simpler, for example:

  1. which database do the authors suggest using for QuadTree Index?
  2. is the Driver Location Server just a Redis cluster?
  3. is the QuadTree server also a Redis cluster?

are you by any chance one of the @Design_Gurus?