Download as PDF, PPTX
Uploaded byNikolay Stoitsev
Evolving big microservice architectures
The document discusses evolving microservice architectures at Uber. It describes Uber's transition from a monolithic architecture to over 4,000 microservices with over 1,000 deploys per day. Key challenges discussed include testing changes, integrating services, handling multiple environments, and establishing common platforms and data models to support new use cases and services. The presentation emphasizes establishing layered, abstracted architectures with clear separations of concerns to facilitate engineering velocity at scale.
More Related Content
Similar to Evolving big microservice architectures
Evolving big microservice architectures
- 1. Evolving big microservice architectures Nikolay Stoitsev,Engineering Manager @ Uber Engineering
- 4.
- 5. A monolith? Code was consistentlygood Easy to reuse code Well tested Hard to deploy
- 6. Pull Request Pull Request PullRequest Pull Request Pull Request ? ? ? ? ?
- 7. Pull Request Pull Request PullRequest Pull Request Pull Request ? ? ? ? ? Unknown risk Unknown priority
- 8. Low Risk High Risk HighRisk Med Risk High Risk Build
- 9. Low Risk High Risk HighRisk Med Risk High Risk Build ?
- 10. Low Risk High Risk HighRisk Med Risk High Risk Build
- 11. Low Risk /P0 High Risk / P1 High Risk / P0 Med Risk / P3 High Risk / P0 Build
- 12. Low Risk /P0 High Risk / P1 High Risk / P0 Med Risk / P3 High Risk / P0 Build CI / CD
- 13. Gradual rollout isimportant
- 14. Lesson learned: A monolithcan scale a lot, but...
- 15.
- 16.
- 17.
- 18.
- 19.
- 21. 4000+ microservices 1K+ avgdeploys a day
- 22.
- 23. We want tointroduce Uber Elevate
- 24.
- 25.
- 26.
- 27.
- 28. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Apache Kafka Apache Kafka Apache Kafka
- 29. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Task #4 Apache Kafka Apache Kafka Apache Kafka
- 30. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Task #4 Task #5Apache Kafka Apache Kafka Apache Kafka
- 31. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Task #4 Task #5 OKApache Kafka Apache Kafka Apache Kafka
- 32. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Task #4 Task #5 OK Task #6 Apache Kafka Apache Kafka Apache Kafka
- 33. How do weevolve big microservice architectures?
- 34. You can’t changewhat you can’t test
- 35.
- 36.
- 37.
- 38.
- 39.
- 40. Tenancy - setof data that is isolated from the other sets of data
- 41.
- 42. Testing tenancy vs.Production tenancy
- 43.
- 44.
- 45.
- 46. Dispatch Pricing Services Tax Calc Vehicles Trips Services Users Payments Services Receipts Task #1 OK Task #2 Task#3 Task #4 Task #5 OKApache Kafka Apache Kafka Apache Kafka
- 47.
- 48. Services are tooconcrete so it’s hard to support new use cases
- 49. Services need tosupport abstraction
- 50. AWS is agood example
- 51.
- 52.
- 53.
- 54.
- 55. Hard shift inmentality in the way you design your services
- 56. Can you sellit outside of the company?
- 57. Tax Calc PaymentsPricing
- 58. Tax Calc PaymentsPricing 3.14159
- 59. Tax Calc PaymentsPricing 3.14159 “3.14”
- 60. Tax Calc PaymentsPricing 3.14159 “3.14” 314159
- 61.
- 64. Data extensions =schema + payload
- 65. How to doit? Schema service Repo Library ...
- 66.
- 67. … but thereis still business specific logic.
- 68. Dispatch Pricing Services Tax Calc Vehicles Orders Platform Users Payments Services Receipts Where to putit? Business logic Apache Kafka Apache Kafka Apache Kafka
- 69. No common understanding ofwhat should go where
- 70. How do wecall code with business logic, presentation logic, and SQL queries all over the place?
- 71. We fix spaghetticode with separation of concerns
- 72.
- 73.
- 74. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend
- 75.
- 76.
- 77. Clear separation ofconcerns
- 78.
- 79. API and functionalitydiscoverability
- 80.
- 81. Users Vehicles Order Platform Pricing Tax Calc Payments Receipts RidesElevate Web Services Mobile Backend Generic Specific
- 82. Users Vehicles Order Platform Pricing Tax Calc Payments Receipts RidesElevate Web Services Mobile Backend Breaks everything Breaks specific thing
- 83. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile BackendPresentation LoB Biz Infra Core
- 84. https://philcalcado.com/2018/09/24/services_layers.html Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend Clay Rocks
- 85. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile BackendPresentation
- 86. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend LoB
- 87. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend Biz Infra
- 88. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend Core
- 89.
- 90.
- 91. End result: Layeredmultitenant architecture built with abstract platforms and a common data model
- 92. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Web Services Mobile Backend
- 93. Users Vehicles Order Platform Pricing TaxCalc Payments Receipts Rides Elevate Web Services Mobile Backend
- 94.
- 95. Proprietary © 2019Uber Technologies, Inc. All rights reserved. No part of this document may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval systems, without permission in writing from Uber. This document is intended only for the use of the individual or entity to whom it is addressed and contains information that is privileged, confidential or otherwise exempt from disclosure under applicable law. All recipients of this document are notified that the information contained herein includes proprietary and confidential information of Uber, and recipient may not make use of, disseminate, or in any way disclose this document or any of the enclosed information to any person other than employees of addressee to the extent necessary for consultations with authorized personnel of Uber.