Uploaded byC4Media
Lessons Learned on Uber's Journey into Microservices
The document details Uber's transition from a monolithic architecture to microservices, highlighting challenges such as scalability, infrastructure readiness, and migration complexities. Key lessons learned include the importance of clear communication with consumers and maintaining interface consistency during the migration process. The resulting microservices architecture improved ownership, failure isolation, and operational efficiency.
More Related Content
Similar to Lessons Learned on Uber's Journey into Microservices
![[Annotated] QConSF 2018: Airbnb's Great Migration - From Monolith to Service-...](https://cdn.slidesharecdn.com/ss_thumbnails/qconsf18-airbnbsgreatmigration-frommonolithtoservice-orientedannotated-181110005137-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Lessons Learned on Uber's Journey into Microservices
- 1. Uber’s Journey into Microservices EmilyReinhold, Software Engineer, Uber JUNE 15, 2016
- 2. InfoQ.com: News &Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/ uber-darwin
- 3. Presented at QConNew York www.qconnewyork.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
- 4.
- 5.
- 6. Lines of Codeover Time 0K 75K 150K 225K 300K 2011 2012 2013 2014 2015 2016 Unique Authors over Time 0 150 300 450 600 2011 2012 2013 2014 2015 2016 Start of migration. Yay! API Trends
- 7. ‣“API” ‣Started January 2011 ‣Accessto core data models Fun Facts
- 8. Core Data Models UsersTrips Payments Products Cities Documents Exchange Rates Vehicles Promos The Uber Monolith
- 9.
- 10. Request Flow Matching Service haproxy APIbox nginx uWSGI process Postgres Downstream Services Third Parties API
- 11. ‣Minimal overhead forcross- domain features Benefits
- 12. “Cross Domain” Users TripsPayments Products Cities Documents Exchange Rates Vehicles Promos The Uber Monolith
- 13. ‣Minimal overhead forcross- domain features ‣Reuse code across domains ‣Broad, extensible interface Benefits
- 14. ‣Honks ‣Halloween 2014 ‣Postgresql MasterFailure Historic Outages Image courtesy of Anita Hart. Licensed under CC-BY-SA 2.0. https://flic.kr/p/8PG15b
- 15.
- 16. ‣Honks ‣Halloween 2014 ‣Postgresql MasterFailure ‣Kafka Outage Historic Outages
- 17.
- 18. ‣Deploy burden ‣Single PostgresMaster Technical Bottlenecks Image courtesy of Paul Schadler. Licensed under CC-BY 2.0. https://flic.kr/p/aDoGkP
- 19. ‣Rapid hiring ‣Slow testsuite ‣Toe stepping, merge conflicts Developability
- 20. ‣Growth of business ‣Growthof features ‣Growth of organization Scalability 3 Ways
- 21.
- 22.
- 23.
- 24. ‣Horizontally scalable ‣Improved onboarding ‣Clearownership Benefits
- 25.
- 26. ‣Horizontally scalable ‣Improved onboarding ‣Clearownership ‣Failure isolation Benefits
- 27. Granular Failures Old Way API client show Payments Promos Usertags Edge Service New Way Edge Service Payments Promos Users ?
- 28.
- 29.
- 30.
- 31. Data Migration 1. Developnew schema 2. Implement converter 3. Dual write 4. Backfill 6. Move read queries 5. Validation ? 7. Remove old writes
- 32. ‣Drastically changing tech stack ‣Infrastructurenot ready ‣ Understaffed ‣ Lacked tooling Limit Scope
- 33. Things Happen Image courtesyof Kim Scarborough. Licensed under CC-BY-SA 2.0. https://flic.kr/p/23HUAK
- 34. ‣Drastically changing tech stack ‣Infrastructurenot ready ‣ Understaffed ‣ Lacked tooling ‣Understanding timelines Limit Scope
- 35. ‣Monolith’s consumers directly impacted Aligningwith Consumers
- 36.
- 37. ‣Monolith’s consumers directlyimpacted ‣Importance of migrating not well communicated ‣Constant interruption Aligning with Consumers
- 38. ‣For service developersand migrating consumers ‣Tool to split up request Build Tools Initially
- 39. Request Splitter API Cities Currencies Users Trips Old Way requestingtrip info, with relationships on user, currency, city New Way API Cities Currencies Users Trips Tool requesting trip info, with relationships on user, currency, city request user request city request currency request trip
- 40. ‣For service developersand migrating consumers ‣Tool to split up request ‣Tool to validate new response ‣Tool to gain visibility into consumers Build Tools Initially
- 41. ‣Most difficult aspectof migration ‣Silently call new system Consumer Migration Tips
- 42.
- 43. ‣Most difficult aspectof migration ‣Silently call new system ‣Most successful migration kept interface the same Consumer Migration Tips
- 44. ‣Tendency to avoidchanges ‣Tackling core (User) directly required refactor Love your Monolith
- 45. ‣Likely to impactother teams ‣Teams shift focus Migration Blockers
- 46.
- 47. ‣Shared accomplishment ‣Relationships formed ‣Newunderstanding Collaboration
- 48. ‣New tech stack:more efficient ‣No more uWSGI! Hardware efficiency
- 49.
- 50.
- 51. ‣New tech stack:more efficient ‣No more uWSGI! ‣Calls asynchronous Hardware efficiency
- 52. ‣How our systemswork ‣Design for stability ‣Evenly spread ownership Deeper Understanding
- 53. First & LastName Email: emilyr@uber.com Engineering Blog: eng.uber.com Twitter: @UberEng Thank you
- 55. Watch the videowith slide synchronization on InfoQ.com! https://www.infoq.com/presentations/uber- darwin