What I Wish I Had Known Before Scaling Uber [video]

amelius wrote: post #4

I didn't see the video. But given that a cab-service has a natural sharding point (i.e., per city), I don't get why scaling is such an issue.

Some cities are bigger than others. That's a heavily imbalanced sharding key.

Re: What I Wish I Had Known Before Scaling Uber [video]

#6

Post by kenrose » Wed, Sep 28, 2016, 1:36 PM UTC

tiborsaas wrote: post #2

"Uber is most reliable over the weekends when engineers don't change it" :)

We see this pattern at PagerDuty over the majority of our customers. There is a definite lull in alert volume over the weekends that picks up first thing Monday morning.

It's led to my personal conclusion that most production issues are caused by people, not errant hardware or systems.

Re: What I Wish I Had Known Before Scaling Uber [video]

#7

Post by tiborsaas » Wed, Sep 28, 2016, 1:36 PM UTC

amelius wrote: post #4

I didn't see the video. But given that a cab-service has a natural sharding point (i.e., per city), I don't get why scaling is such an issue.

Cab service on a planetary scale :) They have 2000 engineers, 800 microservices and 8000 GIT repositories. Does it still seem trivial to you?

EDIT: to downvoters: why shoot the messenger? :)

Re: What I Wish I Had Known Before Scaling Uber [video]

#8

Post by asimuvPR » Wed, Sep 28, 2016, 1:39 PM UTC

kenrose wrote: post #6

tiborsaas wrote: post #2

"Uber is most reliable over the weekends when engineers don't change it" :)

We see this pattern at PagerDuty over the majority of our customers. There is a definite lull in alert volume over the weekends that picks up first thing Monday morning. It's led to my personal conclusion that most production issues are caused by people, not errant hardware or systems.

I've come to question releasing often as a result.

Re: What I Wish I Had Known Before Scaling Uber [video]

#9

Post by cheez » Wed, Sep 28, 2016, 1:40 PM UTC

tiborsaas wrote: post #7

amelius wrote: post #4

I didn't see the video. But given that a cab-service has a natural sharding point (i.e., per city), I don't get why scaling is such an issue.

Cab service on a planetary scale :) They have 2000 engineers, 800 microservices and 8000 GIT repositories. Does it still seem trivial to you? EDIT: to downvoters: why shoot the messenger? :)

Sounds like they have 2000 very individualistic engineers with that level of insanity.

Re: What I Wish I Had Known Before Scaling Uber [video]

#10

Post by itsthecourier » Wed, Sep 28, 2016, 1:40 PM UTC

amelius wrote: post #4

I didn't see the video. But given that a cab-service has a natural sharding point (i.e., per city), I don't get why scaling is such an issue.

Hey where are my travel logs? Uhhh can't watch them, I'm in another city today :(