As you already know, the idea is to eventually have a server running which can autoscale and without the need to create VM for each of them. Nevertheless, to have a first MVP I think it would be best to simply have a server that can do only routing. I think all other functionality can be done through Firebase functions.
This ticket is only about th server setup. I am leaving the decision to you of where/how to do that since I think you have more knowledge about it.
Later on we can iterate through it and find a more fitting solution to scale it.
This is how I thought about it (request for comments):
[x] - expose a single endpoint "directions" or "routing" ...
[ ] - load an OSM file on start, no need to update while running
[ ] - the endpoint returns a response similar (or equal) to that of MapBox (see here). The point here is to avoid re-inventing the wheel and instead use a format that we already know that works.
In the following days I will introduce routing to the Android App using the response that I get from MapBox. The idea is that eventually we could just replace it with our own routing.
Hey Mehdi,
As you already know, the idea is to eventually have a server running which can autoscale and without the need to create VM for each of them. Nevertheless, to have a first MVP I think it would be best to simply have a server that can do only routing. I think all other functionality can be done through Firebase functions.
This ticket is only about th server setup. I am leaving the decision to you of where/how to do that since I think you have more knowledge about it.
Later on we can iterate through it and find a more fitting solution to scale it.
This is how I thought about it (request for comments):
In the following days I will introduce routing to the Android App using the response that I get from MapBox. The idea is that eventually we could just replace it with our own routing.