4 ms·
I appreciate the niche you're filling here for smaller projects. Going through the pain of self-hosting OSRM and VROOM, then building an API layer around it, is
by MarcelinoGMX3C 6mo ago
I appreciate the niche you're filling here for smaller projects. Going through the pain of self-hosting OSRM and VROOM, then building an API layer around it, is a real time sink that most hobbyists or small teams can't justify. My team ended up moving to a managed service a while back due to the operational overhead, but something like this could have been a good stepping stone.
From a DevSecOps perspective, running a Django API gateway on a single Hetzner dedicated server for a service like this concerns me a bit. What's the failover strategy if that server goes down? I'd be looking at potential single points of failure for data and availability. You mentioned low costs, but how are you handling redundancy and regular patching for the Django and underlying OSRM/VROOM stack in that setup?
- tristanmk 6mo agoGreat questions. Every project starts somewhere :) In this "testing market fit" phase, everything (api gateway, postgres, osrm, vroom, analytics, etc) is hosted on one server. As the project scales, servers will scale, for increased throughput and redundancy.