Uber & microservice case

Studding Cases of Utilizing modern methods in big tech companies can be valuable and informative. This case is one the interesting ones in which Uber company’s engineers explain that how and when they migrated towards microservice architecture. In this case Uber’s engineers have taken a road to a style of microservice architecture which was named as “Domain-Oriented Microservice Architecture” by themselves.
Some parts of this story:

As a result, we adopted a microservice architecture. Ultimately our systems became more flexible, which allowed teams to be more autonomous.
🔘 System reliability. Overall system reliability goes up in a microservice architecture. A single service can go down (and be rolled back) without taking down the whole system.
🔘 Separation of concerns. Architecturally, microservice architectures force you to ask the question “why does this service exist?” more clearly defining the roles of different components.
🔘 Clear Ownership. It becomes much clearer who owned what code. Services are typically owned at the individual, team, or org level enabling faster growth.
🔘 Autonomous execution. Independent deployments + clearer lines of ownership unlock autonomous execution by various product and platform teams.
🔘 Developer Velocity. Teams can deploy their code independently, which enables them to execute at their own pace.

Source: https://eng.uber.com/microservice-architecture/

Leave a Reply

Your email address will not be published. Required fields are marked *