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.
So almost certainly they are duplicating their entire stack per-country if only to get around the vastly different regulatory environments.
But that scale introduces a lot of complexity so you can't just have "one service for onboarding drivers"
I find this hard to believe given the regulations from some of the larger countries requiring, by law, customer data be processed in country.
Responding comment says no they are not and the services are built to handle global traffic.
I respond and say I doubt that due to on soil laws.
You can argue two regions with different configurations but the same code bases are different services but that’s not what we’re talking about here.
Do you mean that your original point was about deployments to begin with?
FWIW I work in a microservices shop for a global app in an extremely regulation heavy industry, and we run a single codebase per service, segregating regulator-imposed behaviour via flags to deployments
Your fwiw is exactly what we’re taking about here and I’d venture a guess nearly half this site works for some Corp with duck tape, hope, and micro services powering their junk. Me too!
The same microservice that deployed in multiple geos still counts as one service, so considered to be 1 out of 4000 in this case.