Does Uber really need 4000 microservices?
Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
21–30 of 233 posts
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#22Earlier 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…
I wonder what setting up a local dev instance is like for anything involving more than one or two of those.
And the thing is that nobody ever needs to run the entire stack other than end to end tests which get run in the cloud.
You just checkout the services you need and because they are designed to be isolated the dependencies will usually be automatically stubbed out. So it's just a matter of running them or chaining them together if you have a particular scenario to test.
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#23I’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 abstracted away Kubernetes and Mesos enough to be worthwhile, and they have a great infra team to support the devs.
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#24Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#25[flagged]
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#26It 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…
They all use GitOps which means all infra deployments and changes are tracked and easily able to be rolled back on any issues. And the complexity is nothing compared to having to manage your own cloud resources using Terraform etc which used to be the case.
And these days every developer needs to be on board with DevOps and so there are no real old-school infra teams supporting anyone.
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#27[flagged]
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#28Does Uber really need 4000 microservices?
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#29Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#30Does Uber really need 4000 microservices?
It reminds me this thread about Netflix, with insane amounts of events and logs compared to active users. https://news.ycombinator.com/item?id=30635369