Live data from Hacker News

Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

uber.com

131–140 of 233 posts

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#131

Earlier quoted context omitted.

UberEats

Where does a line cook's use case fit in it? From what I know, uber eats sends a order to a restaurant, an employee manually punches in the order on their POS system, and the order ticket goes into the kitchen

You don't think there are a variety of people at a restaurant who might interact with the system? Is this particular detail so very important to the point of the parent comment?

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#132

In 3 years… “Uber saved cost by migrating their micro service to their own colo.” followed by “Uber simplified operations by migrating their micro service platform to a monolith”.

I'm not sure why this is an issue with a long running system. Business requirements change, knowledge changes, cost structures change, etc... Unfortunately the world isn't static. I'm not sure about you, but when the facts change I also try to change.

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#133
post #130
post #125

Earlier quoted context omitted.

That isn't what bad faith typically covers? Bad faith is easiest seen when they hold opposition to higher standards than they can hit. In particular, on purpose. It is a smoke and mirror dialogue that is not intended to make progress, but only to spend the other side's time. In contrast, being wrong and or not fully grasping difficulties is normal. And sometimes, you get lucky and unexpectedly make progress

This is my core contention: negligence of bringing one's efforts to suitably address the problem is not necessarily intentional a la mens rea , but rather demonstrates that a person is not appropriately engaging their mental and cognitive faculties and in essence disrespects the entire process to which they've assigned themselves. These processes are bigger than individuals and it behooves one to engage in ways that…

I can see the similarities. That said, there is an advantage to allowing a bit of hubris in young teams. It is a gambit that can uncover absurd progress.

There is also a bit of the established problems obfuscating themselves. Such that it is easy to see many new workers have been given the run around many times.

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#135
post #58

For a company that is basically a taxi service, they seem to invest an awful lot in constant rebuilds of their extremely complex infrastructure, which raises the question of whether that is even remotely necessary or just an exercise in pretending that they are a tech company.

“Basically a taxi service,” except that Uber spans hundreds of cities, coordinates millions of drivers - none of whom work on a fixed schedule - and its only interface with customers is an app that has to be fast, accurate, and reliable at all times.

Even a single taxi event is complex. Tell Uber you want to go to the ATL airport and it'll ask which terminal. If you're catching one from the ATL airport, it'll map and walk you to the rather distant pick up spot. And we haven't even touched on payment yet...

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#136

In 3 years… “Uber saved cost by migrating their micro service to their own colo.” followed by “Uber simplified operations by migrating their micro service platform to a monolith”.

Might be a good guess, there's precedent of them changing fundamental techology in a similar timeframe... 2013: "Migrating Uber from MySQL to PostgreSQL"[1] 2016: "Why Uber Engineering Switched from Postgres to MySQL"[2] [1] https://www.yumpu.com/en/document/view/53683323/migrating-ub... [2] https://www.uber.com/en-GB/blog/postgres-to-mysql-migration/

More like “we hired a new principal arch who drove a change they personally liked, and everything was better because it allowed a lot of time to fix tech debt”

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#137
post #2

Does Uber really need 4000 microservices?

A different (better?) question is, does Uber need 4000 API contracts? The answer to that is probably yes. APIs let us split work across systems/people/teams/regions, and provide a way for both sides of a split to work together. Uber has a lot of teams, a lot of engineers, and so it makes sense that there are a lot of API boundaries to allow them to work together more efficiently. Sometimes those APIs make sense to pa…

Microservices allow development orgs to scale horizontally which enables businesses to expand to adjacent markets, faster.

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#138
post #2

Does Uber really need 4000 microservices?

There's an an interesting HN comment[1] from 2020 by former Uber engineer, which discusses the complexity a bit. It's more about UI, but the thread discusses the backend as well. In brief something that may look super simple for the user (like handling payments) is actually quite complicated when you cover all the market, different payment types etc. And all this carries to the backend as well.

[1] https://news.ycombinator.com/item?id=25376346

Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos

#140
post #2

Does Uber really need 4000 microservices?

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".

Post reply on HN