Re:The architecture of Uber’s API gateway
by thundergolfer on Sunday May 23, 2021 @06:47AM
(#27254038)
That post you linked is the one that got heavily criticised by a Bing Maps engineer for being under-engineered[1].
1. https://medium.com/@buckhx/unwinding-uber-s-most-efficient-s...
While the linked post maybbe right. I completely agree with the Uber engineers that it sounds too complicated. I can understand the double polygon search without thinking about it.
I also understand the double polygon search with bounding box optimization, so I’m not sure why that wasn’t used.
If that’s the case, it’s weird that they would take the time to write a blog post about how great their algorithm is while effectively saying that they didn’t understand the other approaches and that they were too hard.
This entry, for example, mentions how they avoided Go routines as a "performance concern" even without any data to prove it. It's bush league level to think you can do it better yourself.
https://eng.uber.com/go-geofence-highest-query-per-second-se...