<story><title>The Uber Engineering Tech Stack, Part I: The Foundation</title><url>https://eng.uber.com/tech-stack-part-one/</url></story><parent_chain></parent_chain><comment><author>Animats</author><text>It&amp;#x27;s interesting that they don&amp;#x27;t break the problem apart geographically.  It&amp;#x27;s inherent in Uber that you&amp;#x27;re local. But their infrastructure isn&amp;#x27;t organized that way.  Facebook originally tried to do that, then discovered that, as they grew, friends weren&amp;#x27;t local.  Uber doesn&amp;#x27;t need to have one giant worldwide system.&lt;p&gt;Most of their load is presumably positional updates.  Uber wants both customers and drivers to keep their app open, reporting position to Master Control.  There have to be a lot more of those pings than transactions.  Of course, they don&amp;#x27;t have to do much with the data, although they presumably log it and analyze it to death.&lt;p&gt;The complicated part of the system has to be matching of drivers and rides.  Not much on that yet. Yet that&amp;#x27;s what has to work well to beat the competition, which is taxi dispatchers with paper maps, phones, and radios.</text></comment>
<story><title>The Uber Engineering Tech Stack, Part I: The Foundation</title><url>https://eng.uber.com/tech-stack-part-one/</url></story><parent_chain></parent_chain><comment><author>NotQuantum</author><text>Uber is really strapped for engineering talent. Especially when it comes for SRE. Myself and many friends working SRE at various Bay Area companies get consistently hit up for free lunches and interviews. It&amp;#x27;s really weird considering that their stack doesn&amp;#x27;t NEED to be this complex....</text></comment>