Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

uber.com

Post reply on HN
Print view View original

11–20 of 233 posts

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

#13

Post by 0xblinq »

ninja3925 wrote: post #4
x86x87 wrote: 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

[flagged]

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

#14

Post by whynotmaybe »

x86x87 wrote: post #2

Does Uber really need 4000 microservices?

There's quite a sizing range between monolith and microservice.

If all their It needs are behind micro "micro" services, that figure is understandable.

Outside of the map, taxi, food, payments, onboarding, they also have monitoring, deployment, HR, billing, legal, taxes, internationalized stufd, and the usual "..." for what I'm missing.

If you just take a standard ERP, you could easily split it in dozens even hundreds of microservices.

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

#17

Post by threeseed »

x86x87 wrote: post #2

Does Uber really need 4000 microservices?

Uber is a global company (70+ countries) operating Uber and Uber Eats.

So almost certainly they are duplicating their entire stack per-country if only to get around the vastly different regulatory environments.

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

#18

Post by davidw »

danpalmer wrote: post #5
x86x87 wrote: 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…

I wonder what setting up a local dev instance is like for anything involving more than one or two of those.

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

#19

Post by talent_deprived »

x86x87 wrote: post #2

Does Uber really need 4000 microservices?

I've seen at least one place with many more than that in recent years. If you have one microservice "listener" per queue and another for the database processing and persistence (business logic) and another providing an API for one or more frontend UI's related to it then the microservice tally goes up very fast. It's kind of surprising to read so many comments indicating HN readers weren't aware of this.

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

#20

Post by bcrosby95 »

whynotmaybe wrote: post #14
x86x87 wrote: post #2

Does Uber really need 4000 microservices?

There's quite a sizing range between monolith and microservice. If all their It needs are behind micro "micro" services, that figure is understandable. Outside of the map, taxi, food, payments, onboarding, they also have monitoring, deployment, HR, billing, legal, taxes, internationalized stufd, and the usual "..." for what I'm missing. If you just take a standard ERP, you could easily split it in dozens even hundred…

> If all their It needs are behind micro "micro" services, that figure is understandable.

I call them nano services.

Post reply on HN