What I Wish I Had Known Before Scaling Uber to 1000 Services • Matt Ranney • GOTO 2016
GOTO Conferences
Why leaders watch it
Honest account of what went wrong scaling to a thousand services, with lessons on sprawl, ownership and organizational consequences of technical choices.
Matt Ranney of Uber talks at GOTO Chicago 2016 about what Uber learned from growing past 1,000 production microservices. He covers regrets, sprawl and organizational effects.
Takeaways
- Autonomy at scale creates sprawl and duplication
- Standards and ownership need deliberate design
- Structure choices carry long-term organizational costs
Topics: Org design & scaling, Engineering & technical leadership
Related
- AWS re:Invent 2019: Optimizing Aerospace manufacturing operations & supply chain with AWS (MFG201) · AWS Events
- Building Software Systems At Google and Lessons Learned · Stanford
- Walt Disney's E.P.C.O.T. Film (1966) · The Original EPCOT
- AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301) · Amazon Web Services
- How We've Scaled Dropbox · Stanford
- Kellie Romack on ServiceNow's $355M AI Transformation | From 4 Days to 8 Seconds · CAIO AI Leadership Podcast
- Erlang Factory 2014 - That's 'Billion' with a 'B': Scaling to the Next Level at WhatsApp · Erlang Solutions
- Kellie Romack on how ServiceNow Generated $355M in AI Value | Technovation 1062 · Metis Strategy
- Rick Reed - WhatsApp: Half a billion unsuspecting FreeBSD users · iX
- Days to Seconds: Harnessing Confidential AI Agents with Kellie Romack · Opaque Systems, Inc.
- How Agentic AI Changes The Workplace — With Jacqui Canney and Kellie Romack · Alex Kantrowitz
- Stanford Seminar - The Soul of a New Machine: Rethinking the Computer · Stanford Online
