4 ms·

There's no way that number isn't fiction; Occam's razor say's its out of the range of believable. That's ~2 per eng according to Google. That's absurd. (That en

There's no way that number isn't fiction; Occam's razor say's its out of the range of believable. That's ~2 per eng according to Google. That's absurd. (That eng headcount is also a bit … high.) This sounds like a figure from someone who sees a signle microservice running across 100 pods/instances, and counted that as 100 "microservices".

scarface_74 3y ago
S3 alone is built on top of 300 micro services. I don’t find it unbelievable that Uber needs a lot of them.
- zo1 3y ago
  I find it highly disturbing that so far I've seen Zero Uber devs on this thread adding any sort of context/info or just confirmation. Wtf is this, the NSA? KGB? Can't they just list/dump the names of said 4000 services, or is that somehow some sort of secret-sauce?
  - scarface_74 3y ago
    A random engineer at any company is not going to divulged non public information about the inner working of their company without permission. We had to sign something at AWS not to divulge internal tooling like what we used for our internal account factory that we used to create AWS accounts. Literally tens of thousands of people know what this tool is.
    - x86x87 3y ago
      you see someone telling you how many microservices s3 has right above.
      - scarface_74 3y ago
        Yes that “someone” was me - a former employee who couldn’t remember whether that information was public or whether it was something I was exposed to from the inside. It in fact was public. https://aws.amazon.com/blogs/storage/how-automated-reasoning-helps-us-innovate-at-s3-scale/#:~:text=S3%20is%20built%20from%20over,form%20a%20distributed%20storage%20system https://aws.amazon.com/blogs/storage/how-automated-reasoning.... I verified that before I posted that little tidbit.
Game_Ender 3y ago
Uber invested heavily in tooling that makes creating and deploying a new service take about 30 minutes. This was before they invested in making it as easy to share code. If you combine that with fast hiring and a big pressure to ship, it makes sense to solve every problem with a new service that calls a few others.

scarface_74 3y ago

S3 alone is built on top of 300 micro services. I don’t find it unbelievable that Uber needs a lot of them.

zo1 3y ago
I find it highly disturbing that so far I've seen Zero Uber devs on this thread adding any sort of context/info or just confirmation. Wtf is this, the NSA? KGB? Can't they just list/dump the names of said 4000 services, or is that somehow some sort of secret-sauce?
- scarface_74 3y ago
  A random engineer at any company is not going to divulged non public information about the inner working of their company without permission. We had to sign something at AWS not to divulge internal tooling like what we used for our internal account factory that we used to create AWS accounts. Literally tens of thousands of people know what this tool is.
  - x86x87 3y ago
    you see someone telling you how many microservices s3 has right above.
    - scarface_74 3y ago
      Yes that “someone” was me - a former employee who couldn’t remember whether that information was public or whether it was something I was exposed to from the inside. It in fact was public. https://aws.amazon.com/blogs/storage/how-automated-reasoning-helps-us-innovate-at-s3-scale/#:~:text=S3%20is%20built%20from%20over,form%20a%20distributed%20storage%20system https://aws.amazon.com/blogs/storage/how-automated-reasoning.... I verified that before I posted that little tidbit.

Game_Ender 3y ago

Uber invested heavily in tooling that makes creating and deploying a new service take about 30 minutes. This was before they invested in making it as easy to share code. If you combine that with fast hiring and a big pressure to ship, it makes sense to solve every problem with a new service that calls a few others.