Live data from Hacker News

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

uber.com

231–233 of 233 posts

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

#231

Earlier quoted context omitted.

It's probably more cost effective to negotiate a long-term max price with your cloud provider with a force majeure clause.

Unless you’re crazy enough to work with GCP, the “my cloud provider is going to lock me in and then raise prices” doesn’t happen. AWS has only raised prices in a few very obscure cases ever. One of which is putting a price on HEAD requests in S3 (?). AWS already gives long term price discounts/guaranteed prices for reserve pricing and Big customers already have negotiated contracts.

The size of the savings you can negotiate is a function of how locked in you are. A big customer will get discounts well beyond reserved instances, in response for (usually) committing to increase their expenditure above where it is.

The better your competing offer, the better the negotiating position. And while Amazon hasn’t gotten more expensive per se, it’s certainly not gotten cheaper.

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

#232

Earlier quoted context omitted.

Yes and I would break my NDA to answer a random question on HN for what personal gain?

It's a ridiculously innocuous question. If I were worried about blowback, I'd question working for Uber at all.

TBH I don’t trust HN with my data. They have weird account policies, and I’d not be surprised if they felt like witch-hunting someone down they would…especially in the interest of ycomb alumni

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

#233
post #176

> In preparation for the move to the cloud, the company spent two years working towards making all stateless microservices portable so that their placement in zones and regions can be managed centrally without any involvement from the service engineers I'd like to hear more about how Uber organized the engineering teams over two years to make "stateless microservices portable". How many teams? What were the requireme…

Maybe direct these questions to a C-level employee at Uber who could potentially answer them for you?

OP here... @s3p: FWIW, I didn't take issue with your comment. Surprised it was down voted. I do find that often people to reply to such comments though with something like "Uber team member here..." so it didn't seem ridiculous, but your suggestion seemed authentic and fair to me.
Post reply on HN