<story><title>What I Wish I Had Known Before Scaling Uber [video]</title><url>https://www.youtube.com/watch?v=kb-m2fasdDY</url></story><parent_chain></parent_chain><comment><author>iamleppert</author><text>It amazes me they have 1,700 services. It would be hilarious satire to actually see the description of each. And the debugging scenarios he listed make it sound like they have very poor engineers working for them. Who on earth lets an application get to prod that iterates through a list of items and makes a request for each thing?&lt;p&gt;When did we loose our heads and think such an architecture is sane? The UNIX philosophy is do one thing and do it well, but that doesn&amp;#x27;t mean be foolish about the size of one said thing. Doing one thing means solving a problem, and limited the scope of said problem so as to have a cap on cognitive overhead, not having a notch in your &amp;quot;I have a service belt&amp;quot;.&lt;p&gt;We don&amp;#x27;t see the LS command divided into 50 separate commands and git repo&amp;#x27;s.....</text></comment>
<story><title>What I Wish I Had Known Before Scaling Uber [video]</title><url>https://www.youtube.com/watch?v=kb-m2fasdDY</url></story><parent_chain></parent_chain><comment><author>paukiatwee</author><text>Just to confirm, 1000 microservices in this case is 1000 different apps (e.g.different docker images) running simultaneously? 1000 microservices in this case not 1000 microservice instances (e.g. docker instances)?&lt;p&gt;If it is 1000 microservices as in different apps, then they must have at least 2000 running apps (at least 2 instances per app for HA).&lt;p&gt;Maybe uber only have 200 &amp;quot;active&amp;quot; microservice app running at the same time where each microservices have N running instances.&lt;p&gt;I just cant imagine running 1000 different microservices (e.g different docker images, not docker instances) at the same time.</text></comment>