You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by yi...@apache.org on 2022/08/17 02:30:52 UTC
[apisix-website] branch master updated: docs: fix bad images (#1290)
This is an automated email from the ASF dual-hosted git repository.
yilinzeng 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 9811e15666c docs: fix bad images (#1290)
9811e15666c is described below
commit 9811e15666cc01aaad7dd758e6d3d6b4654584fb
Author: Fei Han <97...@users.noreply.github.com>
AuthorDate: Wed Aug 17 10:30:47 2022 +0800
docs: fix bad images (#1290)
---
.../11/beike-how-to-build-gateway-based-on-apache-apisix.md | 2 +-
blog/en/blog/2021/09/18/xiaodian-usercase.md | 6 +++---
.../11/beike-how-to-build-gateway-based-on-apache-apisix.md | 8 ++++----
blog/zh/blog/2021/09/16/tencent-cloud.md | 2 +-
blog/zh/blog/2021/09/18/xiaodian-usercase.md | 12 ++++++------
5 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/blog/en/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md b/blog/en/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
index b2f0423efc8..4e7e48347fc 100644
--- a/blog/en/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
+++ b/blog/en/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
@@ -19,7 +19,7 @@ My name is Hui Wang, and I am responsible for the development of the API gateway
## Choose Kong or Apache APISIX
-
+
For the technical requirements of the gateway, the first is to have good performance and be able to support the access of large traffic, and the second is to be stable without problems.
diff --git a/blog/en/blog/2021/09/18/xiaodian-usercase.md b/blog/en/blog/2021/09/18/xiaodian-usercase.md
index 5be5eb9b20d..c3d0c32062e 100644
--- a/blog/en/blog/2021/09/18/xiaodian-usercase.md
+++ b/blog/en/blog/2021/09/18/xiaodian-usercase.md
@@ -61,13 +61,13 @@ Of course, as an open source project, Apache APISIX has a very active community
Our current product architecture is broadly similar to using Apache APISIX in K8s. The main idea is to expose Apache APISIX’s Service as a LoadBalancer type. The user then transfers the request access to Apache APISIX and forwards the route to the upstream related service.
-
+
One additional point is why we put the ETCD outside the technology stack. The ETCD was taken out separately because of errors in resolving domain names in earlier versions, and because the internal maintenance and backup process was cumbersome.
### Business Model
-
+
The image above shows the business environment transformation model after accessing Apache APISIX. As each development or project changes, the DNA creates a change and converts it into a K8s Namespace resource.
@@ -85,7 +85,7 @@ In a change environment we have two scenarios, one is point-to-point mode, where
Another scenario is multilevel path routing. In this scenario, we use Apache APISIX to point multiple APP routes required in project changes to the current Namespace environment, and their associated APP routes to a Stable set of Namespace environments (usually Stable) .
-
+
#### Function 2: Automate the Process
diff --git a/blog/zh/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md b/blog/zh/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
index 8e7b3229668..4f075857488 100644
--- a/blog/zh/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
+++ b/blog/zh/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
@@ -19,7 +19,7 @@ tags: [Case Studies]
## 选择 Kong 还是 Apache APISIX
-
+
对于网关的技术要求，一是要性能好，能够支撑大流量的接入，二是要稳定，不能出问题。
@@ -42,7 +42,7 @@ tags: [Case Studies]
官网的理由如下图所示：
-
+
## Apache APISIX 能提供哪些能力
@@ -60,7 +60,7 @@ tags: [Case Studies]
Apache APISIX 已经发布了接近十个版本了，它所支持的功能远不止这些了。结合业务情况绘制了架构图，如下：
-
+
## 集成 APISIX 的点点滴滴
@@ -68,7 +68,7 @@ Apache APISIX 已经发布了接近十个版本了，它所支持的功能远不
在键盘上敲打了两周，我的“小金刚”终于有些模样了，该看看它跑的有多快、省不省油了，就这样压测开始了。服务部署在 8CPU 32G 内存的腾讯云上面了，上游是真实的线上生产环境，因此不能压的太狠，性能报告如下：
-
+
性能报告小结：接口耗时减少了 47%，没有错误产生稳定性有所提升，TPS 峰值提升了 82%，没有错误产生，稳定性有所提升。
diff --git a/blog/zh/blog/2021/09/16/tencent-cloud.md b/blog/zh/blog/2021/09/16/tencent-cloud.md
index 3364922921f..ad0a462430b 100644
--- a/blog/zh/blog/2021/09/16/tencent-cloud.md
+++ b/blog/zh/blog/2021/09/16/tencent-cloud.md
@@ -29,7 +29,7 @@ tags: [Case Studies]
考虑到后续业务对接腾讯云的需求，API 网关必须支持腾讯定制的鉴权和登录机制以及遵守腾讯云 API 3.0 的格式。
-
+
业务层面则主要考虑使用者感受。平台进行开发时，AI 和算法同事需要交互式编程环境，那么就需要 API 网关支持 Notebook。完成部署后，API 网关需要具有流量分配功能和足够高的性能，满足多用户直接调用接口的场景。还需支持请求级别的监控，包括日志（Logging）监控和指标（Metrics）监控。
diff --git a/blog/zh/blog/2021/09/18/xiaodian-usercase.md b/blog/zh/blog/2021/09/18/xiaodian-usercase.md
index 595180e7080..cdd563c8f79 100644
--- a/blog/zh/blog/2021/09/18/xiaodian-usercase.md
+++ b/blog/zh/blog/2021/09/18/xiaodian-usercase.md
@@ -62,13 +62,13 @@ OpenShift 3.0 开始引入 OpenShift Route ，作用是通过 Ingress Operator
我们目前的产品架构与在 K8s 中使用 Apache APISIX 大体类似。主要是将 Apache APISIX 的 Service 以 LoadBalancer 类型暴露到外部。然后用户通过请求访问传输到 Apache APISIX，再将路由转发到上游的相关服务中。
-
+
额外要提的一点是，为什么我们把 etcd 放在了技术栈外。一是因为早些版本解析域名时会出现偏差，二是因为在内部我们进行维护和备份的过程比较繁琐，所以就把 etcd 单独拿了出来。
### 业务模型
-
+
上图是接入 Apache APISIX 后的业务环境改造模型。每个开发或项目进行变更时，DNA 都会创建一个变更，同时转化为 k8s Namespace 资源。
@@ -82,11 +82,11 @@ OpenShift 3.0 开始引入 OpenShift Route ，作用是通过 Ingress Operator
在变更环境中我们有两种场景，一个是点对点模式，即一个域名对应一个应用。开发只需要启用域名，DNA 里就会利用 Apache APISIX 去生成对应路由，这种就是单一路径的路由规则。
-
+
另一种场景就是多级路径路由。在这种场景下我们基于 Apache APISIX 将项目变更中需要的多个 APP 路由指向到当前 Namespace 环境，其关联 APP 路由则指向到一套稳定的 Namespace 环境中（通常为 Stable 环境）。
-
+
#### 功能二：自动化流程
@@ -94,11 +94,11 @@ OpenShift 3.0 开始引入 OpenShift Route ，作用是通过 Ingress Operator
比如某个新应用上线时，可以申请一条相应的路由规则，然后把规则加到控制中心中。需要请求路由时，就可以一键启用这条路由规则并自动同步到 Apache APISIX。
-
+
另外我们也提供了单一普通路由申请，包括线上环境和测试环境，或者一些对外公网的暴露与测试需求等，也可以调用 Apache APISIX 接口。
-
+
## 基于 Apache APISIX 的具体实践