Live data from Hacker News

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

uber.com

101–110 of 233 posts

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

#101
post #80

Earlier quoted context omitted.

Later "Lowering cost and dramatically reducing complexity with nanofunctions running on monoecosystem".

Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.

It’s been happening since the dawn of time, fat client/thin client, static link/dynamic link, micro services/monolith, centralised/decentralised, it doesn’t just migrate from one to the other, the pendulum swings back and forwards, and will do for eternity.

You can be all angry about it, but being angry at the storm doesn’t affect the storm, it only affects you. A lot. Negatively.

The trick is to position yourself to maximally profit from the next trend swing, I’ve been doing it for 20 years now, if you can predict where the next place is gold will fall from the sky, then go and stand there, with a really big bucket.

I always found it strange that there is a certain type of intellect who is capable of accurate observation of reality, but incapable of execution (sometimes called “the disconnected intellect”), they can tell you exactly the problem, and the solution, but sit angry/frustrated that the observed world doesn’t match some imagined ideal in their head, and rather than adapt their internal model and be entrepreneurial enough to capture the value that generates, they bleet and complain while losing all opportunities - opportunities they can see! I can’t imagine being like this.

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

#102
post #80

Earlier quoted context omitted.

Later "Lowering cost and dramatically reducing complexity with nanofunctions running on monoecosystem".

Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.

I’m 30+ years in and I don’t think there’s any bad faith. It’s just people who are new seeing all of the problems with the old implementation and thinking their way will be better.

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

#103
post #89

Earlier quoted context omitted.

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…

Uber has several different APIs for users. A naive purist might think that's silly until you realize a rider is user, a driver is a user, a courier is a user, a restaurant owner is a user, a line cook is a user, a doctor's secretary is a user, a Uber employee is a user, a freight broker is a user, an advertising manager is a user... people can simultaneously be multiple types of users and have multiple profiles as a…

> a line cook is a user, a doctor's secretary is a user

I was with you on other types of users, but can you elaborate on these particular use cases?

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

#104
post #80

Earlier quoted context omitted.

Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.

I’m 30+ years in and I don’t think there’s any bad faith. It’s just people who are new seeing all of the problems with the old implementation and thinking their way will be better.

That is bad faith. They're not trying to understand the systems that they feel they can take the responsibility to try to "fix".

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

#105
post #80

Earlier quoted context omitted.

Don't even start on that. It's no longer funny coming up with things like that for me. I'm currently trying to get out of the industry because I'm drowning in architectural bullshit like this constantly. It is pedalled by snakes, bastards and wankers who care nothing for solving problems but want to create new ones.

It’s been happening since the dawn of time, fat client/thin client, static link/dynamic link, micro services/monolith, centralised/decentralised, it doesn’t just migrate from one to the other, the pendulum swings back and forwards, and will do for eternity. You can be all angry about it, but being angry at the storm doesn’t affect the storm, it only affects you. A lot. Negatively. The trick is to position yourself to…

I have ridden these fads for the last 25 years (well actually longer - I had a different career first!) and made a fuck load of money out of it. But I am tired of it now. I really don't care any more.

I am fed up of solving the same problems again and again. It's more than just earning; there's intellectual dishonesty in this and it's tiring and demotivating.

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

#106
post #2

Does Uber really need 4000 microservices?

From experience working at big tech I’m willing to take a guess.

Maybe a couple of dozens will be actual more complex and meaningful services. Then few dozens more services that are somewhat more unique.

And then majority of the long tail will be mostly cookie cutter services, doing X, but for lots of different use cases, where each of use cases is separate deployment counting as a service (for example - systems to process streams of logs related to business logic).

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

#107
post #23

It seems like they’ve gotten to the “holy grail” of deployment where developers don’t have to worry about infrastructure at all in theory. I’ve seen many teams go for simple/leaky abstractions on top Kubernetes to provide a similar solution, which is tempting because it’s easy and flexible. The problem is then all your devs need to be trained in all the complexities of Kubernetes deployments anyway. Hopefully Uber ab…

It's not clear to me that being completely unaware of your infrastructure is a good thing. I don't think it's too much trouble to ask an engineer to understand k8s and think about where their service will live, even if it's a ci system that actually deploys. Furthermore, many layers of abstraction, especially in-house abstraction, just mean you have more code to maintain, another system for people to learn, and exist…

All it takes is for one microservice to start hanging on a GRPC request, server hardware stops doing some fundamental thing correctly, or some weird network quirk that 10x’s latency to half the switch ports in a rack, and you end up with insane, sophisticated cascade failures.

Because engineers don’t have to understand infra, it often spans geographies and failure domains in unanticipated, undetectable ways. In my opinion the only antidote is a thorough understanding of your stack down to the metal it’s running on.

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

#108
post #89

Earlier quoted context omitted.

Uber has several different APIs for users. A naive purist might think that's silly until you realize a rider is user, a driver is a user, a courier is a user, a restaurant owner is a user, a line cook is a user, a doctor's secretary is a user, a Uber employee is a user, a freight broker is a user, an advertising manager is a user... people can simultaneously be multiple types of users and have multiple profiles as a…

> a line cook is a user, a doctor's secretary is a user I was with you on other types of users, but can you elaborate on these particular use cases?

UberEats

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

#109
post #2

Does Uber really need 4000 microservices?

(Worked at Lyft) Our number of active micro services was small in comparison. 4,000 is likely a overblown number to highlight the accomplishment possibly counting inactive ones

Worked at Grab. They had a ton of micro services. It was their way of partitioning databases so that they didn't have to deal with joins. Yes, it caused a lot of problems.

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

#110
post #89

Earlier quoted context omitted.

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…

Uber has several different APIs for users. A naive purist might think that's silly until you realize a rider is user, a driver is a user, a courier is a user, a restaurant owner is a user, a line cook is a user, a doctor's secretary is a user, a Uber employee is a user, a freight broker is a user, an advertising manager is a user... people can simultaneously be multiple types of users and have multiple profiles as a…

Plus there's a surprisingly high floor on the number of apis a large company needs for basic stuff like "set up new hires automatically in all the system needed"
Post reply on HN