This is an automated email from the ASF dual-hosted git repository.
juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 95aef9d docs: add translation for Hyperchain user case (#748)
95aef9d is described below
commit 95aef9de668e19301e15fb3cae7c57695738583a
Author: yilinzeng <[email protected]>
AuthorDate: Tue Nov 16 17:53:34 2021 +0800
docs: add translation for Hyperchain user case (#748)
---
.../blog/2021/08/09/Apache-APISIX-in-Quliankeji.md | 209 +++++++++++----------
.../2021/08/09/Apache-APISIX-in-Quliankeji.md | 2 +-
2 files changed, 107 insertions(+), 104 deletions(-)
diff --git a/website/blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
b/website/blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
index 2f50219..80308e8 100644
--- a/website/blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
+++ b/website/blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
@@ -1,214 +1,217 @@
---
-title: "舍弃 Kong 和 Nginx，Apache APISIX 在趣链科技 BaaS 平台的落地实践"
-author: "盛威锋"
+title: "Abandoning Kong and Nginx, Hyperchain Technology implements on its
BaaS platform"
+author: "Weifeng Sheng"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
+- Hyperchain
- BaaS
-description: 本文介绍了 Apache APISIX 在趣链科技 BaaS 平台中的落地实践情况，以及趣链科技在众多网关应用中选择
Apache APISIX 的原因。
+description: This article introduces the landing practice of Apache APISIX in
Hyperchain Blockchain BaaS platform, and explains why Hyperchain Technology has
chosen Apache APISIX among many gateway applications.
tags: [User Case]
---
-> 本文介绍了 Apache APISIX 在趣链科技 BaaS 平台中的落地实践情况，以及趣链科技在众多网关应用中选择 Apache APISIX 的原因。
+> This article introduces the landing practice of Apache APISIX in Hyperchain
Blockchain BaaS platform, and explains why Hyperchain Technology has chosen
Apache APISIX among many gateway applications.
<!--truncate-->
-## 业务背景
+## Background Information
-BaaS（Blockchain as a
Service），中文为“区块链即服务”，是指将区块链框架嵌入云计算平台，利用云服务基础设施的部署和管理优势，为开发者提供便捷、高性能的区块链生态环境和生态配套服务，支持开发者的业务拓展及运营支持的区块链开放平台。
+BaaS, which is also known as “Blockchain as a Service”, is an open platform
that embeds blockchain framework into cloud computing platform and provides
convenient and high performance blockchain ecological environment and
ecological support services for developers by taking advantage of the
deployment and management of cloud service infrastructure to support their
business expansion and operation. It is an open blockchain platform that
supports developers’ business expansion and operatio [...]
-通常情况下，一套完整的 BaaS 解决方案包括设备接入、访问控制、服务监控和区块链平台四个主要环节。
+Typically, a complete BaaS solution includes four main components: device
access, access control, service monitoring and blockchain platform.
-**通过 BaaS 可以快速灵活地搭建区块链网络，对于企业来说，有了 BaaS 平台就能够对区块链业务进行统一的管理。**
+**We can build blockchain network quickly and flexibly through BaaS. For
enterprises, with BaaS platform, we can manage blockchain business in a unified
way.**
-相信有不少朋友接触过以太坊上面的合约代码，通过 BaaS 平台，我们能够很轻松地在 IDE
上编写智能合约，然后把它部署到我们的创建出来的区块链网络上，最后供上层的服务调用区块链相关的合约来进行业务的流转。
+I believe that many of you have come across the contract code on top of
Ethernet. Through BaaS platform, we can easily write smart contracts on the IDE
and then deploy it to our created blockchain network, and finally for the upper
layer services to call the blockchain-related contracts to carry out the flow
of business.
-因为链的节点非常多，少则几十个，多则上千个，如果没有 BaaS 平台的支持，我们很难监控和维护链的运行。通过使用 BaaS
平台，用户不仅能够节约成本，而且可以更加便捷地管理区块链，提升整个系统的安全系数。
+Because the chain has so many nodes, from tens to thousands, it is difficult
to monitor and maintain the operation of the chain without the support of BaaS
platform. By using BaaS platform, users can not only save cost, but also manage
the blockchain more conveniently and the security of the whole system is higher.
-趣链科技 BaaS 产品的架构总共分为四层，分别为资源层、区块链底层、区块链服务层和应用层。
+The architecture of BaaS product of Hyperchain Technology is divided into four
layers in total, which are resource layer, blockchain underlying layer,
blockchain service layer and application layer.
-
+
-现在我们对 Baas 平台有了初步的了解，下面我们来看看 Apache APISIX 在 BaaS 系统上的使用场景与收获。
+Now that we have a preliminary understanding of Baas platform, let’s take a
look at the usage scenarios and gains of Apache APISIX on BaaS system.
-## Apache APISIX 的使用场景
+## Apache APISIX Usage Scenarios and Gains
-### 场景 1：在 BaaS 系统上的落地实践
+### Scenario 1: Practice on BaaS system
-
+
-从这张图中可以看到，趣链科技 BaaS 平台的架构不仅是微服务化的，而且分为两层，分别是业务接入层和核心服务层。
+The architecture of Hyperchain’s BaaS platform is not only
microservices-based, but also divided into two layers, which are business
access layer and core service layer.
-BFF（Backend For Frontend） 一般对着前端，通过 HTTP 接入。核心服务一般是通过类似 Dubbo、ETCD 等服务注册，最后使用
gRPC 来访问。
+BFF (Backend For Frontend) is generally to the frontend, through HTTP access.
The core services are generally registered through services like Dubbo, ETCD,
etc., and finally accessed using gRPC.
-也就是说，趣链科技的 BaaS 平台前端连接的都是 BFF 模块，然后 BFF 模块再去连接后面的微服务模块。BFF
的作用主要就是做业务聚合、格式适配，并把最终的结果数据给到前端。
+The role of BFF is to do business aggregation, format adaptation, and give the
final result data to the frontend.
-这些业务模块需要把相关信息存到注册中心（ETCD），当要使用的时候，再通过网关模块把信息读取出来。
+These business modules need to store the relevant information in the registry
(ETCD), and then read out the information through the gateway module when it is
used.
-
+
-在整个流程中，我们主要用到了 Apache APISIX 的四个特性：
+In the whole process, we mainly use four features of Apache APISIX.
-- 路由转发
-- 流量控制
-- 安全控制
-- 动态加载
+- Routing and Forwarding
+- Traffic Control
+- Security and Access Control
+- Dynamic Loading
-我们下面再来了解下这些特性在趣链 BaaS 系统上是如何使用的。
+Let’s learn more about how these features are used on the Hyperchain BaaS
system below.
-#### 路由转发
+#### Routing and Forwarding
-
+
-趣链科技使用 Apache APISIX 官方提供的 Proxy-rewrite 插件执行路由转发服务。
+Hyperchain uses the official Proxy-rewrite plugin provided by Apache APISIX to
perform route forwarding services.
-当一个请求访问 8080 端口，通过 Proxy-rewrite 插件，请求会被转发到对应服务的 API 上去。
+When a request accesses port 8080, through the Proxy-rewrite plugin, the
request will be accessed to the API of the corresponding service.
-
+
-上图为 Proxy-rewrite 的操作界面，我们可以看到可以通过正则匹配来匹配自己的转发规则，当然也可以通过写 HOST 或者通过 URL 来匹配。
+The above figure shows the interface of Proxy-rewrite, we can see that you can
match your own forwarding rules by regular matching, of course, you can also
write HOST or by URL to match.
-#### 限流管理
+#### Traffic Control
-
+Before Apache APISIX, the platform needed to write its own logic code. With
Apache APISIX, we can directly use the officially provided Limit-req plugin to
limit the input and output for the purpose of protecting the system.
-在趣链 BaaS 平台中，客户可以根据自己的需要构建任何链。此时，BaaS 平台需要快速地支持创建这些链，并对它们进行生命周期管理。
+Through the interface of the Limit-req plugin, we can easily configure
parameters such as speed, bucket height, etc.
-这些联盟链的创建，并不是通过硬代码直接写在代码上，而是通过驱动组件来解决的。在私有化场景中，我们需要有这样驱动组件来快速地提供支持，并需要控制驱动进程的访问频率。
+
-
+In the Hyperchain BaaS platform, customers can build any chains according to
their needs. At this point, the BaaS platform needs to quickly support the
creation of these chains and manage their lifecycle.
-在没有 Apache APISIX 之前，平台需要自己写逻辑代码，有 Apache APISIX 以后，我们可以直接使用官方提供的 Limit-req
插件来限制输入输出，以达到保护系统的目的。通过 Limit-req 插件的操作界面，我们可以很方便地配置速度、桶高等参数。
+The creation of these federated chains is not solved by hard code written
directly on the code, but by driver components. In a privatization scenario, we
need to have such driver components to provide support quickly and need to
control the frequency of access to the driver processes.
-
+
-#### 安全控制、权限管理
+Before Apache APISIX, the platform needed to write its own logic code. With
Apache APISIX, we can directly use the officially provided Limit-req plugin to
limit the input and output for the purpose of protecting the system. Through
the interface of the Limit-req plugin, we can easily configure parameters such
as speed, bucket height, etc.
-
+
-在趣链科技的私有化场景，有不少用户不喜欢用平台所提供的账号体系，要求平台对接他们现有的账户系统，所以趣链科技使用了 Apache APISIX 的
Access-Auth 插件来适配第三方的鉴权服务地址。
+#### Security and Access Control
-
+
-在趣链科技的 Baas 平台中，所有的 Web 请求都会经过 Apache APISIX 的 Access-Auth 插件，完成 cookie
解析和鉴权，然后在 HEAD 头中携带用户信息，传给后端的微服务来处理业务。这样做的好处是，微服务的开发者不需要去解析
Cookie，而是可以直接把用户信息发送到微服务模块，非常方便。
+In Hyperchain’s privatization scenario, many users don’t like to use the
account system provided by the platform and ask the platform to connect to
their existing account system, so Hyperchain uses Apache APISIX’s Access-Auth
plugin to adapt the third-party authentication service address with it.
-#### 动态加载
+
-
+In Baas platform, all web requests will go through Apache APISIX’s Access-Auth
plugin, complete cookie parsing and authentication, then carry user information
in HEAD header and pass to back-end microservices to process business. The
advantage of this is that the developer of the microservice does not need to
parse the cookie, but can send the user information to the microservice module
directly, which is very convenient.
-上图左边是趣链科技 Baas 平台的客户端界面，上面没有 “商店” 的按钮；但在上图的右边，趣链科技的 Baas 公共平台上却有一个 “商店”
的按钮。在某些私有化场景中不需要 “商店” 按钮，但二者的后台服务是共享的，只要后端服务一启动，平台界面就会根据需求进行不同的显示。
+#### Dynamic Loading
-趣链科技利用 Apache APISIX 与服务中心协同运作，保证前端微服务业务模块的新增和调整，这让趣链科技 Baas 平台的线上发布流程变得非常简单。
+
-### 场景 2：在区块链节点上的落地实践
+The client interface of Baas platform of Hyperchain does not have a “store”
button on top; however, there is a “store” button on the public platform of
Baas of Hyperchain. In some privatization scenarios, the “store” button is not
needed, but the backend services of both are shared, and the platform interface
will be displayed differently according to the demand as soon as the backend
services are started.
-
+Hyperchain uses Apache APISIX to operate in collaboration with the service
center to ensure the addition and adjustment of front-end microservice business
modules, which makes the online publishing process of Hyperchain’s Baas
platform very easy.
-通过上图可以看到有 A、B、C 三条链，这三条链是怎么创建出来的呢？
+### Scenario 2: Practice on blockchain nodes
-当用户通过 BaaS
平台购买了一条链，它的上层业务或开发者客户端就可以直连节点，比如某银行连左三个，某保险连右三个，或者有的用户就访问一整条链。这样会带来一个很大的问题，因为基本上每个节点都会被访问到，所以我们需要在公网环境上把所有的区块链上的节点全部都暴露出来。
+
-#### 节约公网端口
+When a user buys a chain through the BaaS platform, its upper business or
developer client connects directly to the nodes, for example, a bank connects
to three on the left, an insurance connects to three on the right, or some
users access a whole chain. This will bring a big problem because basically
every node will be accessed, so we need to expose all the nodes on the
blockchain to the public network environment.
-
+#### Conserve public network ports
-以这张图为例，我们可以看到 6 个节点，那这条链就至少需要有 6 个公网 IP 和 6 个端口。
+
-这种情况对私有化的用户来说可能还可以接受，但是对于像趣链这样全部对互联网用户开放的 BaaS 平台，少则需要几十个，多则需要上百个、上千个公网
IP。这样不仅成本非常高，也对公网 IP 资源造成了浪费。
+This situation may be acceptable for private users, but for a BaaS platform
like Hyperchain, which is open to all Internet users, it requires dozens or
hundreds or thousands of public IPs, which is not only very costly but also a
waste of public IP resources.
-为了解决这个问题，趣链科技的 Baas 平台使用了 Apache APISIX 统一对外提供服务，无需联盟链全量节点暴露外网访问端口，可以有效节约成本。
+In order to solve this problem, Hyperchain’s Baas platform uses Apache APISIX.
-#### 访问权限控制
+#### Access Control
-
+
-对于传统软件来说，因为不同的异构链访问都有自己非常复杂的 RBAC 权限控制，所以用户需要在客户端加很多证书，非常令人头疼。
+Unlike traditional software, different heterogeneous chains have their own
very complicated RBAC permission control, so users need to add many
certificates on the client side, which is a great headache.
-为了解决这个痛点，趣链科技 BaaS 平台通过 Apache APISIX 的 Key-auth 插件让有权限的用户直接能够访问，并且统一所有链的权限控制。
+In order to solve this pain point, Baas platform of Hyperchain Technology uses
Apache APISIX’s Key-auth plugin to allow users with permission to access
directly and unify the permission control of all chains.
-#### 集群化提升节点稳定性
+#### Improved node stability
-
+
-区块链的一个特性是：本质上，访问任何一个节点都是一样的。就像比特币一样，我们访问任何一个节点都能拿到数据，所以很多用户直接对着某个节点进行操作。
+One of the properties of blockchain is that, essentially, accessing any node
is the same.
-
+Just like Bitcoin, we access any node to get the data, so many users operate
directly against a node.
-但是，直接访问单节点的模式很容易受到攻击。比如说，银行的并发量非常高，TPS 可以达到 4-5W/秒，每一次交易都会冲击这个节点。
+
-为了能够达到快速动态扩容的效果，趣链科技 BaaS 平台利用 Apache APISIX 在 Kubernetes 上的 HPA
部署模式，根据流量动态地扩展，有效解决了单点流量冲击问题。
+However, the direct access to a single node model is vulnerable to attacks.
For example, banks have a very high concurrency, TPS can reach 4–5W/sec, and
every transaction will hit this node.
-#### 多协议支持
+In order to achieve the effect of fast dynamic scaling, Hyperchain’s Baas
platform utilizes Apache APISIX HPA deployment model on Kubernetes to
dynamically scale according to the traffic, effectively solving the
single-point traffic impact problem.
-
+#### Multi-protocol support
-趣链科技 BaaS 平台使用了很多的异构链，这导致使用到的协议非常多样，如 HTTP、RPC、WebSocket 等。而 Apache APISIX
能很好地支持多协议，完全能满足趣链科技 BaaS 平台在相关场景中的使用，能显著减少开发的成本。
+
-
-ng)
+Because Hyperchain’s Baas platform uses a lot of heterogeneous chains, the
protocols used are very diverse, such as HTTP, RPC, WebSocket and so on. Apache
APISIX supports multi-protocols very well, which can fully meet the use of Baas
platform in the relevant scenarios, which significantly reduces the development
cost.
-## 为什么选择 Apache APISIX
+
-在 Apache APISIX 之前，趣链科技 BaaS 平台已经在使用 Kong 了，但是后来 Kong 被放弃了。
+## What were the kinks we went through before choosing Apache APISIX?
-**为什么放弃 Kong？**
+Before choosing Apache APISIX, Hyperchain’s Baas platform was already using
Kong, but Kong was later abandoned.
-Kong 使用 PostgreSQL 来存储它的信息，这显然不是一个好方式。
+**Why did we give up on Kong?**
+
+Kong uses PostgreSQL to store its information, which is obviously not a good
way to do it.
-在软件行业，数据库的高可用配置非常复杂。不仅需要配备专门的 DBA，实施难度也非常大。
+In the software industry, high availability configuration of databases is very
complex. Not only do you need to have a dedicated DBA, but the implementation
is also very difficult.
-趣链科技 BaaS 系统本身已经在使用 MySQL，如果这里还需要搭建一个 PostgreSQL 数据库的话，意味着趣链科技的 BaaS
系统需要有两套关系型数据库。这会给实施难度、运维成本带来更多麻烦，引入更多风险。
+The Baas system of Hyperchain Technology is already using MySQL, if we need to
build a PostgreSQL database here, it means that Hyperchain Technology’s Baas
system needs to have two sets of relational databases. This brings problems to
the implementation difficulty and operation and maintenance cost, and
introduces more risks.
-同时，因为趣链科技 BaaS 平台也有不少地方用到了 etcd，所以最后趣链科技选择放弃 Kong，全面投向了基于 etcd 的 Apache APISIX。
+At the same time, because ETCD is also used in many places of Hyperchain’s
Baas platform, finally, Hyperchain abandoned Kong and invested in Apache APISIX
which is based on ETCD.
-**为什么不使用 Nginx？**
+**Why did we give up on Nginx?**
-可能会有朋友会想，那为什么不使用 Nginx？
+Some of you may think, “Why not use Nginx?
-其实趣链科技 BaaS 平台以前用的就是 Nginx，但是后来发现，Nginx 与 Apache APISIX 相比还是有很多不完善的地方。
+Yes, Hyperchain’s BaaS platform used to use Nginx, but later we found that
Nginx has many imperfections compared to Apache APISIX.
-- **热启动、热插件问题**
+- **Issues on hot starts and hot plugins**
+
+In the Hyperchain BaaS platform, we not only need to manage the federated
chain, but also need to be able to add and delete nodes at any time.
-在趣链 BaaS 平台中，我们不仅需要对联盟链进行管理，而且要能够随时对节点进行新增、删除。如果使用
Nginx，不仅存在扩展性问题，调整配置后还需要重启。而且在插件的编写上，Nginx 上需要配置非常复杂的规则代码。
+- **Clustering difficulties**
-- **集群化困难**
+While Nginx is very difficult to cluster, Apache APISIX can be implemented
with ETCD clustering enhancements.
-Nginx 的集群化非常困难，而 Apache APISIX 可以通过 etcd 集群的增强功能来实现。
+- **Unable to proxy TCP and UDP directly**
-- **无法直接代理 TCP、UDP**
+By default, Nginx can only implement proxies for Layer 7 networks. To support
Layer 4 networks, you need to recompile the Stream module, while Apache APISIX
can support both Layer 4/7 proxies.
-Nginx 在默认情况下只能实现七层网络的代理，如果要支持四层网络，需要把 Stream 模块重新编译，而 Apache APISIX 能同时支持四 /
七层的代理。
+- **Lack of Dashboard**
-- **没有良好的 Dashboard**
+Nginx does not have a Dashboard, and the Apache APISIX Dashboard makes it less
difficult for development and operations staff to manage nodes.
-Nginx 没有 Dashboard，而 Apache APISIX Dashboard 能让开发、运维人员对于管理节点的难度变小。
+## Future Plans
-## 未来规划
+
-
+### Plan 1: Use Apache APISIX provided or self-developed logging plugins
-### 1.运用 Apache APISIX 提供或自研的日志插件
+The official website of Apache APISIX already provides a lot of logging
plugins, such as HTTP and UDP support, including kafka, etc. However, for a
platform like Hyperchain BaaS, which needs to control thousands of blockchain
networks, it is a big headache to search for fault traces in the logs when
every problem occurs.
-Apache APISIX 官网已提供了不少日志插件，比如对 HTTP、UDP 的支持，包括 Kafka 等，但像趣链 BaaS
这样需要管控成千上万区块链网络的平台，当每次问题发生的时候，在日志中翻找故障痕迹都是一件非常头痛的事情。
+In the near future, Hyperchain will add some APM functions between BaaS system
and blockchain system based on Apache APISIX. Improve the efficiency of
operation and maintenance management in multi-chain scenarios.
-在不久的将来，趣链科技会在 BaaS 系统和区块链系统之间，基于 Apache APISIX 增加一些 APM 功能，提升多链场景下的运维管理效率。
+### Plan 2: Development of monitoring plugins to achieve traceability
-### 2.开发监管插件，实现操作留痕及溯源
+Domestic regulation of blockchain is very strict, and all operations need to
be traceable and traceable.
-国内对于区块链的监管非常严格，一切操作都需要留痕和溯源。未来，趣链科技会基于 Apache APISIX 开发监管插件来提升监管能力，增加
VIP、白名单、回放等功能。
+In the future, Hyperchain Technology will develop regulatory plugins based on
Apache APISIX to improve the regulatory capability and add VIP, whitelist,
replay and other functions.
-### 3.使用 APISIX Ingress Controller，代替 Kubernetes 默认的 Nginx-Ingress
+### Plan 3: Use APISIX Ingress Controller instead of Kubernetes’ default
Nginx-Ingress
-在部署 Kubernetes 的时候，我们一般都会选择 Nginx-Ingress 来处理外网请求，但因为上面提到的一些 Nginx
的问题，趣链科技正在调研使用 APISIX Ingress Controller。
+When deploying Kubernetes, we usually choose Nginx-Ingress to handle outbound
requests, but because of some of the Nginx issues mentioned above, Hyperchain
is investigating using APISIX Ingress Controller.
-### 4.探索 Service Mesh
+### Plan 4: Explore Service Mesh
-趣链科技之前尝试过 traffic-mesh，未来会尝试使用 APISIX Mesh。
+Hyperchain has tried traffic-mesh before, and will try to use APISIX Mesh in
the future.
diff --git
a/website/i18n/zh/docusaurus-plugin-content-blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
b/website/i18n/zh/docusaurus-plugin-content-blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
index 2f50219..c3025fb 100644
---
a/website/i18n/zh/docusaurus-plugin-content-blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
+++
b/website/i18n/zh/docusaurus-plugin-content-blog/2021/08/09/Apache-APISIX-in-Quliankeji.md
@@ -39,7 +39,7 @@ BaaS（Blockchain as a Service），中文为“区块链即服务”，是指
### 场景 1：在 BaaS 系统上的落地实践
-
+
从这张图中可以看到，趣链科技 BaaS 平台的架构不仅是微服务化的，而且分为两层，分别是业务接入层和核心服务层。
