How Uber Broke a Monolithic API into Microservices

In the last few months, Uberhas invested thousands of engineering hours in expanding their new microservices ecosystem after abandoning its monolithic codebase. In a recent poston Uber Engineering, Emily Reinhold explains a few key design and architectural decisions that have helped to rewrite Uber engineering as a modular and flexible microservices architecture.

One design decision was adopting MVCS to separate the persistence specifics from the application logic. This pattern is an extension of the common MVC with an additional Service layer where the business logic lives.

Be sure to read the next Microservices article: What's the Difference Between a Monolith and Microservices?

Original Article

Rewriting Uber Engineering: The Opportunities Microservices Provide

 

Comments