SYSTEM Cited by 1 source
Uber Edge Gateway¶
Edge Gateway is Uber's 2020 mobile API gateway, built to replace RTAPI when it became technically obsolete (still Node.js + deprecated-in-Project-Ark JavaScript, ad-hoc view-generation and business-logic mixed in). By 2019 Uber had many lines of business (Uber Eats, Freight, ATG, Elevate) that each wanted their backend + app systems vertically independent — the gateway needed a clean architectural contract. (Source: sources/2024-03-14-highscalability-brief-history-of-scaling-uber)
Four-layer architecture —¶
| Layer | Role | Rule |
|---|---|---|
| Edge Layer | API lifecycle management | No extraneous logic; stays clean. |
| Presentation Layer | Microservices for view generation + data aggregation over many downstream services | Shapes responses for mobile clients. |
| Product Layer | Microservices providing functional, reusable APIs describing a product | Can be reused by other teams to compose new product experiences. |
| Domain Layer | Leaf-node microservices providing a single refined capability for a product team | Pure business primitive. |
This decoupling of concerns across four explicit tiers restructured Uber's 1000s of engineers' work without slowing product velocity — a microservices-era evolution of the BFF pattern, explicitly rejecting the RTAPI generation's ad hoc accretion.
Primary-source references:
- Uber's new gateway architecture (Edge Gateway launch)
- API gateway: the evolution of Uber's API gateway
- Microservice architecture: service "domains"
Seen in¶
- sources/2024-03-14-highscalability-brief-history-of-scaling-uber — introduced as the 2020 gateway rebuild after 2018 Project Ark made the new architectural-layering language explicit.
Related¶
- systems/uber-rtapi-gateway — predecessor.
- companies/uber — origin org.
- patterns/layered-gateway-architecture — the canonical pattern this system instantiates.