This video is about the Uber Microservices Architecture & explains how monolith architecture are transitioned into small microservices to maximize business value.
A monolith architecture is a unified model. It means it has all the pieces of the IT architecture tightly coupled, and each component needs to be present for the codes to be executed. For example, Uber had started its journey with a monolith architecture. It had all its functionalizes like payment, notification, passenger manager, driver management running in a single application. Meaning there were different APIs connecting to a monolithic architecture.
The Uber microservices architecture was distributed, but it was connected to a single server. So any slight change in one of the APIs, the whole application needed to be run. This architecture worked fine when the business operations were small. However, this was not efficient as Uber’s operations scaled up.
This is when Uber decided to refactor the whole monolith architecture. It moved to microservices. A microservices or microservices architecture consists of small individual deployable services for different operations. Each microservice focuses on a single business domain and is implemented independently.
Uber introduced an API Gate through which all the functionalizes like driver management, billing, trip management are connected as individually separate deployable units. So, if there is any change in driver management, only that particular microservices need to be deployed without impacting the rest of the system.
There are many advantages and disadvantages of monolith vs. microservices. One does not need to turn the entire business into microservices as some functions work best, even in the monolith. It depends on the scalability of a particular domain.
Read more about Microservice architecture
Check out some other case studies on Microservices