You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by sy...@apache.org on 2022/03/09 06:56:35 UTC
[apisix-website] branch master updated: docs: update images and add Beike english blog. (#953)
This is an automated email from the ASF dual-hosted git repository.
sylviasu 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 68a9bca docs: update images and add Beike english blog. (#953)
68a9bca is described below
commit 68a9bcaa35f613248a743ab2f73d0d2e2a92466e
Author: homeward <97...@users.noreply.github.com>
AuthorDate: Wed Mar 9 14:56:30 2022 +0800
docs: update images and add Beike english blog. (#953)
* docs: add english images
---
...-how-to-build-gateway-based-on-apache-apisix.md | 98 +++++++++++-----------
website/blog/2021/09/07/iQIYI-usercase.md | 12 +--
.../blog/2021/09/13/china-mobile-cloud-usercase.md | 10 +--
website/blog/2021/09/14/youzan.md | 12 +--
.../blog/2022/03/03/develop-apisix-with-gitpod.md | 2 +-
...-how-to-build-gateway-based-on-apache-apisix.md | 2 -
.../2022/03/03/develop-apisix-with-gitpod.md | 2 +-
7 files changed, 67 insertions(+), 71 deletions(-)
diff --git a/website/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md b/website/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
index 6863904..ec1df29 100644
--- a/website/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
+++ b/website/blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
@@ -1,93 +1,91 @@
---
-title: "贝壳找房：如何基于 Apache APISIX 搭建网关"
-author: "王辉"
+title: "Beike：How to Build Gateway Based on Apache APISIX"
+author: "Hui Wang"
keywords:
-- API 网关
+- API Gateway
- APISIX
- Apache APISIX
- Kong
- Nginx
-description: 贝壳找房使用 Apache APISIX 作为生产系统的 API 网关，每天处理过亿的生产流量，性能优异，而且很稳定。正好 Apache APISIX 刚刚加入 Apache 孵化器，除了恭喜之外，我想来分享下贝壳找房当初为什么选择 Apache APISIX，以及使用过程中的一些心得。
+description: Beike uses Apache APISIX as the API gateway of the production system, processing over 100 million production traffic every day, with excellent performance and stability. It happens that Apache APISIX has just joined the Apache incubator. In addition to congratulations, I would like to share why I chose Apache APISIX in the first place and some experiences in the process of using it.
tags: [User Case]
---
-> 本文讲述了贝壳找房当初为什么选择 Apache APISIX 作为 API 网关，以及使用过程中的一些心得。
+> This article describes why Beike chose Apache APISIX as the API gateway at the beginning, and some experiences in the process of using it.
<!--truncate-->
-我是王辉，在贝壳找房负责 API 网关系统的开发，贝壳找房使用 Apache APISIX 作为生产系统的 API 网关，每天处理过亿的生产流量，性能优异，而且很稳定。正好 Apache APISIX 刚刚加入 Apache 孵化器，除了恭喜之外，我想来分享下贝壳找房当初为什么选择 Apache APISIX，以及使用过程中的一些心得。
+My name is Hui Wang, and I am responsible for the development of the API gateway system at Beike. Beike uses Apache APISIX as the API gateway for the production system. It handles over 100 million production traffic every day, with excellent performance and stability. It happens that Apache APISIX has just joined the Apache incubator. In addition to congratulations, I would like to share why Beike chose Apache APISIX at the beginning and some experiences in the process of using it.
-## 选择 Kong 还是 Apache APISIX
+## 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.
-选型的原则就是基于或者借鉴开源项目重构一个更加稳定的版本，能够保证接入更大的流量，刚开始的流量还少，做这样的大动作是完全可以接受的。评估完利弊后和领导沟通了一下想法，得到领导的肯定后就决定搞起，这时脑海想的第一个就是 Kong 了，大名鼎鼎的开源网关。于是就去官网浏览了一番，周边文章也看了些，第一印象就是这个项目很不错，能够满足用户的大多数需求，性能还稳定，就是它了。兴高采烈地 clone 了代码开始阅读起来，一天两天若干天过去了，还是一头雾水的样子，想想也是，Kong 能提供这么多的功能，其代码的复杂度可想而知。
+The principle of model selection is to reconstruct a more stable version based on or learn from open source projects, which can ensure access to larger traffic. After evaluating the pros and cons, I communicated the idea with the leader, and decided to start it after getting the leader's affirmation. At this time, the first thing that comes to mind is Kong, the famous open source gateway. So I went to the official website to browse and read some surrounding articles. The first impression [...]
-这时几个问题出现在我的脑海里，我一个人多久能啃下来 Kong 呢？然后还要构建一个适合自己的项目，又需要多久呢？还有就是这么多的功能我都需要么？
+At this time, several questions appeared in my mind. How long can I chew down Kong by myself? And then how long does it take to build a project that suits you? There are so many functions I need?
-刚好那几天 API 网关 Apache APISIX 0.5 版本发布了，抱着了解的心态去看了一眼，发现是院生和温铭一起搞的开源项目，有两位技术大佬的背书，让我不禁想试试看。
+Just a few days ago, the API gateway Apache APISIX version 0.5 was released. I took a look with an understanding mentality and found that it was an open source project jointly developed by the academy student and Wen Ming. With the guarantee of two technical bigwigs, I really wanted to try it out. .
-抱着试一试的态度开始走近 Apache APISIX，由于开源时间较短所以支持的功能有限，但是像动态负载均衡、熔断、身份认证、限速等等这些基本功能都已实现。同时代码量也不是很大降低了学习成本，在这一点上 PK 掉了 Kong。所以综合来看 Apache APISIX 更适合我当前的状况，满足我初期的功能规划，也不用考虑不需要的功能怎么处理问题了。
+With the attitude of giving it a try, I started to approach Apache APISIX. Due to the short open source time, the supported functions are limited, but basic functions such as dynamic load balancing, circuit breaker, identity authentication, speed limit, etc. have been implemented. At the same time, the amount of code is not very large, which reduces the cost of learning. At this point, PK lost Kong. So on the whole, Apache APISIX is more suitable for my current situation, to meet my init [...]
-最关键的问题，开源时间这么短，性能怎么样？看了相同环境的压测数据对比，Apache APISIX 完爆 Kong，虽然这样不太公平，毕竟 Kong 是个庞然大物，但对于我的生产环境来说，它俩是一样的。根据 Apache APISIX 的性能测试报告，单核 CPU 可以达到 24k QPS，同时延时只有 0.7 毫秒。
+The most critical question, how is the performance of the open source time so short? Looking at the comparison of the stress test data in the same environment, Apache APISIX completely exploded Kong, although this is not fair. After all, Kong is a behemoth, but for my production environment, they are the same. According to the performance test report of Apache APISIX, a single-core CPU can reach 24k QPS, while the latency is only 0.7 milliseconds.
-最终选择了 Apache APISIX，我的理由如下：
+In the end, I chose Apache APISIX for the following reasons:
-+ 在都能满足项目需求的前提下，Apache APISIX 学习成本低
-+ Kong 的代码量庞大，后期维护也会带来难度
-+ Apache APISIX 作者经常活跃于 OpenResty 社区，代码质量有保证
-+ 最重要的一点就是接触过作者，有什么问题都可以快速的沟通
+- On the premise that it can meet the needs of the project, the learning cost of Apache APISIX is low
+- Kong has a huge amount of code, and later maintenance will also bring difficulties
+- Apache APISIX authors are often active in the OpenResty community with guaranteed code quality
+- The most important point is to have contact with the author, and you can communicate quickly if you have any questions
-官网的理由如下图所示：
+The reasons for the APISIX official website are shown in the following figure:
-
+
-## Apache APISIX 能提供哪些能力
+## What capabilities can Apache APISIX provide
-+ 热更新和热插件
-+ 动态负载均衡
-+ 主动和被动健康检测
-+ 熔断器
-+ 身份认证
-+ 限流限速
-+ gRPC 协议转换
-+ 动态 TCP/UDP、gRPC、websocket、MQTT 代理
-+ 控制台
-+ 黑白名单
-+ Serverless
+- Hot Updates and Hot Plugins
+- Dynamic load balancing
+- Active and passive health detection
+- Circuit Breaking
+- Authentication
+- Current limit and speed limit
+- gRPC protocol conversion
+- Dynamic TCP/UDP, gRPC, websocket, MQTT broker
+- Dashboard
+- Prohibited and Permitted List
+- Serverless
-Apache APISIX 已经发布了接近十个版本了，它所支持的功能远不止这些了。结合业务情况绘制了架构图，如下：
+Apache APISIX has been released nearly ten versions, and it supports far more functions than these. The architecture diagram is drawn according to the business situation, as follows:
-
+
-## 集成 APISIX 的点点滴滴
+## Integrating APISIX Process
-经过几天的代码阅读，对 Apache APISIX 有了一定的了解了，但第一个问题出现了：之前没有基于开源项目开发的经验，一方面要做业务需求迭代，一方面还要升级开源项目，怎么搞呢？我在本地创建了三个分支，一个 Apache APISIX 分支指向上游开源仓库，dev 用来常规的业务迭代，而 master 分支用来上线升级。
+After a few days of code reading, I have a certain understanding of Apache APISIX, but the first problem arises: I have no experience in developing based on open source projects before. How to do it? I created three branches locally, one Apache APISIX branch points to the upstream open source repository, dev is used for regular business iteration, and the master branch is used for online upgrades.
-在键盘上敲打了两周，我的“小金刚”终于有些模样了，该看看它跑的有多快、省不省油了，就这样压测开始了。服务部署在 8CPU 32G 内存的腾讯云上面了，上游是真实的线上生产环境，因此不能压的太狠，性能报告如下：
+After two weeks of typing on the keyboard, my "Little King Kong" finally has some appearance. It's time to see how fast it runs and whether it saves fuel. That's how the stress test began. The service is deployed on Tencent Cloud with 8 Core and 32 GB emory. The upstream is a real online production environment, so it cannot be pressed too hard. The performance report is as follows:
-
+
-性能报告小结：接口耗时减少了 47%，没有错误产生稳定性有所提升，TPS 峰值提升了 82%，没有错误产生，稳定性有所提升。
+Performance report summary: The interface time consumption is reduced by 47%, no errors are generated, and the stability is improved. The TPS peak value is increased by 82%, no errors are generated, and the stability is improved.
-开发环境没问题了，开始研究线上部署。Apache APISIX 支持各种安装的方式：docker、rpm 包、Luarocks 和源码。但是线上环境不让安装任何东西，代码只能放到固定的路径中，Apache APISIX 支持的很多特性都是基于 OpenResty 1.15.8 的，咋搞呢？编译完了放在代码仓库中吧，按照指定的目录进行编译，而且不能用 pcre 的静态联编，折腾了一两天才搞定。调整负载开始灰度，从 2% 的流量到全量经历了几周，好在一切顺利。
+The development environment is no problem, and we start to study online deployment. Apache APISIX supports various installation methods: Docker, RPM Package, Luarocks and Source Code. However, the online environment does't allow anything to be installed, and the code can only be placed in a fixed path. Many features supported by Apache APISIX are based on OpenResty 1.15.8. What should I do? After compiling, put it in the code repository, compile it according to the specified directory, a [...]
-经过几周的观察线上服务很稳定，Apache APISIX 0.5 版本的很多功能都是得用通过 API 接口调用实现的，请求参数比较容易出现语法错误，没有页面来的直观方便，还有一点就是我的业务场景需要有对上游服务的探活功能。就是这么巧 Apache APISIX 0.7 版本发布了，0.7 版本支持了控制台和上游服务探活，真是个喜大普奔的好消息啊，升级。
+After several weeks of observation, the online service is very stable. Many functions of Apache APISIX 0.5 must be implemented through API interface calls. The request parameters are prone to syntax errors, and there is no intuitive and convenient page. Another point is that my business scenario needs to have the function of probing upstream services. It's such a coincidence that Apache APISIX version 0.7 has been released, and version 0.7 supports console and upstream service exploratio [...]
-Apache APISIX 分支升级到 0.7 很方便，我咋合并代码呢？两个版本代码改动非常大，先尝试一下合并，我的天啊，这冲突太多了，搞死的节奏啊，普通的解决冲突的方法不现实了，这么多处手一抖还会出现一下隐藏的 bug，有没有啥高效的方法呢？搜索了一下找到了快捷方法 git checkout --ours 和 git checkout --theirs（没用过的自行搜索哈），几分钟完成 APISIX 0.5 到 0.7 的升级，很痛快。当然这也是得益于 APISIX 代码的健壮，我只需要添加业务插件即可，完全零耦合。
+The Apache APISIX branch is easy to upgrade to 0.7, how do I merge the code? The code changes of the two versions are very large. Try to merge them first. There are too many conflicts, and the rhythm is dead. The ordinary method of resolving conflicts is unrealistic. There will be hidden bugs when you shake your hands in so many places. Is there no efficient way? I searched and found the shortcut methods git checkout --ours and git checkout --theirs (search for yourself if you haven't us [...]
-Apache APISIX 0.7 版本提供了控制台了，不用再拼 json 了，舒服。赶紧测试一下自己关心的健康检测吧，一开始没什么问题，能够清晰的感知上游服务的状态，但我观察上游服务的日志发现，经过几次启停，健康检测功能探活的频率好像变快了，应该是健康检测有 bug，简单的阅读一下相关的代码，发现创建的每个路由的 checker 不是全局唯一的，而是每个 work 创建了一个，发现问题就好办了，创建的 work 都用一个 name 就能保证全局唯一了，虽然改动很小，但还是赶紧提交了一个 PR。
+Apache APISIX 0.7 version provides a console, no need to spell json anymore. I quickly tested the health detection function. There was no problem at first, and I could clearly perceive the status of the upstream service. However, when I observed the logs of the upstream service, I found that after several starts and stops, the frequency of the health detection function seems to be faster. It should be that there is a bug in the health check. Simply read the relevant code and find that th [...]
-把线上业务 APISIX 升级到了 0.7，然后观察服务资源占用情况，毕竟是升级了较大的版本，头几个小时还没感觉，和之前 0.5 差不多。等下班时再看一眼，好像内存资源占用好像不太对，0.5 版本一直比较稳定，0.7 却好像有泄漏，因为内存的占用增长很慢，就决定再观察一晚上。第二天来对比了监控数据，确定是有内存泄漏，赶紧回滚到上一个版本。和院生反馈了一下问题，根据我描述的场景通过压测发现了问题所在，是 radixtree 的问题，院生发布了 radixtree 的新版本，我升级了一下依赖，然后在进行压测，没有复现问题，皆大欢喜。
+I upgraded the online business APISIX to 0.7, and then observed the service resource usage. After all, it was a larger version, and I didn’t feel it for the first few hours, which was similar to the previous 0.5. I'll take a look at it again when I get off work. It seems that the memory resource usage is not right. The 0.5 version has been relatively stable, but the 0.7 version seems to have leaks. Because the memory usage is growing very slowly, I decided to observe it for another night [...]
-再次上线，Apache APISIX 0.7 版本还是给了我一些惊喜的，之前 Apache APISIX 0.5 版本使用的路由依赖是 libr3，而 Apache APISIX 0.7 是换用了 radixtree，较之前有更好的表现，cpu 使用率和内存都有所下降，Apache APISIX 0.5 版本单 work 的 cpu 在 1-10%，内存 0.1%，Apache APISIX 0.7 版本单 work 的 cpu 使用率降低到 1-2%，内存也不足 0.1% 了，优秀。
+Going online again, Apache APISIX 0.7 version still gave me some surprises. The routing dependency used in Apache APISIX 0.5 version was libr3, while Apache APISIX 0.7 used radixtree instead, which has better performance, cpu usage and memory than before. All have declined. In Apache APISIX 0.5, the single-work cpu usage is 1-10%, and the memory is 0.1%. In Apache APISIX 0.7, the single-work cpu usage is reduced to 1-2%, and the memory is less than 0.1%, which is excellent.
-## 未来规划
+## Future Plan
-Apache APISIX 在线上已经跑了两个月了，还未出现线上故障，窃喜。这才是开始，后续我们还能做很多东西，把更多的能力展现给服务方。网关提供的不仅仅只是反向代理，可以给一些没有更多精力去开发保证服务稳定功能的团队提供帮助，包括限流、熔断、监控等服务，还有接入的平台。最后感谢两位大佬提供了这么优秀的产品，也感谢 Apache APISIX 社区贡献出的迭代功能。
+Apache APISIX has been running online for two months, and there has been no online failure. This is the beginning, and we can do a lot in the future to show more capabilities to service providers. The gateway provides not only a reverse proxy, but also helps some teams that do not have more energy to develop functions to ensure service stability, including services such as current limiting, circuit breaker, monitoring, and access platforms. Finally, I would like to thank the two big guys [...]
-现在网关每日流量已经过亿，还没有什么性能问题，流量如果能达到十亿级，后续还会再分享一下 Apache APISIX 和我的前行之路，欢迎大家关注。
+Now the daily traffic of the gateway has exceeded 100 million, and there is no performance problem. If the traffic can reach one billion, I will share Apache APISIX and my way forward in the future. Welcome everyone to pay attention.
diff --git a/website/blog/2021/09/07/iQIYI-usercase.md b/website/blog/2021/09/07/iQIYI-usercase.md
index 3a8a8c1..f1612aa 100644
--- a/website/blog/2021/09/07/iQIYI-usercase.md
+++ b/website/blog/2021/09/07/iQIYI-usercase.md
@@ -31,7 +31,7 @@ Before choosing Apache APISIX, the iqiyi platform was already using Kong, but it
### Why Give Up Kong
-
+
Kong uses PostgreSQL to store its information, which is obviously not a good way. We also looked at the performance of Apache APISIX compared to Kong in the course of our research, and it’s amazing that Apache Apisix is 10 times better than Kong in terms of performance optimization. We also compared some of the major gateway products, Apache APISIX’s response latency is more than 50% lower than other gateways, and Apache APISIX can still run stably when the CPU reaches more than 70% .
@@ -43,13 +43,13 @@ We also saw that Apache APISIX was very active throughout the open source projec
The overall architecture of iQIYI Gateway is shown below, including domain name, gateway to service instance and monitoring alarm. DPVS is an open source project within the company based on LVS, Hubble monitoring alerts is also a deep secondary development based on an open source project, and the Consul area has been optimized for performance and high availability.
-
+
### Scenario 1: Microservice Gateway
About the gateway this piece, simple from the control surface and the data surface introduce.
-
+
The data plane is mainly oriented to the front-end users, and the whole architecture from LB to Gateway is multi-location and multi-link disaster deployment.
@@ -59,7 +59,7 @@ From the perspective of control surface, because of the multi-cluster compositio
At present, the API architecture based on Apache APISIX has realized some basic functions, such as current limiting, authentication, alarm, monitoring and so on.
-
+
First is the HTTPS section, iQIYI for security reasons, certificates and keys are not stored on the gateway machine, will be placed on a dedicated remote server. We didn’t support this when we used Kong, we used the prefix Nginx to do HTTPS Offload, and after the migration to Apache APISIX, we implemented this feature on Apache APISIX, which is a layer less forwarding over the link.
@@ -71,13 +71,13 @@ The monitoring feature is currently implemented using the Apache APISIX plug-in
With regard to the above-mentioned service discovery, it is mainly through the service center to register the service to the Consul cluster, and then through the DNS service discovery to do dynamic updates, qae is a micro-service platform in our company. A simple example illustrates the general flow of updating a backend application instance.
-
+
When the instance changes, the corresponding node is first unlogged from Consul and a request to update the DNS cache is sent to the gateway through the API Gateway Controller. After the cache update is successful, the Controller then feeds back to the QAE platform to stop the associated back-end application node and avoid reforwarding traffic to the offline node.
### Scenario 4: Directional Route
-
+
The gateway is multi-location deployment, build a set of multi-location backup link in advance, at the same time suggest the user back-end service is also multi-location deployment nearby. Then the user creates an API service on the Skywalker Gateway platform, the Controller deploys the API routing on the entire DC gateway cluster, and the business domain defaults to CNAME on the unified gateway domain name.
diff --git a/website/blog/2021/09/13/china-mobile-cloud-usercase.md b/website/blog/2021/09/13/china-mobile-cloud-usercase.md
index ba009ac..d4ab668 100644
--- a/website/blog/2021/09/13/china-mobile-cloud-usercase.md
+++ b/website/blog/2021/09/13/china-mobile-cloud-usercase.md
@@ -64,11 +64,11 @@ By accessing Apache APISIX, we realize multi-domain certificate configuration fo
Here we first give you a brief description of the current Object Storage EOS node management after accessing Apache APISIX. The entire object store is divided into a data plane and a control plane. The data plane mainly carries the I/O flow of the whole business. The business data is processed from APISIX’s Layer 7 traffic governance module as the entry point, through the APISIX back-end upstream Accesser, which is the main module for business interface processing.
-
+
The control plane has several main services, including the autopilot service Manager, the observable system Observer, and the chaos engineering fault injection module Checker. there is also an additional overall interaction orchestration system Orchestrator and a canary release platform Publisher.
-
+
In order to achieve request fusion protection, the data plane is connected to Apache APISIX to achieve the processing capability of request intervention. The observable system at the control plane is mainly built based on Prometheus, which collects indicators and alerts, and finally realizes the overall fusion protection at the back-end.
@@ -77,7 +77,7 @@ In order to achieve request fusion protection, the data plane is connected to Ap
limit-conn key This plugin mainly supports remote_addr, server_addr, X-Forwarded-For, X-Real-IP, but cannot do full limit flow for north-south gateway traffic.
In order to match our business requirements, we customize a constant constant as the range of imit-conn key. The right side of the above figure is the modified configuration after accessing Apache APISIX, and the constant constant constant key is used to achieve the function of global flow-limit.
-
+
### Improvement 4: New Function Feature Switches
@@ -103,7 +103,7 @@ Combined with the Apache APISIX Layer 7 governance capabilities, we perform upgr
Based on access.log, we have implemented a centralized log collection management method to collect APISIX logs and logs of other processes, and then perform a comprehensive analysis.
-
+
The configuration item on the right side of the image above uses the request-id plugin of Apache APISIX. Each request is assigned a request-id when it passes through APISIX, which is used in the business logic processing layer (Accesser) and the data persistence layer, which in turn filters out the log timestamps of the different components in the official Loki panel and helps to automate some analysis using AI later.
@@ -112,7 +112,7 @@ The configuration item on the right side of the image above uses the request-id
The backend of the current load balancing is a seven-layer traffic governance layer based on APISIX implementation, which achieves multi-live capability by equal ECMP + BGP routing. We define three traffic types, each APISIX node receives service traffic and only hits the upstream service of this node to process (level0, purple line), similar to SideCar mode.
If a node has a problem upstream, it will be forwarded to other upstream nodes in the same AZ for processing (green line). If all upstream nodes hang, the ability to invoke requests across AZs (level2, red line) is implemented based on Apache APISIX, which writes the requests to other AZs and finally achieves request scheduling across AZs.
-
+
## Future Plans
diff --git a/website/blog/2021/09/14/youzan.md b/website/blog/2021/09/14/youzan.md
index d1c6abd..671c089 100644
--- a/website/blog/2021/09/14/youzan.md
+++ b/website/blog/2021/09/14/youzan.md
@@ -22,7 +22,7 @@ Youzan is a major retail technology SaaS provider that helps businesses open onl
Youzan OPS platform is based on FLASK in the early single application, mainly to support business-oriented. It gradually went online and deployed a lot of business-side code into the containerization phase. At that time, the gateway was only a part of the function of the internal flash application, and there was no clear concept of the gateway, only as the traffic forwarding function of business application. The following illustration shows the current Gateway 1.0 business structure.
-
+
As the entire system in the early days mainly focused on the direction of the business, so did not generate too much momentum to carry out the transformation. From 2018 onwards, through internal communication, we found that if there is not a good gateway layer governance, the subsequent product function and business access will bring more and more obvious bottlenecks.
@@ -40,7 +40,7 @@ Based on this problem, our action direction is: the professional work to the pro
#### Internal Operational Aspects
-
+
1. The number of internal services to manage is very high (hundreds)
2. Some services do not dock with CAS implementation authentication
@@ -57,7 +57,7 @@ We also initially investigated a number of gateway systems, such as Apache APISI
Considering the maturity and extensibility of the product, we finally made a choice between Kong and Apache APISIX.
-
+
As you can see from the image above, the two are basically the same in many ways, so the storage side has become a key consideration. Because etcd is mature in our company’s internal operation and maintenance system, Apache APISIX is a little better than Kong.
@@ -73,7 +73,7 @@ When we started accessing Apache APISIX, the two problems mentioned above were s
Apache APISIX is deployed as an entry point to gateway at the edge of the internal service area, through which all requests to the front end pass. At the same time, we use the plug-in function of Apache APISIX to connect with the company’s internal CAS single sign-on system. At the same time in the front end we provide a responsible for authentication SDK Apache APISIX authentication interface docking, to achieve a complete and automated process system.
-
+
So the problem was solved:
@@ -92,7 +92,7 @@ Some of the fine-tuning details of the in-house service are briefly described he
The authentication plug-in is developed based on JWT-Auth protocol. When a user accesses the front end, the front end calls the SDK first to get the available JWT-Token locally. Then through the following path to get the user’s valid information, placed in the front-end of a storage, complete login authentication.
-
+
#### Deployment Configuration Upgrade
@@ -136,7 +136,7 @@ In our usage scenario, we are more involved in multi-service of intranet, and we
Then we’re going to Dock Apache Apisix with the company’s permission system, and after authentication, determine if the user has access to a resource on the back end, the administrator of the permissions only needs to make a uniform configuration on the administration plane.
-
+
One of the benefits of this is that all back-end services do not need to be individually managed, since all current traffic is handled through the gateway layer.
diff --git a/website/blog/2022/03/03/develop-apisix-with-gitpod.md b/website/blog/2022/03/03/develop-apisix-with-gitpod.md
index 9665d9c..a51f616 100644
--- a/website/blog/2022/03/03/develop-apisix-with-gitpod.md
+++ b/website/blog/2022/03/03/develop-apisix-with-gitpod.md
@@ -32,7 +32,7 @@ This development model has many benefits for developers, such as:
- Quickly start or destroy a development environment for each project to avoid problems such as dependency conflicts when multiple projects are developed in parallel.
- For pure Linux environments, it is sometimes more difficult for server-side development students to toss some dependency differences between MacOS and Windows than to develop project code.
-The two most popular IDEs are Jetbrain and VSCode, and both of these popular development tools have cloud-based products, so it's clear that the "cloud IDE" direction is favored by many developers.
+The two most popular IDEs are JetBrains and VSCode, and both of these popular development tools have cloud-based products, so it's clear that the "cloud IDE" direction is favored by many developers.
Apache APISIX is a dynamic, real-time, high-performance API gateway that provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more.
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md b/website/i18n/zh/docusaurus-plugin-content-blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
index 6863904..9a06092 100644
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
+++ b/website/i18n/zh/docusaurus-plugin-content-blog/2020/12/11/beike-how-to-build-gateway-based-on-apache-apisix.md
@@ -20,8 +20,6 @@ tags: [User Case]
## 选择 Kong 还是 Apache APISIX
-
-
对于网关的技术要求，一是要性能好，能够支撑大流量的接入，二是要稳定，不能出问题。
diff --git a/website/i18n/zh/docusaurus-plugin-content-blog/2022/03/03/develop-apisix-with-gitpod.md b/website/i18n/zh/docusaurus-plugin-content-blog/2022/03/03/develop-apisix-with-gitpod.md
index 06c5ea4..08562c1 100644
--- a/website/i18n/zh/docusaurus-plugin-content-blog/2022/03/03/develop-apisix-with-gitpod.md
+++ b/website/i18n/zh/docusaurus-plugin-content-blog/2022/03/03/develop-apisix-with-gitpod.md
@@ -32,7 +32,7 @@ tags: [Technology]
- 快速为每个项目启动或摧毁一个开发环境，避免多个项目并行开发时存在依赖冲突等问题；
- 纯粹的 Linux 环境。对于服务端开发同学来说，MacOS 和 Windows 的依赖问题往往比开发项目代码还要困难；
-目前最流行的两种 IDE，非 Jetbrain 系和 VSCode 莫属，而这两种广受欢迎的开发工具都有相关的云产品面世，可见很多开发者看好“云 IDE”这个方向。
+目前最流行的两种 IDE，非 JetBrains 系和 VSCode 莫属，而这两种广受欢迎的开发工具都有相关的云产品面世，可见很多开发者看好“云 IDE”这个方向。
Apache APISIX 是一个动态、实时、高性能的 API 网关，提供负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。