How Uber’s Domain‑Oriented Microservice Architecture Reduces Complexity

What Is a Microservice

Microservices are an evolution of service‑oriented architecture, representing small, independently deployable functions exposed via well‑defined network interfaces. They enable independent deployment, clearer ownership, and improved system stability, but can increase overall system complexity.

Motivation

Uber adopted microservices around 2012‑2013 to address availability risk, deployment risk, and poor separation of concerns in monolithic codebases. As the engineering organization grew, microservices provided flexibility, reliability, clearer ownership, and faster development, though they also introduced complexity and coordination challenges.

Domain‑Oriented Microservice Architecture (DOMA)

DOMA structures microservices into domains (collections of related services), groups domains into layers (defining allowed dependencies), and exposes each domain through a single gateway . It also defines extensions —logical and data extensions—that allow functionality to be added without modifying core services.

Domain: a set of microservices that share a logical function.

Layer: a hierarchy that limits which services may call others, reducing impact radius.

Gateway: a single entry point for a domain, analogous to an API gateway.

Extension: mechanisms (logical or data) to augment domain functionality without changing core code.

By applying established design principles such as domain‑driven design and clean architecture, DOMA turns a complex microservice landscape into a structured, reusable set of components.

Benefits

DOMA has improved reliability, reduced integration points (cutting onboarding time by 25‑50%), and lowered platform costs. Uber has partitioned roughly 2,200 microservices into about 70 domains, with half already implemented. The architecture also eases migration by isolating changes behind gateways.

Practical Advice

For startups, the operational benefits of microservices may not outweigh added complexity; delaying adoption can be sensible. Mid‑size companies should begin introducing hierarchical layers and extensions to manage growing dependencies. Large organizations benefit most from full DOMA adoption, using domains, layers, and gateways to manage hundreds of services and support platform evolution.

Future Migration

Microservice half‑life at Uber is ~1.5 years, making migration challenging without gateways. Gateways decouple downstream changes from upstream consumers, preventing “migration hell.” Future platform rewrites will continue to rely on gateways to minimize disruption.

Final Thoughts

DOMA treats a microservice system as a large distributed program, applying familiar software‑engineering principles to its evolution. Uber continues to refine DOMA and hopes other organizations find the approach useful.