这是用户在 2024-7-22 11:36 为 https://www.uber.com/en-KR/blog/microservice-architecture/ 保存的双语快照页面,由 沉浸式翻译 提供双语支持。了解如何保存?
Skip to main content
Engineering

Introducing Domain-Oriented Microservice Architecture

July 23, 2020 / Global
Featured image for Introducing Domain-Oriented Microservice Architecture
Uber’s microservice architecture circa mid-2018 from Jaeger
Jaeger 于 2018 年中期发布的 Uber 微服务架构
An example of a complex flow at Uber circa 2018, which required 10 touch points for a simple integration before DOMA.
2018 年左右 Uber 的复杂流程示例,在 DOMA 之前需要 10 个接触点才能进行简单集成。
The following figure illustrates the high level diagram of a gateway. It abstracts away the internal details of the domains – multiple services, data tables, ETL pipelines etc. Only the interfaces – RPC APIs, messaging events and queries are exposed to other domains.
下图展示了网关的高级图。它抽象了域的内部细节 - 多个服务、数据表、ETL 管道等。只有接口 - RPC API、消息传递事件和查询暴露给其他域。
Adam Gluck

Adam Gluck 亚当·格鲁克

Adam Gluck is a Sr. Software Engineer II at Uber. He spent his first 3.5 years at Uber fleshing out our Driver Platform team and helping to scale our driver product.
Adam Gluck 是 Uber 的高级二级软件工程师。他在 Uber 工作的头 3.5 年充实了我们的司机平台团队,并帮助扩展了我们的司机产品。

More recently, he’s been a part of Uber’s engineering strategy team, focused on high level system architecture and Uber-wide platformization efforts.
最近,他成为 Uber 工程战略团队的一员,专注于高级系统架构和 Uber 范围内的平台化工作。

Posted by Adam Gluck  亚当·格鲁克发表

Category: 类别:

Related articles 相关文章

Select your preferred language
English
对比 (0/20)
全部清除
对比 (0/20)
全部清除