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
Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
131–140 of 233 posts
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#132In 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”.
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#133Earlier 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…
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
#134Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#135For 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.
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#136In 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/
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#137Does 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…
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#138Does Uber really need 4000 microservices?
Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#139Re: Uber migrates microservices to multi-cloud platform running Kubernetes and Mesos
#140Does Uber really need 4000 microservices?
This sounds like a figure from someone who sees a signle microservice running across 100 pods/instances, and counted that as 100 "microservices".