使用 Node.js 搭建一个 API 网关 #2042

MuYunyun · 2017-08-10T09:11:24Z

resolve #2006

jasonxia23 · 2017-08-10T11:49:00Z

认领校对~@sqrthree

linhe0x0 · 2017-08-10T11:49:05Z

@jasonxia23 好的呢 🍺

CACppuccino · 2017-08-10T14:07:00Z

@sqrthree 校对认领

linhe0x0 · 2017-08-10T14:07:03Z

@CACppuccino 妥妥哒 🍻

CACppuccino

总体上无问题，个别格式需要改正

CACppuccino · 2017-08-10T14:16:15Z

TODO/building-an-api-gateway-using-nodejs.md


-Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows **technology diversity** on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
+微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的**技术多样性**，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


JSON over HTTP REST => HTTP REST 上的 JSON

CACppuccino · 2017-08-10T14:22:27Z

TODO/building-an-api-gateway-using-nodejs.md


-Using different data serialization and protocols can be powerful in certain situations, but **clients** that want to consume our product may **have different requirements**. The problem can also occur in systems with homogeneous technology stack as consumers can vary from a desktop browser through mobile devices and gaming consoles to legacy systems. One client may expect XML format while the other one wants JSON. In many cases, you need to support both.
+在某些情况下使用不同的数据序列化和协议可能是强大的，但**要使用我们的产品的**客户**可能有不同的需求**。该问题也可能发生在具有同质技术栈的系统中，因为客户可以从桌面浏览器通过移动设备和游戏机到遗留系统。一个客户可能期望XML格式，而另一个客户可能希望JSON。在许多情况下，您需要同时支持它们。


一个客户可能期望XML格式 => 一个客户可能期望 XML 格式

JSON 空格

CACppuccino · 2017-08-10T14:30:59Z

TODO/building-an-api-gateway-using-nodejs.md


-As API Gateway provides functionality for client applications like browsers - it can be implemented and managed by the team who is responsible for the frontend application.
+由于 API Gateway 为客户端应用程序（如浏览器）提供了功能，它可以由负责开发前端应用程序的团队实施和管理。


API GATEWAY应该统一翻译为 API 网关，不再使用gateway

CACppuccino · 2017-08-10T14:32:28Z

TODO/building-an-api-gateway-using-nodejs.md


