Twitter | Search | |
Ben Sandofsky
Uber in 2016: “We have thousands of microservices.” Everyone: “That sounds insane." Uber in 2020: “It turns out that was insane.”
Reply Retweet Like More
Ben Sandofsky Apr 7
Replying to @sandofsky
Reply Retweet Like
Leo Picado Apr 7
Replying to @sandofsky
Context? Was there a post or article about this?
Reply Retweet Like
Dan Jacka Apr 7
Replying to @leopyc
Reply Retweet Like
Bill Mckim Apr 7
Replying to @sandofsky
I’m not sure people will get into strangers cars after this is over
Reply Retweet Like
Charles Choi Apr 7
Replying to @sandofsky
Yep. When I read their post then bragging about thousands of microservices, I thought, there’s a place that failed to think through architecture.
Reply Retweet Like
Ari Tanninen Apr 8
Replying to @cy_choi @sandofsky
Yes exactly! Did someone forget that we need multiple levels of abstraction, and composition? Regardless of microservices, distributed objects, components, or what have you.
Reply Retweet Like
Zac Sweers Apr 7
Replying to @sandofsky
One person at Uber is probably not reflective of all the teams at large. Most backend teams when I was there existed in silos and there's very little in the way of consensus or higher level organization. Microservices were more of a symptom of that.
Reply Retweet Like
Zac Sweers Apr 7
Replying to @sandofsky
The payments team generally have their shit together though, Uber as a whole would usually do well to follow their lead in a number of ways.
Reply Retweet Like
Andrew Meredith Apr 7
Replying to @sandofsky
I was waiting to see if it went so far as to make each service effectively a single function that only calls other functions over RPC. Sanity was restored sooner that expected.
Reply Retweet Like
Alex 👩🏼‍💻 Apr 7
Replying to @asmeredith @sandofsky
I’ve seen somewhere do this it was pretty nuts.
Reply Retweet Like