-![](https://image.slidesharecdn.com/qconpaved-170718200756/95/paved-paas-to-microservices-7-638.jpg?cb=1500408507)*Netflix's approach to handle different clients, [source](https://www.slideshare.net/yunongx/paved-paas-to-microservices)*
+![](https://image.slidesharecdn.com/qconpaved-170718200756/95/paved-paas-to-microservices-7-638.jpg?cb=1500408507) **Netflix处理不同客户端的方法 , [资源](https://www.slideshare.net/yunongx/paved-paas-to-microservices)**


中英文空格

CACppuccino · 2017-08-10T17:01:42Z

@MuYunyun @sqrthree 校对完毕

jasonxia23

译者文笔超好～校正完毕
@sqrthree @MuYunyun

jasonxia23 · 2017-08-10T11:55:30Z

TODO/building-an-api-gateway-using-nodejs.md


-Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows **technology diversity** on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
+微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的**技术多样性**，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


团队可以独立设计，开发和发布应用程序
=>
团队可以独立设计、开发和发布应用程序

jasonxia23 · 2017-08-10T11:58:20Z

TODO/building-an-api-gateway-using-nodejs.md


-Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows **technology diversity** on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
+微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的**技术多样性**，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


在技术挑战中使用最佳语言，数据库，协议和传输层
=>
在给定的技术难题中使用最佳语言、数据库、协议和传输层

最好用顿号；

challenge 可以理解为难题。

jasonxia23 · 2017-08-10T12:05:14Z

TODO/building-an-api-gateway-using-nodejs.md


-Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows **technology diversity** on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
+微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的**技术多样性**，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


JSON over HTTP REST
=>
基于 HTTP REST 的 JSON
使用 HTTP/2 上的
=>
使用基于 HTTP/2 的
保持一致，似乎也更通顺

jasonxia23 · 2017-08-10T12:09:17Z

TODO/building-an-api-gateway-using-nodejs.md


-Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows **technology diversity** on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
+微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的**技术多样性**，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


消息传递代理
=>
消息代理
https://zh.wikipedia.org/wiki/RabbitMQ

jasonxia23 · 2017-08-10T12:10:40Z

TODO/building-an-api-gateway-using-nodejs.md


-  Services in a microservices architecture share some common requirements regarding authentication and transportation when they need to be accessible by external clients. API Gateway s provide a **shared layer** to handle differences between service protocols and fulfills the requirements of specific clients like desktop browsers, mobile devices, and legacy systems.
+  外部客户端访问微服务架构中的服务时，服务端会对认证和传输有一些常见的要求。API 网关提供**共享层**来处理服务协议之间的差异，并满足特定客户端（如桌面浏览器，移动设备和旧系统）的要求。


旧系统
=>
遗留系统

这个地方感觉还是用老系统比较接近日常用语

jasonxia23 · 2017-08-11T05:15:07Z

TODO/building-an-api-gateway-using-nodejs.md


-To summarize: we don't want to implement our internal services in our microservices architecture in a way to support multiple clients and re-implement the same logic all over. This is where the **API Gateway** comes into the picture and provides a **shared layer** to handle differences between service protocols and fulfills the requirements of specific clients.
+总结：我们不想在我们的微服务架构中实现我们的内部服务，以支持多个客户端并可以重复使用相同的逻辑。这就是**API网关**出现的原因，其作为**共享层**来处理服务协议之间的差异并满足特定客户端的要求。


API网关
=>
API 网关

jasonxia23 · 2017-08-11T06:22:58Z

TODO/building-an-api-gateway-using-nodejs.md


-API Gateway is a type of service in a microservices architecture which provides a shared layer and API for clients to communicate with internal services. The API Gateway can **route requests**, transform protocols, **aggregate data** and **implement shared logic** like authentication and rate-limiters.
+API 网关是微服务架构中的一种服务，它为客户端提供共享层和 API ，以便与内部服务进行通信。API 网关可以进行**路由请求**，转换协议，**聚合数据**以及**实现共享逻辑**，如认证和速率限制器。


API ，
=＞
API，

jasonxia23 · 2017-08-11T06:28:55Z

TODO/building-an-api-gateway-using-nodejs.md


-Netflix successfully uses Node.js API Gateways with their Java backend to support a broad range of clients - to learn more about their approach read [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) article.
+Netflix 成功地使用 Node.js API 网关及其 Java 后端来支持广泛的客户端 - 了解更多关于它们的方法阅读 [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) 这篇文章


链接翻译出来是否更好～

jasonxia23 · 2017-08-11T06:43:18Z

TODO/building-an-api-gateway-using-nodejs.md


-# Node.js API Gateways
+# Node.js API网关


jasonxia23 · 2017-08-11T06:44:31Z

TODO/building-an-api-gateway-using-nodejs.md


-While you want to do simple things in your API Gateway like routing requests to specific services you can **use a reverse proxy** like nginx. But at some point, you may need to implement logic that's not supported in general proxies. In this case, you can **implement your own** API Gateway in Node.js.
+当您希望在 API 网关中执行简单的操作，比如将请求路由到特定服务，您可以使用像 nginx 这样的**反向代理**。但在某些时候，您可能需要实现一般代理不支持的逻辑。在这种情况下，您可以在 Node.js 中**实现自己的**API网关。


linhe0x0 · 2017-08-11T12:42:40Z

@MuYunyun 两位校对者都已经校对好了~ 可以来根据校对意见进行调整了哈 ┏ (゜ω゜)=☞

MuYunyun · 2017-08-12T10:34:47Z

@sqrthree 修改完毕

linhe0x0 · 2017-08-14T07:39:42Z

TODO/building-an-api-gateway-using-nodejs.md


-API Gateway is a type of service in a microservices architecture which provides a shared layer and API for clients to communicate with internal services. The API Gateway can **route requests**, transform protocols, **aggregate data** and **implement shared logic** like authentication and rate-limiters.
+API 网关是微服务架构中的一种服务，它为客户端提供共享层和 API，以便与内部服务进行通信。API 网关可以进行**路由请求**，转换协议，**聚合数据**以及**实现共享逻辑**，如认证和速率限制器。


『进行路由请求，转换协议，聚合数据以及实现共享逻辑』=>『进行路由请求、转换协议、聚合数据以及实现共享逻辑』

linhe0x0 · 2017-08-14T07:40:09Z

TODO/building-an-api-gateway-using-nodejs.md


-Our system can have one or multiple API Gateways, depending on the clients' requirements. For example, we can have a separate gateway for desktop browsers, mobile applications and public API(s) as well.
+我们的系统可以有一个或多个 API 网关，具体取决于客户的需求。例如，我们可以为桌面浏览器，移动应用程序和公共 API 提供单独的网关。


『桌面浏览器』后面应使用顿号。

linhe0x0 · 2017-08-14T07:40:31Z

TODO/building-an-api-gateway-using-nodejs.md


-![API Gateway](https://blog-assets.risingstack.com/2017/07/api-gateway-1.png)*API Gateway as an entry point to microservices*
+![API Gateway](https://blog-assets.risingstack.com/2017/07/api-gateway-1.png)**API 网关作为微服务的切入点**


图片和文字之间加一个空行吧。

linhe0x0 · 2017-08-14T07:40:56Z

TODO/building-an-api-gateway-using-nodejs.md


-Netflix successfully uses Node.js API Gateways with their Java backend to support a broad range of clients - to learn more about their approach read [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) article.
+Netflix 成功地使用 Node.js API 网关及其 Java 后端来支持广泛的客户端 - 了解更多关于它们的方法阅读 [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) 这篇文章
+![](https://image.slidesharecdn.com/qconpaved-170718200756/95/paved-paas-to-microservices-7-638.jpg?cb=1500408507) **Netflix 处理不同客户端的方法, [资源](https://www.slideshare.net/yunongx/paved-paas-to-microservices)**


同样需要一个空行。

MuYunyun · 2017-08-14T08:06:12Z

@sqrthree 修改完毕

MuYunyun · 2017-08-14T15:50:46Z

@sqrthree 这篇文章，我在segmentfault看到同文翻译了，好坑啊，这还能获取到积分吗？

linhe0x0 · 2017-08-15T04:17:30Z

没事，冲突常有。已经 merge 啦~ 快快麻溜发布到掘金专栏然后给我发下链接，方便及时添加积分哟。

MuYunyun · 2017-08-15T05:05:40Z

@sqrthree 已发到掘金，掘金链接

使用 Node.js 搭建一个 API 网关

dd8eb05

linhe0x0 added the 校对认领 label Aug 10, 2017

linhe0x0 mentioned this pull request Aug 10, 2017

使用 Node.js 搭建一个 API 网关 #2006

Closed

linhe0x0 added the 后端 label Aug 10, 2017

linhe0x0 added the 正在校对 label Aug 10, 2017

linhe0x0 removed the 校对认领 label Aug 10, 2017

CACppuccino approved these changes Aug 10, 2017

View reviewed changes

jasonxia23 reviewed Aug 11, 2017

View reviewed changes

MuYunyun added 2 commits August 12, 2017 18:24

使用 Node.js 搭建一个 API 网关

2eea8ba

使用 Node.js 搭建一个 API 网关

ca228a8

linhe0x0 requested changes Aug 14, 2017

View reviewed changes

使用 Node.js 搭建一个 API 网关

64ba119

linhe0x0 approved these changes Aug 15, 2017

View reviewed changes

linhe0x0 merged commit 5a4b152 into xitu:master Aug 15, 2017

linhe0x0 added 翻译完成 and removed 正在校对 labels Aug 15, 2017

MuYunyun deleted the translate branch August 25, 2017 03:51

cdadar pushed a commit to cdadar/gold-miner that referenced this pull request Dec 8, 2017

使用 Node.js 搭建一个 API 网关 (xitu#2042)

bcf5cb0

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

使用 Node.js 搭建一个 API 网关 #2042

使用 Node.js 搭建一个 API 网关 #2042

MuYunyun commented Aug 10, 2017 •

edited by linhe0x0

Loading

jasonxia23 commented Aug 10, 2017

linhe0x0 commented Aug 10, 2017

CACppuccino commented Aug 10, 2017

linhe0x0 commented Aug 10, 2017

CACppuccino left a comment

CACppuccino Aug 10, 2017

CACppuccino Aug 10, 2017

CACppuccino Aug 10, 2017

CACppuccino Aug 10, 2017

CACppuccino Aug 10, 2017

CACppuccino commented Aug 10, 2017

jasonxia23 left a comment

jasonxia23 Aug 10, 2017

jasonxia23 Aug 10, 2017

jasonxia23 Aug 10, 2017

jasonxia23 Aug 10, 2017

jasonxia23 Aug 10, 2017

MuYunyun Aug 12, 2017

jasonxia23 Aug 11, 2017

jasonxia23 Aug 11, 2017

jasonxia23 Aug 11, 2017

jasonxia23 Aug 11, 2017

jasonxia23 Aug 11, 2017

linhe0x0 commented Aug 11, 2017 •

edited

Loading

MuYunyun commented Aug 12, 2017

linhe0x0 Aug 14, 2017

linhe0x0 Aug 14, 2017

linhe0x0 Aug 14, 2017

linhe0x0 Aug 14, 2017

MuYunyun commented Aug 14, 2017

MuYunyun commented Aug 14, 2017

linhe0x0 commented Aug 15, 2017

MuYunyun commented Aug 15, 2017


		Microservices are a service oriented architecture where teams can design, develop and ship their applications independently. It allows technology diversity on various levels of the system, where teams can benefit from using the best language, database, protocol, and transportation layer for the given technical challenge. For example, one team can use JSON over HTTP REST while the other team can use gRPC over HTTP/2 or a messaging broker like RabbitMQ.
		微服务是面向服务的架构，团队可以独立设计，开发和发布应用程序。它允许在系统各个层面上的技术多样性，团队可以在技术挑战中使用最佳语言，数据库，协议和传输层，从而受益。例如，一个团队可以使用 JSON over HTTP REST，而另一个团队可以使用 HTTP/2 上的 gRPC 或 RabbitMQ 等消息传递代理。


		Using different data serialization and protocols can be powerful in certain situations, but clients that want to consume our product may have different requirements. The problem can also occur in systems with homogeneous technology stack as consumers can vary from a desktop browser through mobile devices and gaming consoles to legacy systems. One client may expect XML format while the other one wants JSON. In many cases, you need to support both.
		在某些情况下使用不同的数据序列化和协议可能是强大的，但要使用我们的产品的客户可能有不同的需求。该问题也可能发生在具有同质技术栈的系统中，因为客户可以从桌面浏览器通过移动设备和游戏机到遗留系统。一个客户可能期望XML格式，而另一个客户可能希望JSON。在许多情况下，您需要同时支持它们。


		As API Gateway provides functionality for client applications like browsers - it can be implemented and managed by the team who is responsible for the frontend application.
		由于 API Gateway 为客户端应用程序（如浏览器）提供了功能，它可以由负责开发前端应用程序的团队实施和管理。


		![](https://image.slidesharecdn.com/qconpaved-170718200756/95/paved-paas-to-microservices-7-638.jpg?cb=1500408507)Netflix's approach to handle different clients, [source](https://www.slideshare.net/yunongx/paved-paas-to-microservices)
		![](https://image.slidesharecdn.com/qconpaved-170718200756/95/paved-paas-to-microservices-7-638.jpg?cb=1500408507) Netflix处理不同客户端的方法 , [资源](https://www.slideshare.net/yunongx/paved-paas-to-microservices)


		Services in a microservices architecture share some common requirements regarding authentication and transportation when they need to be accessible by external clients. API Gateway s provide a shared layer to handle differences between service protocols and fulfills the requirements of specific clients like desktop browsers, mobile devices, and legacy systems.
		外部客户端访问微服务架构中的服务时，服务端会对认证和传输有一些常见的要求。API 网关提供共享层来处理服务协议之间的差异，并满足特定客户端（如桌面浏览器，移动设备和旧系统）的要求。


		To summarize: we don't want to implement our internal services in our microservices architecture in a way to support multiple clients and re-implement the same logic all over. This is where the API Gateway comes into the picture and provides a shared layer to handle differences between service protocols and fulfills the requirements of specific clients.
		总结：我们不想在我们的微服务架构中实现我们的内部服务，以支持多个客户端并可以重复使用相同的逻辑。这就是API网关出现的原因，其作为共享层来处理服务协议之间的差异并满足特定客户端的要求。


		API Gateway is a type of service in a microservices architecture which provides a shared layer and API for clients to communicate with internal services. The API Gateway can route requests, transform protocols, aggregate data and implement shared logic like authentication and rate-limiters.
		API 网关是微服务架构中的一种服务，它为客户端提供共享层和 API ，以便与内部服务进行通信。API 网关可以进行路由请求，转换协议，聚合数据以及实现共享逻辑，如认证和速率限制器。


		Netflix successfully uses Node.js API Gateways with their Java backend to support a broad range of clients - to learn more about their approach read [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) article.
		Netflix 成功地使用 Node.js API 网关及其 Java 后端来支持广泛的客户端 - 了解更多关于它们的方法阅读 [The "Paved Road" PaaS for Microservices at Netflix](https://www.infoq.com/news/2017/06/paved-paas-netflix) 这篇文章


		While you want to do simple things in your API Gateway like routing requests to specific services you can use a reverse proxy like nginx. But at some point, you may need to implement logic that's not supported in general proxies. In this case, you can implement your own API Gateway in Node.js.
		当您希望在 API 网关中执行简单的操作，比如将请求路由到特定服务，您可以使用像 nginx 这样的反向代理。但在某些时候，您可能需要实现一般代理不支持的逻辑。在这种情况下，您可以在 Node.js 中实现自己的API网关。


		API Gateway is a type of service in a microservices architecture which provides a shared layer and API for clients to communicate with internal services. The API Gateway can route requests, transform protocols, aggregate data and implement shared logic like authentication and rate-limiters.
		API 网关是微服务架构中的一种服务，它为客户端提供共享层和 API，以便与内部服务进行通信。API 网关可以进行路由请求，转换协议，聚合数据以及实现共享逻辑，如认证和速率限制器。


		Our system can have one or multiple API Gateways, depending on the clients' requirements. For example, we can have a separate gateway for desktop browsers, mobile applications and public API(s) as well.
		我们的系统可以有一个或多个 API 网关，具体取决于客户的需求。例如，我们可以为桌面浏览器，移动应用程序和公共 API 提供单独的网关。


		![API Gateway](https://blog-assets.risingstack.com/2017/07/api-gateway-1.png)API Gateway as an entry point to microservices
		![API Gateway](https://blog-assets.risingstack.com/2017/07/api-gateway-1.png)API 网关作为微服务的切入点

使用 Node.js 搭建一个 API 网关 #2042

使用 Node.js 搭建一个 API 网关 #2042

Conversation

MuYunyun commented Aug 10, 2017 • edited by linhe0x0 Loading

jasonxia23 commented Aug 10, 2017

linhe0x0 commented Aug 10, 2017

CACppuccino commented Aug 10, 2017

linhe0x0 commented Aug 10, 2017

CACppuccino left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

CACppuccino commented Aug 10, 2017

jasonxia23 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

linhe0x0 commented Aug 11, 2017 • edited Loading

MuYunyun commented Aug 12, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MuYunyun commented Aug 14, 2017

MuYunyun commented Aug 14, 2017

linhe0x0 commented Aug 15, 2017

MuYunyun commented Aug 15, 2017

MuYunyun commented Aug 10, 2017 •

edited by linhe0x0

Loading

linhe0x0 commented Aug 11, 2017 •

edited

Loading