You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/10/27 02:10:13 UTC
[GitHub] [apisix-website] yzeng25 commented on a change in pull request #682: docs: translate blogs on 2021.07 and 2021.06
yzeng25 commented on a change in pull request #682:
URL: https://github.com/apache/apisix-website/pull/682#discussion_r737034636
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
Review comment:
```suggestion
yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
```
I don't get the point of having 'Shuyang Wu!' in front of the picture here.
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
-
+## Sharing Guest: Zeping Bai
-**Q：泽平，你好，请做个简单的自我介绍吧。**
+! [Zeping Bai](https://static.apiseven.com/202108/1630546751119-8df77cd8-6be0-4f8e-af13-182e77462d73.png)
-**泽平**：我是白泽平，目前在天津商业大学工商管理专业大三年级。从我初中时开始我就在自学编程了，它也成了我的兴趣之一。我擅长的领域主要是后端、Web 前端开发，曾经还客串过 Android 开发，主要使用 Golang、PHP 和 Javascript。
+**Q: Hi Zeping, please do a brief introduction of yourself.**
-**Q：去年你为什么会选择参加编程之夏，选择 Apache APISIX 的项目?**
+**Zeping**: I'm Zeping Bai, I'm currently in my junior year of Business Administration at Tianjin University of Commerce. I've been teaching myself programming since I was in junior high school, and it's become one of my hobbies. I specialize in back-end, web front-end development, and once guest-hosted Android development, mainly using Golang, PHP and Javascript.
-**泽平**：之前在使用 Apache APISIX 网关控制面板时发现了一些没有支持到的功能，于是提交了一些代码完善了这块的功能，社区的大佬们很给力，能让我学到不少东西，这给了我参与开源项目的动力。在去年编程之夏活动开始之前我申请了其他社区项目的 GSoC，但没有被选中，后来看到编程之夏 2020 的活动宣传时，就报名参加了。
+**Q: Why did you choose to participate in Summer of Programming last year and choose the Apache APISIX project?**
-**Q：今年你成为了 Apache APISIX 项目导师，对于项目申请有哪些 tips 可以给到大家？**
+**Zephyr**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
-**泽平**：在项目申请书中主要描述一下你关于当前项目方案的想法或相关的技术路线，同时还要简要描述一下实现项目目标的过程（从每一个小模块出发逐步实现项目目标）和大致所需的时间。其余的信息需要如个人介绍等。以上内容可以帮助我们快速的你的能力和项目方案，有助于项目申请。同时还可以提前与项目导师联系，了解更全面的项目信息。
+**Q: This year you became an Apache APISIX project mentor, what tips can you give to people about applying for the project?**
-**Q：泽平，今年你成为了社区项目的导师，关于这个角色的转变，有什么想和大家分享一下的吗？**
+**Zephyr**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
-**泽平**：去年作为学生参加编程之夏活动时，得到了不少指导与帮助，如果你今年选择参加 Apache APISIX 社区的项目，我同样也会为你提供帮助，让你更快的上手项目开发。
+**Q: Zephyr, you became a mentor for the community program this year, is there anything you would like to share with us about this change in role?**
Review comment:
```suggestion
**Q: Zeping, you became a mentor for the community program this year, is there anything you would like to share with us about this change in role?**
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
Review comment:
```suggestion
**Shuyang**: Hi, I'm Shuyang Wu, graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
Review comment:
```suggestion
**Shuyang**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
-右图部分就是 APISIX Mesh 的内部架构图。
+The diagram on the right shows the internal architecture of APISIX Mesh.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625024.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
Review comment:
```suggestion
**Shuyang**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
-
+## Sharing Guest: Zeping Bai
-**Q：泽平，你好，请做个简单的自我介绍吧。**
+! [Zeping Bai](https://static.apiseven.com/202108/1630546751119-8df77cd8-6be0-4f8e-af13-182e77462d73.png)
-**泽平**：我是白泽平，目前在天津商业大学工商管理专业大三年级。从我初中时开始我就在自学编程了，它也成了我的兴趣之一。我擅长的领域主要是后端、Web 前端开发，曾经还客串过 Android 开发，主要使用 Golang、PHP 和 Javascript。
+**Q: Hi Zeping, please do a brief introduction of yourself.**
-**Q：去年你为什么会选择参加编程之夏，选择 Apache APISIX 的项目?**
+**Zeping**: I'm Zeping Bai, I'm currently in my junior year of Business Administration at Tianjin University of Commerce. I've been teaching myself programming since I was in junior high school, and it's become one of my hobbies. I specialize in back-end, web front-end development, and once guest-hosted Android development, mainly using Golang, PHP and Javascript.
-**泽平**：之前在使用 Apache APISIX 网关控制面板时发现了一些没有支持到的功能，于是提交了一些代码完善了这块的功能，社区的大佬们很给力，能让我学到不少东西，这给了我参与开源项目的动力。在去年编程之夏活动开始之前我申请了其他社区项目的 GSoC，但没有被选中，后来看到编程之夏 2020 的活动宣传时，就报名参加了。
+**Q: Why did you choose to participate in Summer of Programming last year and choose the Apache APISIX project?**
-**Q：今年你成为了 Apache APISIX 项目导师，对于项目申请有哪些 tips 可以给到大家？**
+**Zephyr**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
-**泽平**：在项目申请书中主要描述一下你关于当前项目方案的想法或相关的技术路线，同时还要简要描述一下实现项目目标的过程（从每一个小模块出发逐步实现项目目标）和大致所需的时间。其余的信息需要如个人介绍等。以上内容可以帮助我们快速的你的能力和项目方案，有助于项目申请。同时还可以提前与项目导师联系，了解更全面的项目信息。
+**Q: This year you became an Apache APISIX project mentor, what tips can you give to people about applying for the project?**
-**Q：泽平，今年你成为了社区项目的导师，关于这个角色的转变，有什么想和大家分享一下的吗？**
+**Zephyr**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
Review comment:
```suggestion
**Zeping**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
Review comment:
@juzhiyuan is it deleted by accident?
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
Review comment:
```suggestion
**Shuyang**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
-
+## Sharing Guest: Zeping Bai
-**Q：泽平，你好，请做个简单的自我介绍吧。**
+! [Zeping Bai](https://static.apiseven.com/202108/1630546751119-8df77cd8-6be0-4f8e-af13-182e77462d73.png)
-**泽平**：我是白泽平，目前在天津商业大学工商管理专业大三年级。从我初中时开始我就在自学编程了，它也成了我的兴趣之一。我擅长的领域主要是后端、Web 前端开发，曾经还客串过 Android 开发，主要使用 Golang、PHP 和 Javascript。
+**Q: Hi Zeping, please do a brief introduction of yourself.**
-**Q：去年你为什么会选择参加编程之夏，选择 Apache APISIX 的项目?**
+**Zeping**: I'm Zeping Bai, I'm currently in my junior year of Business Administration at Tianjin University of Commerce. I've been teaching myself programming since I was in junior high school, and it's become one of my hobbies. I specialize in back-end, web front-end development, and once guest-hosted Android development, mainly using Golang, PHP and Javascript.
-**泽平**：之前在使用 Apache APISIX 网关控制面板时发现了一些没有支持到的功能，于是提交了一些代码完善了这块的功能，社区的大佬们很给力，能让我学到不少东西，这给了我参与开源项目的动力。在去年编程之夏活动开始之前我申请了其他社区项目的 GSoC，但没有被选中，后来看到编程之夏 2020 的活动宣传时，就报名参加了。
+**Q: Why did you choose to participate in Summer of Programming last year and choose the Apache APISIX project?**
-**Q：今年你成为了 Apache APISIX 项目导师，对于项目申请有哪些 tips 可以给到大家？**
+**Zephyr**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
Review comment:
```suggestion
**Zeping**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
-
+## Sharing Guest: Zeping Bai
-**Q：泽平，你好，请做个简单的自我介绍吧。**
+! [Zeping Bai](https://static.apiseven.com/202108/1630546751119-8df77cd8-6be0-4f8e-af13-182e77462d73.png)
-**泽平**：我是白泽平，目前在天津商业大学工商管理专业大三年级。从我初中时开始我就在自学编程了，它也成了我的兴趣之一。我擅长的领域主要是后端、Web 前端开发，曾经还客串过 Android 开发，主要使用 Golang、PHP 和 Javascript。
+**Q: Hi Zeping, please do a brief introduction of yourself.**
-**Q：去年你为什么会选择参加编程之夏，选择 Apache APISIX 的项目?**
+**Zeping**: I'm Zeping Bai, I'm currently in my junior year of Business Administration at Tianjin University of Commerce. I've been teaching myself programming since I was in junior high school, and it's become one of my hobbies. I specialize in back-end, web front-end development, and once guest-hosted Android development, mainly using Golang, PHP and Javascript.
-**泽平**：之前在使用 Apache APISIX 网关控制面板时发现了一些没有支持到的功能，于是提交了一些代码完善了这块的功能，社区的大佬们很给力，能让我学到不少东西，这给了我参与开源项目的动力。在去年编程之夏活动开始之前我申请了其他社区项目的 GSoC，但没有被选中，后来看到编程之夏 2020 的活动宣传时，就报名参加了。
+**Q: Why did you choose to participate in Summer of Programming last year and choose the Apache APISIX project?**
-**Q：今年你成为了 Apache APISIX 项目导师，对于项目申请有哪些 tips 可以给到大家？**
+**Zephyr**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
-**泽平**：在项目申请书中主要描述一下你关于当前项目方案的想法或相关的技术路线，同时还要简要描述一下实现项目目标的过程（从每一个小模块出发逐步实现项目目标）和大致所需的时间。其余的信息需要如个人介绍等。以上内容可以帮助我们快速的你的能力和项目方案，有助于项目申请。同时还可以提前与项目导师联系，了解更全面的项目信息。
+**Q: This year you became an Apache APISIX project mentor, what tips can you give to people about applying for the project?**
-**Q：泽平，今年你成为了社区项目的导师，关于这个角色的转变，有什么想和大家分享一下的吗？**
+**Zephyr**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
Review comment:
```suggestion
**Zepingr**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
```
##########
File path: website/blog/2021/06/17/Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md
##########
@@ -1,49 +1,50 @@
---
-title: "Apache APISIX Dashboard 访问控制绕过漏洞公告（CVE-2021-33190）"
-author: "琚致远"
+title: Apache APISIX Dashboard Access Control Bypass Vulnerability Advisory (CVE-2021-33190)
+author: Zhiyuan Ju
authorURL: "https://github.com/juzhiyuan"
authorImageURL: "https://avatars.githubusercontent.com/u/2106987?v=4"
keywords:
- APISIX
- Apache APISIX
- Ingress Controller
-description: Apache APISIX Dashboard 访问控制绕过漏洞公告
+description: Apache APISIX Dashboard Access Control Bypass Vulnerability Bulletin
tags: [Security]
---
-> 由于程序通过获取请求头 `X-Forwarded-For` 的值来进行访问控制判断，导致攻击者在调用 API 请求时，只需篡改该请求头即可实现访问控制绕过攻击。
+> Because the application makes access control determinations by obtaining the value of the request header `X-Forwarded-For`, an attacker can achieve an access control bypass attack by simply tampering with that request header when invoking the API request.
-<!--truncate-->
-## 问题描述
+<! --truncate -->
-在 Apache APISIX Dashboard 2.6 中，存在两个配置项：
+## Problem Description
-1. `conf.listen.host` 的配置项，用于指定 ManagerAPI 在启动时监听哪个 IP 地址，它的默认值为 `0.0.0.0` （默认监听外部网络请求）；
+In Apache APISIX Dashboard 2.6, there are two configuration entries.
-2. `conf.allow_list` 的配置项，用于进行访问控制，默认只允许 `127.0.0.1` （即本地网络）进行访问。
+1. the `conf.listen.host` configuration item, which specifies which IP address ManagerAPI listens to at startup, and which defaults to `0.0.0.0` (listens to external network requests by default).
-由于程序通过获取请求头 `X-Forwarded-For` 的值来进行访问控制判断，导致攻击者在调用 API 请求时，只需篡改该请求头即可实现访问控制绕过攻击。
+2. the configuration item `conf.allow_list`, which is used for access control and only allows access to `127.0.0.1` (i.e. local network) by default.
-## 影响版本
+Since the program makes access control determinations by obtaining the value of the request header `X-Forwarded-For`, an attacker can achieve an access control bypass attack by simply tampering with this request header when invoking an API request.
+
+## Affected Versions
Apache APISIX 2.6.0
-## 解决方案
+## Solution
-该问题已在 2.6.1 版本中解决，请尽快更新至最新版本，并在部署程序后修改默认用户名与密码。
+This issue has been resolved in version 2.6.1. Please update to the latest version as soon as possible and change the default username and password after deploying the application.
-## 漏洞详情
+## Vulnerability details
-漏洞公开时间：2021 年 6 月 8 日
+Vulnerability public date: June 8, 2021
-CVE 详细信息：https://nvd.nist.gov/vuln/detail/CVE-2021-33190
+CVE details: https://nvd.nist.gov/vuln/detail/CVE-2021-33190
-## 贡献者简介
+## Contributor Profile
-该漏洞是由平安科技银河安全实验室的 Vern 发现，并向 Apache 软件基金会上报该漏洞。感谢 Vern 和平安科技银河安全实验室对 Apache APISIX 社区的贡献。
+This vulnerability was discovered by Vern at Ping An Technology Galaxy Security Lab and reported to the Apache Software Foundation. Thanks to Vern and Ping An Technology Galaxy Security Lab for their contributions to the Apache APISIX community.
-
+! [2021-06-17-1](/img/blog_img/2021-06-17-1.jpeg)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/17/Apache-APISIX-Dashboard-Access-Control-Bypass-Vulnerability-Announcement.md
##########
@@ -1,49 +1,50 @@
---
-title: "Apache APISIX Dashboard 访问控制绕过漏洞公告（CVE-2021-33190）"
-author: "琚致远"
+title: Apache APISIX Dashboard Access Control Bypass Vulnerability Advisory (CVE-2021-33190)
+author: Zhiyuan Ju
authorURL: "https://github.com/juzhiyuan"
authorImageURL: "https://avatars.githubusercontent.com/u/2106987?v=4"
keywords:
- APISIX
- Apache APISIX
- Ingress Controller
-description: Apache APISIX Dashboard 访问控制绕过漏洞公告
+description: Apache APISIX Dashboard Access Control Bypass Vulnerability Bulletin
tags: [Security]
---
-> 由于程序通过获取请求头 `X-Forwarded-For` 的值来进行访问控制判断，导致攻击者在调用 API 请求时，只需篡改该请求头即可实现访问控制绕过攻击。
+> Because the application makes access control determinations by obtaining the value of the request header `X-Forwarded-For`, an attacker can achieve an access control bypass attack by simply tampering with that request header when invoking the API request.
-<!--truncate-->
-## 问题描述
+<! --truncate -->
-在 Apache APISIX Dashboard 2.6 中，存在两个配置项：
+## Problem Description
-1. `conf.listen.host` 的配置项，用于指定 ManagerAPI 在启动时监听哪个 IP 地址，它的默认值为 `0.0.0.0` （默认监听外部网络请求）；
+In Apache APISIX Dashboard 2.6, there are two configuration entries.
-2. `conf.allow_list` 的配置项，用于进行访问控制，默认只允许 `127.0.0.1` （即本地网络）进行访问。
+1. the `conf.listen.host` configuration item, which specifies which IP address ManagerAPI listens to at startup, and which defaults to `0.0.0.0` (listens to external network requests by default).
-由于程序通过获取请求头 `X-Forwarded-For` 的值来进行访问控制判断，导致攻击者在调用 API 请求时，只需篡改该请求头即可实现访问控制绕过攻击。
+2. the configuration item `conf.allow_list`, which is used for access control and only allows access to `127.0.0.1` (i.e. local network) by default.
-## 影响版本
+Since the program makes access control determinations by obtaining the value of the request header `X-Forwarded-For`, an attacker can achieve an access control bypass attack by simply tampering with this request header when invoking an API request.
+
+## Affected Versions
Apache APISIX 2.6.0
-## 解决方案
+## Solution
-该问题已在 2.6.1 版本中解决，请尽快更新至最新版本，并在部署程序后修改默认用户名与密码。
+This issue has been resolved in version 2.6.1. Please update to the latest version as soon as possible and change the default username and password after deploying the application.
-## 漏洞详情
+## Vulnerability details
-漏洞公开时间：2021 年 6 月 8 日
+Vulnerability public date: June 8, 2021
-CVE 详细信息：https://nvd.nist.gov/vuln/detail/CVE-2021-33190
+CVE details: https://nvd.nist.gov/vuln/detail/CVE-2021-33190
-## 贡献者简介
+## Contributor Profile
-该漏洞是由平安科技银河安全实验室的 Vern 发现，并向 Apache 软件基金会上报该漏洞。感谢 Vern 和平安科技银河安全实验室对 Apache APISIX 社区的贡献。
+This vulnerability was discovered by Vern at Ping An Technology Galaxy Security Lab and reported to the Apache Software Foundation. Thanks to Vern and Ping An Technology Galaxy Security Lab for their contributions to the Apache APISIX community.
-
+! [2021-06-17-1](/img/blog_img/2021-06-17-1.jpeg)
-## 拓展阅读
+## Expanded Reading
-[Apache APISIX 贡献者专访 | 普华永道华南数据安全与隐私保护团队高级安全顾问王鹏诚](./2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md)
+[Apache APISIX Contributor Interview | Pengcheng Wang, Senior Security Consultant, PwC South China Data Security & Privacy Team](. /2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and- Privacy-Protection-Team.md)
Review comment:
```suggestion
[Apache APISIX Contributor Interview | Pengcheng Wang, Senior Security Consultant, PwC South China Data Security & Privacy Team](./2021-01-11-interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and- Privacy-Protection-Team.md)
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
Review comment:
```suggestion
**Shuyang**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
Review comment:
```suggestion
**Shuyang**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
Review comment:
```suggestion
The system is similar but there is no unified solution, which has been blank for more than ten years.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
-
+## Sharing Guest: Zeping Bai
-**Q：泽平，你好，请做个简单的自我介绍吧。**
+! [Zeping Bai](https://static.apiseven.com/202108/1630546751119-8df77cd8-6be0-4f8e-af13-182e77462d73.png)
-**泽平**：我是白泽平，目前在天津商业大学工商管理专业大三年级。从我初中时开始我就在自学编程了，它也成了我的兴趣之一。我擅长的领域主要是后端、Web 前端开发，曾经还客串过 Android 开发，主要使用 Golang、PHP 和 Javascript。
+**Q: Hi Zeping, please do a brief introduction of yourself.**
-**Q：去年你为什么会选择参加编程之夏，选择 Apache APISIX 的项目?**
+**Zeping**: I'm Zeping Bai, I'm currently in my junior year of Business Administration at Tianjin University of Commerce. I've been teaching myself programming since I was in junior high school, and it's become one of my hobbies. I specialize in back-end, web front-end development, and once guest-hosted Android development, mainly using Golang, PHP and Javascript.
-**泽平**：之前在使用 Apache APISIX 网关控制面板时发现了一些没有支持到的功能，于是提交了一些代码完善了这块的功能，社区的大佬们很给力，能让我学到不少东西，这给了我参与开源项目的动力。在去年编程之夏活动开始之前我申请了其他社区项目的 GSoC，但没有被选中，后来看到编程之夏 2020 的活动宣传时，就报名参加了。
+**Q: Why did you choose to participate in Summer of Programming last year and choose the Apache APISIX project?**
-**Q：今年你成为了 Apache APISIX 项目导师，对于项目申请有哪些 tips 可以给到大家？**
+**Zephyr**: When I was using the Apache APISIX gateway control panel, I found some features that were not supported, so I submitted some code to improve the functionality of this piece. I applied for GSoC for other community projects before the Summer of Programming event started last year, but was not selected, and then when I saw the Summer of Programming 2020 event advertised, I signed up for it.
-**泽平**：在项目申请书中主要描述一下你关于当前项目方案的想法或相关的技术路线，同时还要简要描述一下实现项目目标的过程（从每一个小模块出发逐步实现项目目标）和大致所需的时间。其余的信息需要如个人介绍等。以上内容可以帮助我们快速的你的能力和项目方案，有助于项目申请。同时还可以提前与项目导师联系，了解更全面的项目信息。
+**Q: This year you became an Apache APISIX project mentor, what tips can you give to people about applying for the project?**
-**Q：泽平，今年你成为了社区项目的导师，关于这个角色的转变，有什么想和大家分享一下的吗？**
+**Zephyr**: In the project application, mainly describe your idea about the current project proposal or the related technical route, and also briefly describe the process of achieving the project goals (starting from each small module to achieve the project goals step by step) and the approximate time required. The rest of the information needed such as a personal introduction, etc. The above can help us to get a quick idea of your capabilities and project proposal, which will help the project application. You can also contact the project supervisor in advance to get more comprehensive information about the project.
-**泽平**：去年作为学生参加编程之夏活动时，得到了不少指导与帮助，如果你今年选择参加 Apache APISIX 社区的项目，我同样也会为你提供帮助，让你更快的上手项目开发。
+**Q: Zephyr, you became a mentor for the community program this year, is there anything you would like to share with us about this change in role?**
-**Q：对想参加编程之夏 2021 的大学生，你有什么话想对各位同学说？**
+**Zeping**: I received a lot of guidance and help when I participated in the programming summer as a student last year, and if you choose to participate in the Apache APISIX community project this year, I will likewise provide you with help to get started with project development faster.
-**泽平**：编程之夏能磨练你的技术，还能帮助你更快地入门开源项目的协作，参与到开源项目中去。申请项目机会很多同时提交的材料也并不困难，希望大家不要犹豫，踊跃参加！
+**Q: What would you like to say to all the students who want to participate in Summer of Programming 2021?**
+
+**Zephyr**: Programming Summer can sharpen your skills and also help you get started faster in collaborating and participating in open source projects. There are many opportunities to apply for the program while the submissions are not difficult, so I hope you won't hesitate to participate!
Review comment:
```suggestion
**Zeping**: Programming Summer can sharpen your skills and also help you get started faster in collaborating and participating in open source projects. There are many opportunities to apply for the program while the submissions are not difficult, so I hope you won't hesitate to participate!
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
Review comment:
```suggestion
The architecture is hard to choose.
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
Review comment:
```suggestion
**Shuyang**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/03/experience-share-from-Apache-APISIX-committer.md
##########
@@ -1,76 +1,75 @@
---
-title: "来自 Apache APISIX committer 的经验分享 —— 编程之夏专访"
+title: Experience sharing from Apache APISIX committer - Interview with Summer of Programming
author: "赵若妃"
authorURL: "https://github.com/Serendipity96"
authorImageURL: "https://avatars.githubusercontent.com/u/23514812?v=4"
keywords:
-- 开源之夏
- APISIX
-- 开源社区
-- 经验分享
-description: 本次采访邀请到了 Apache APISIX 的 committer，分享参与开源项目的心得体会
+- Open Source
+description: In this interview, we invited Apache APISIX committer to share his experience of participating in open source projects.
tags: [Interview]
---
-> 本次采访邀请到了去年参加编程之夏的两位同学，两位同学现在都是 Apache APISIX 的 committer，也是今年社区项目的导师
-<!--truncate-->
+> This interview features two students who participated in last year's programming summer, both of whom are now Apache APISIX committers and mentors for this year's community project
-## 分享嘉宾：吴舒旸
+<! --truncate-->
-
+## Guest speaker: Shuyang Wu
-**Q：舒旸，请简单介绍一下自己。**
+Shuyang Wu! [yiyiyimu](https://static.apiseven.com/202108/1630546588578-2d8386cd-06c0-4c71-848a-8ed0e1263a4e.png)
-**舒旸**：Hello，大家好~ 我是吴舒旸（Github ID: yiyiyimu），去年本科毕业于上海交通大学环境学院，今年八月会在佐治亚理工学院开始读计算机硕士。现在在 APISIX 背后的商业公司——支流科技全职维护开源社区，也是 Apache APISIX 和 Chaos Mesh 两个项目的 committer。去年参与“编程之夏 2020”在 Apache APISIX 完成了“支持 etcd v3 协议”这个项目，这也作为了 APISIX v2.0 的主要更新点，之后也有幸被评上了“编程之夏 2020”的优秀学生，今年也会作为 mentor 继续参与“编程之夏 2021”。
+**Q: Shuyang Wu, please briefly introduce yourself.**
-**Q：去年为什么会选择参加编程之夏？**
+**Shuyang Wu (Github ID: yiyiyimu), graduated from Shanghai Jiaotong University's School of Environment last year, and will be starting a Master's degree in Computer Science at Georgia Tech this August. I am currently working full-time at Tributary Technology, the commercial company behind APISIX, to maintain the open source community, and I am also a committer for both Apache APISIX and Chaos Mesh projects. Last year, he completed the project "Support etcd v3 protocol" in Apache APISIX, which was the main update point of APISIX v2.0, and was honored to be awarded as one of the outstanding students of "Programming Summer 2020". After that, I was honored to be selected as an outstanding student of "Programming Summer 2020", and will continue to participate in "Programming Summer 2021" as a mentor this year.
-**舒旸**：去年因为疫情原因有时间可以在家陪父母，就想着尽量找可以远程实习的项目，运气很好找到了开源社区的活动（这里给我司打个广告，上班是完全远程工作的）。编程之夏相比 GSOC 和 Community Bridge，因为项目多并且每个项目都保证会有自己的 slot，可以说有着非常高的入选率了。**去年的数据是：397 的项目数，219 的被申请数，185 的中选数。基本有着 85% 的报名中选率，如果算上可以报名三个项目中选率就大于 99% 了，所以我这个 Github Contribution Graph 基本全白的人也可以入选。**
+**Q: Why did you choose to participate in Programming Summer last year?**
-**Q：舒旸去年为什么选择 Apache APISIX 的项目?**
+Yang **Shu**: Last year, I had time to stay home with my parents because of the epidemic, so I thought I would try to find a project where I could intern remotely, and I was lucky enough to find an open source community event (here is an advertisement for our company, we work completely remotely). Compared to GSOC and Community Bridge, Summer of Programming has a very high selection rate because there are many projects and each project is guaranteed to have its own slot. **Last year's numbers were: 397 projects, 219 applications, and 185 wins. If you include the three projects you can sign up for, the winning rate is more than 99%, so I, a person with an all-white Github Contribution Graph, can also be selected.**
-**舒旸**：我把去年会议上讲的 PPT 截出来了，对于有明确兴趣目标的同学，自然不需要考虑如何选择项目的问题。但如果像去年的我自己一样，看一圈项目下来发现都不怎么看得懂该怎么办呢。这个时候大家可能会去选择 star 数多的项目，但实际上 **star 数多只表明了这个项目的受欢迎程度，而不是能从社区中获得多少帮助的“社区活跃度”指标。活跃的社区在你两个阶段都会有所裨益，在入门时提供足够的帮助，也在后面维护社区时提供足够的反馈。**
+**Q: Why did Shuyang Wu choose the Apache APISIX project last year?** Q: Why did Shuyang Wu choose the Apache APISIX project last year?
-
+**Shuyang Wu**: I took a screenshot of the PPT from last year's conference. For those who have a clear goal of interest, naturally you don't need to think about how to choose a project. But if you're like me last year, you don't really understand what you're doing when you look at a project. At this point, you may choose a project with a high star count, but in fact **star count only indicates the popularity of the project, not the "community activity" indicator of how much help you can get from the community. An active community will benefit you at both stages, providing enough help to get started and enough feedback to maintain the community later.**!
-**舒旸**：**我当时选择的指标主要是 issue 回复情况（入门时碰到问题能否及时得到回复）、good first issue 数量（有没有好入手的 issue，既增加对项目的了解也可以多刷脸）以及 insights 指标（社区整体的活跃度）。** 今年我们在公司也写了一个查看[贡献者](https://github.com/api7/contributor-graph)情况的小工具，可以更直观的看到社区贡献者增长情况以及月度活跃贡献者多少，也是一个不错的选择指标。
+! [github introduction](https://static.apiseven.com/202108/1630546653087-23ff48eb-8e13-464c-874e-c4225cc32336.png)
-
+**Shuyang Wu**: **The metrics I chose at the time were issue response (whether you can get a timely response when you get started), good first issue (whether there is a good issue to start with, both to increase your understanding of the project and to brush up on your face), and insights (the overall activity of the community).** This year we also wrote a small tool to check the [contributors](https://github.com/api7/contributor-graph) situation in our company, so you can see more intuitively the growth of the community contributors and how many monthly active contributors, which is also a good choice of metrics.
-**舒旸**：去年参与 APISIX 之前我对于项目需要的技术栈包括 Lua/Openresty/etcd 甚至 API 网关都完全没有任何了解，但其实上手速度很快。借助文档把程序跑起来运行几个 demo 很快就可以完成，Lua 也半天就可以上手。这里再推荐一下 APISIX PMC moonming 大佬的两份 Openresty 入门必备，免费的 Openresty 电子书和付费的 Openresty 极客时间课程，当时入门从其中收获颇丰。
+! [join opensource](https://static.apiseven.com/202108/1630546703021-d63457b1-4068-45da-8bde-aa9c708c6793.png)
-**Q：社区活跃度对开源项目来说是非常重要的，舒旸介绍地非常详细。参加到 Apache APISIX 项目中，你最大的收获是什么？**
+**Shuyang Wu**: Before I got involved with APISIX last year, I had no knowledge of the technology stack required for the project, including Lua/Openresty/etcd and even API gateways, but I actually got up to speed very quickly. I was able to run a few demos with the help of the documentation, and I was able to get started with Lua in half a day. Here we recommend the APISIX PMC moonming big brother's two Openresty must-haves, the free Openresty e-book and the paid Openresty Geek Time course, from which we gained a lot at that time.
-**舒旸**：最大收获应该是第一次知道了**大型项目是如何运作的**。可能是因为转专业的缘故，不管是在学校做的还是自己做的项目都只能算是 toy project，参与开源社区是我第一次学习到一个在生产上使用的项目是如何开发和维护的。在社区中也会遇见各路大神以及热爱开源的小伙伴们，都是非常开心的经历。也非常感谢 mentor nic-chen 不厌其烦的指导我这个小白。
+**Shuyang Wu introduced this in great detail. What is your biggest takeaway from being a part of the Apache APISIX project?**
-**Q：舒旸是怎么成为 committer 的？可以跟大家分享一些你的经验吗？**
+**Shuyang Wu**: The most rewarding part was learning for the first time how a **large project works**. Probably because I changed my major, the projects I did at school or on my own were only toy projects, but participating in the open source community was the first time I learned how to develop and maintain a project for production use. It was a great experience to meet all kinds of gods and open source lovers in the community. Thanks to mentor nic-chen for guiding me through the process.
-**舒旸**：最主要的原因应该就是贡献了一个比较大的 feature。除此之外因为我们是开源社区嘛，分享合作都是非常重要的组成部分，在社区中帮助他人，回复 issue，review PR，以及在邮件列表中参与新 feature 的讨论都是参与社区很重要的部分。
+**Q: How did Shuyang Wu become a committer? Can you share some of your experience with us?**
-**Q：对想参加编程之夏 2021 的大学生，有什么想说的？**
+**Shuyang Wu**: The main reason is that I contributed a large feature, and because we are an open source community, sharing and collaborating is a very important part of the community, helping others, replying to issues, reviewing PRs, and participating in discussions about new features on the mailing list are all important parts of being involved in the community.
-**舒旸**：希望大家多多报名，不要有太多顾虑，多和社区交流，大家都非常友好的，好好享受这三个月的开发经历~
+**Q: What would you like to say to the students who want to participate in Summer of Programming 2021?**
-## 分享嘉宾：白泽平
+**Shuyang Wu**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience~.
Review comment:
```suggestion
**Shuyang**: I hope you'll sign up, don't have too many worries, talk to the community more, everyone is very friendly, and enjoy the three-month development experience.
```
##########
File path: website/blog/2021/06/06/apisix-two-years.md
##########
@@ -10,32 +10,32 @@ description: Apache APISIX is now two years old, thanks for all contributors.
tags: [Release]
---
-> Apache APISIX 开源 2 周年啦！
+> Apache APISIX is open for 2 years!
-<!--truncate-->
+<! --truncate-->
-今天是 2021 年 6 月 6 日，在这个 666 的日子 [Apache APISIX](https://github.com/apache/apisix) 开源 2 周年啦！🎉
+Today is June 6, 2021, and on this 666th day [Apache APISIX](https://github.com/apache/apisix) is 2 years old! 🎉
-Apache APISIX 于 2019 年 6 月 6 日开源，同年 10 月进入 Apache 孵化器，也是在这短短两年时间内，成为了 **Apache 顶级项目**！
+Apache APISIX was open sourced on June 6, 2019, and entered the Apache Incubator in October of the same year, and has become an **Apache top project** in just two years!
-在进入 Apache 孵化器之前，Apache APISIX 仅有 20 多个 contributor，现在和 Apache APISIX 有关的项目共有 249 个 contributor，在一年半的时间，**contributor 数量增长了 10 倍**！ Apache APISIX 的社区也非常活跃，截止到今天 **249 位 contributor 共提交了 2303 个 PR ，每个月都会发布一个新版本**。
+Before entering the Apache Incubator, Apache APISIX had just over 20 contributors, and now there are 249 contributors to projects related to Apache APISIX, a 10-fold increase in **contributors** in a year and a half! The Apache APISIX community is also very active, with **249 contributors submitting 2303 PRs as of today, and a new release every month**.
-
+
-生活中，当你去买机票、刷微博、买奶茶的时候，背后的关键流量都是由 Apache APISIX 来处理的。在这两年里， Apache APISIX 已经被非常多的企业广泛使用，涵盖金融、互联网、制造、零售、运营商等等，比如美国的航空航天局（NASA)、欧盟的数字工厂、中国航信、腾讯、华为、微博、贝壳找房、中国移动、泰康、360、奈雪的茶等等。点击查看 [Apache APISIX 的用户列表](https://github.com/apache/apisix)。
+In life, when you go to buy airline tickets, swipe Weibo, or buy milk tea, the critical traffic behind it is handled by Apache APISIX. In the past two years, Apache APISIX has been widely used by many enterprises, covering finance, Internet, manufacturing, retail, operators, etc., such as NASA in the US, Digital Factory in the EU, China Airlines, Tencent, Huawei, Weibo, Shell House, China Mobile, Taikang, 360, Nespresso Tea, etc. Click to view [list of users of Apache APISIX](https://github.com/apache/apisix).
-**2019 年 8 月，Apache APISIX 发布了第一个版本 0.6.0**。这个版本带来很多新的特性：健康检查、服务熔断、debug 模式，分布式追踪、JWT 认证等，以及内置的 dashboard。
+**In August 2019, Apache APISIX released its first version 0.6.0**. This release brought many new features: health checks, service fusion, debug mode, distributed tracing, JWT authentication, etc., and a built-in dashboard.
-**1.0 版本于 2020 年 1 月 发布，是 Apache APISIX 第一个生产版本。** 这个版本不仅支持了新特性——在 URI 相同的条件下根据 header、args、优先级等条件，来匹配到不同的上游服务，而且在代码稳定性、文档方面也更加完善，如：增加自定义开发插件的文档、Oauth 插件的使用文档、dashboard 编译的文档、如何进行 a/b 测试的文档、如何开启 MQTT 插件的文档等，说明 Apache APISIX 开始在越来越多的环境中被应用起来。
+Version **1.0 was released in January 2020 and was the first production release of Apache APISIX.** This version not only supports new features - matching to different upstream services based on header, args, priority, etc. with the same URI - but also improves code stability and documentation, such as adding documentation for custom development plugins, documentation for using the Oauth plugin, documentation for documentation for dashboard compilation, documentation on how to perform a/b testing, documentation on how to enable the MQTT plugin, etc., indicating that Apache APISIX is starting to be used in more and more environments.
-**每月发布一个新版本，我们是认真的！** 在 2020 年 10 月，我们发布了 2.0 版本。2.0 版本从 etcd v2 协议迁移到 v3，只支持 etcd 3.4 以及后续的版本，支持为上游对象增加标签，为上游、路由等资源增加更多字段，使用拦截器来保护插件的路由，支持 http 和 https 监听多个端口，增加 AK/SK(HMAC) 认证插件、 referer-restriction 插件。
+**A new release every month, and we mean it!** In October 2020, we released version 2.0. 2.0 migrates from etcd v2 protocol to v3, supports only etcd 3.4 and later, supports adding tags to upstream objects, adds more fields to upstream, routing and other resources, uses interceptors to protect the plugin's routes, supports http and https listening on multiple ports, adds AK/SK( HMAC) authentication plugin, referer-restriction plugin.
-**16 天前，我们发布了 APISIX 2.6 版本！** 在这个版本里，支持了大家呼声很高的新特性，如：**使用其他语言编写自定义插件，现在已经支持 Java 开发自定义插件，本月底还会支持使用 Go 开发自定义插件！** 除此之外，2.6 版本的生态已经完整支持 Nacos 服务发现，支持配置 IPv6 的 DNS resolver，支持修改 Prometheus 默认端口，不再暴露到数据面的端口上。
+**16 days ago, we released APISIX version 2.6!** In this version, new features that have been highly requested are supported, such as: **Writing custom plugins in other languages, custom plugins in Java are now supported, and custom plugins in Go will be supported at the end of this month!** In addition, version 2.6 of ecology has full support for Nacos service discovery, support for configuring DNS resolver for IPv6, and support for modifying the Prometheus default port so that it is no longer exposed to the data-plane port.
-Apache APISIX 的目标不只是做一个 API 网关，**Apache APISIX 希望做云原生时代四层和七层流量处理和连接者。** 在 Apache APISIX 里所有的配置都是动态的，这对于云原生时代的弹性伸缩以及多云的部署是非常重要的。我们相信 Apache APISIX 是云原生时代最好的选择。欢迎大家加入 Apache APISIX 的开源社区，欢迎大家使用 Apache APISIX！
+Apache APISIX aims to be more than just an API gateway, **Apache APISIX wants to be a Layer 4 and 7 traffic handler and connector in the cloud-native era.** All configurations in Apache APISIX are dynamic, which is important for elastic scaling and multi-cloud deployments in the cloud-native era. We believe that Apache APISIX is the best choice for the cloud-native era. Welcome to the Apache APISIX open source community, and welcome to Apache APISIX!
-Apache APISIX 的发展离不开社区里的每一个小伙伴，**特别感谢 Apache APISIX 社区的 contributor 和社区用户为 Apache APISIX 发展作出的贡献。**
+The development of Apache APISIX cannot be achieved without each and every one of the community members, **Special thanks to the contributors and users of the Apache APISIX community for their contributions to the development of Apache APISIX.**!
-Apache APISIX 2 周岁，生日快乐！
+Apache APISIX turns 2, happy birthday!
Review comment:
```suggestion
Apache APISIX is 2 years old now, happy birthday!
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
-右图部分就是 APISIX Mesh 的内部架构图。
+The diagram on the right shows the internal architecture of APISIX Mesh.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625024.png)
-聊了这么多 APISIX 的当下，也和大家聊聊 APISIX 的未来。
+After talking so much about the present of APISIX, let's also talk about the future of APISIX.
-因为 APISIX 目前是 Apache 基金会项目，所以它已经不再属于个人或公司，而是全人类共享财产。这样社区中的每一个你，都有权利决定他往哪个方向发展。
+Because APISIX is currently an Apache Foundation project, it is no longer the property of individuals or companies, but of all humanity. This gives every one of you in the community the right to decide which direction it will go.
-开源版本 APISIX 目前默认搭配的配置中心是 etcd ，虽然目前它依旧是最好的选择，但我们在和用户沟通时依然经常会听到是否支持其他配置中心，比较常见的原因是 etcd 这个产品太新了，公司现有运维产品支持列表中没有它。所以我们计划让 APISIX 可以与其他配置中心协作。
+The default configuration center for the open source version of APISIX is etcd, and while it is still the best choice, we still often hear about support for other configuration centers when we talk to users, more often than not because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers.
-
+! [APISIX data plane](https://static.apiseven.com/202108/20210625025.png)
-APISIX 已经走在全流量数据面这条路上，相信大家都会问一些问题，比如：为什么要统一流量转发？统一是否给企业带来价值？对技术人员有什么收益？带着这些问题，我们看下图：
+APISIX is already on the road to full traffic data plane, and I believe we all ask questions such as: Why do we need to unify traffic forwarding? Does unification bring value to the enterprise? What are the benefits to the technical staff? With these questions in mind, let's look at the following diagram.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625026.png)
-统一本身不是目标，统一之后的收益才是我们追求的背后逻辑，下面分别给出几个不同角度来分别阐述。
+Unification itself is not the goal, but the benefits after unification is the logic behind our pursuit, and several different perspectives are given below to elaborate separately.
-- 运维角色：使用相同的运维工具收集日志、Metric 指标等，复用已有积累；
+- Operation and maintenance role: use the same operation and maintenance tools to collect logs, Metric metrics, etc., and reuse existing accumulations.
-- 开发角色：基于标准化的 APISIX 插件开发，能力可以方便复用，并且积累的经验可以应用到 LB、API Gateway、K8s Ingress 等不同产品线；
+- Development role: based on standardized APISIX plug-in development, the capabilities can be easily reused, and the accumulated experience can be applied to different product lines such as LB, API Gateway, K8s Ingress, etc.
-- 公司价值：统一技术栈，降低公司运营成本，降低过渡到微服务、云原生的难度，加速企业数字化转型。
+- Company value: Unify technology stack, reduce company operation cost, reduce the difficulty of transitioning to microservices and cloud-native, and accelerate enterprise digital transformation.
-
+! [connect APISIX](https://static.apiseven.com/202108/20210625027.png)
-最后是 APISIX 的 QQ 群，有任何问题都可以在这里或者 [Github issue](https://github.com/apache/apisix/issues) 留言，会有专人快速响应，再次感谢大家。
+Last but not least is the APISIX QQ group, any questions can be left here or on [Github issue](https://github.com/apache/apisix/issues), there will be someone to respond quickly, thanks again.
Review comment:
change qq to slack channel if possible
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
Review comment:
```suggestion
The left and right of this diagram are DP (Data Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
-右图部分就是 APISIX Mesh 的内部架构图。
+The diagram on the right shows the internal architecture of APISIX Mesh.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625024.png)
-聊了这么多 APISIX 的当下，也和大家聊聊 APISIX 的未来。
+After talking so much about the present of APISIX, let's also talk about the future of APISIX.
-因为 APISIX 目前是 Apache 基金会项目，所以它已经不再属于个人或公司，而是全人类共享财产。这样社区中的每一个你，都有权利决定他往哪个方向发展。
+Because APISIX is currently an Apache Foundation project, it is no longer the property of individuals or companies, but of all humanity. This gives every one of you in the community the right to decide which direction it will go.
-开源版本 APISIX 目前默认搭配的配置中心是 etcd ，虽然目前它依旧是最好的选择，但我们在和用户沟通时依然经常会听到是否支持其他配置中心，比较常见的原因是 etcd 这个产品太新了，公司现有运维产品支持列表中没有它。所以我们计划让 APISIX 可以与其他配置中心协作。
+The default configuration center for the open source version of APISIX is etcd, and while it is still the best choice, we still often hear about support for other configuration centers when we talk to users, more often than not because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers.
-
+! [APISIX data plane](https://static.apiseven.com/202108/20210625025.png)
-APISIX 已经走在全流量数据面这条路上，相信大家都会问一些问题，比如：为什么要统一流量转发？统一是否给企业带来价值？对技术人员有什么收益？带着这些问题，我们看下图：
+APISIX is already on the road to full traffic data plane, and I believe we all ask questions such as: Why do we need to unify traffic forwarding? Does unification bring value to the enterprise? What are the benefits to the technical staff? With these questions in mind, let's look at the following diagram.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625026.png)
-统一本身不是目标，统一之后的收益才是我们追求的背后逻辑，下面分别给出几个不同角度来分别阐述。
+Unification itself is not the goal, but the benefits after unification is the logic behind our pursuit, and several different perspectives are given below to elaborate separately.
-- 运维角色：使用相同的运维工具收集日志、Metric 指标等，复用已有积累；
+- Operation and maintenance role: use the same operation and maintenance tools to collect logs, Metric metrics, etc., and reuse existing accumulations.
Review comment:
```suggestion
- Operation and maintenance role: use the same operation and maintenance tools to collect logs, metrics, etc., and reuse existing accumulations.
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
-右图部分就是 APISIX Mesh 的内部架构图。
+The diagram on the right shows the internal architecture of APISIX Mesh.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625024.png)
-聊了这么多 APISIX 的当下，也和大家聊聊 APISIX 的未来。
+After talking so much about the present of APISIX, let's also talk about the future of APISIX.
-因为 APISIX 目前是 Apache 基金会项目，所以它已经不再属于个人或公司，而是全人类共享财产。这样社区中的每一个你，都有权利决定他往哪个方向发展。
+Because APISIX is currently an Apache Foundation project, it is no longer the property of individuals or companies, but of all humanity. This gives every one of you in the community the right to decide which direction it will go.
-开源版本 APISIX 目前默认搭配的配置中心是 etcd ，虽然目前它依旧是最好的选择，但我们在和用户沟通时依然经常会听到是否支持其他配置中心，比较常见的原因是 etcd 这个产品太新了，公司现有运维产品支持列表中没有它。所以我们计划让 APISIX 可以与其他配置中心协作。
+The default configuration center for the open source version of APISIX is etcd, and while it is still the best choice, we still often hear about support for other configuration centers when we talk to users, more often than not because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers.
-
+! [APISIX data plane](https://static.apiseven.com/202108/20210625025.png)
Review comment:
```suggestion
```
##########
File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md
##########
@@ -1,176 +1,176 @@
---
-title: "有了 NGINX 和 Kong，为什么还需要 Apache APISIX"
-author: "王院生"
+title: Why do you need Apache APISIX when you have NGINX and Kong?
+author: Yuansheng Wang
authorURL: "https://github.com/membphis"
authorImageURL: "https://avatars.githubusercontent.com/u/6814606?v=4"
keywords:
- APISIX
- Kong
- Nginx
-- API 网关
-- 开源
-description: 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+- API Gateway
+- Open Source
+description: This article describes the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
tags: [Technology]
---
-> 本文介绍了 Apache APISIX 架构演进历史，对比 Nginx 和 Kong 这两个框架 Apache APISIX 的优势是什么。
+> This article describes the history of the evolution of the Apache APISIX architecture and compares what the advantages of the two frameworks, Apache APISIX and Nginx, are.
-<!--truncate-->
+<! --truncate -->
> Source: https://www.apiseven.com/zh/blog/why-we-need-Apache-APISIX
-大家好，非常开心给大家分享一个让我激动的主题《有了 NGINX 和 Kong，为什么还需要 Apache APISIX》。
+Hello everyone, I'm happy to share a topic that I'm excited about, "Why do you need Apache APISIX when you have NGINX and Kong".
-
+! [why we need APISIX](https://static.apiseven.com/202108/20210625001.png)
-之所以我们要做 NGINX 和 Kong 的替代项目，实际和我们后端架构演变史大背景息息相关，我会先和大家一起分享后端架构演变过程，这非常重要。
+The reason why we are doing a replacement project for NGINX and Kong is actually related to the background of our backend architecture evolution, and I will start by sharing with you the backend architecture evolution process, which is very important.
-
+I'll start by sharing with you the evolution of the backend architecture, which is very important. [membphis](https://static.apiseven.com/202108/20210625002.png)
-首先做下自我介绍，本人叫王院生。和这次大会主办者净超一样我们都做社区很久，我在 2015 年写了一本电子书叫《OpenResty 最佳实践》，通过这本书结成了一个超万人社区。从那个时候开始个人对开源本身越发感兴趣，2015 年以前我基本上主要是开源软件的使用者，然后慢慢变成社区的一个协办者，再往后变成社区领导者，也许你会问为什么？很简单，因为这本书是你写的，别人遇到各种各样的问题，有高级的也有比较普通的，问得多了我就逐步成为老师并最终成了社区领导者，像那句名言“走的人多了，也变成了路”。
+First of all, I would like to introduce myself, my name is Wang Yansheng. I wrote an e-book called "OpenResty Best Practices" in 2015 and formed a community of over 10,000 people through this book. Since that time, I have become more and more interested in open source itself. Before 2015, I was basically mainly a user of open source software, then slowly became a co-organizer of the community, and then later became a community leader. Simple, because the book is written by you, others encounter a variety of problems, there are advanced and more common, ask more I gradually became a teacher and eventually became a community leader, like the famous saying "walk more people, also become the road.
-
+I've been a teacher and eventually a community leader. [api7.ai](https://static.apiseven.com/202108/20210625003.png)
-2019 年我与合伙人温铭一起创办了深圳支流科技公司，它是一家以开源为依托的商业化公司。这家公司承载了我俩很多个人理想，也可以说是在做每一位普通程序员的理想，不想庸庸碌碌 996，我经常对别人说我的梦想就是“把我的名字刻入史册”，悲催的是人类已经不需要史册了。
+In 2019, I founded Shenzhen Tributary Technology Company with my partner Ming Wen, which is an open source-based commercialization company. This company carries a lot of personal ideals for both of us, and we can also say that we are doing the ideals of every ordinary programmer, not wanting to be mediocre 996, I often say to others that my dream is to "engrave my name into the history books", the sad thing is that human beings no longer need the history books.
-
+The sad thing is that mankind doesn't need a history anymore. [api7.ai team](https://static.apiseven.com/202108/20210625004.png)
-这是我们团队，大家主要是远程协作，所有人聚在一起比较难。公司早期阶段只有五六个人时，还能比较容易的把团队聚起来，但从今年之后就一直没聚齐过，这是我们今年到目前以来最齐的一次（但依然有几位同学没能一起）。
+This is our team, we mainly collaborate remotely, and it's harder to get everyone together. When there were only five or six people in the early stages of the company, it was relatively easy to get the team together, but it hasn't been together since this year, and this is the most together we've had so far this year (but there are still a few students who didn't make it together).
-作为一家技术说了算的商业公司，技术在我司有非常大的话语权，尊重技术从尊重技术人才开始。没有 996 ，没有上班打卡，远程办公，欢迎感兴趣的同学联系我们，期待有梦想、有理想的你加入我司。
+As a technology-driven business company, technology has a very big say in our company, and respect for technology starts with respect for technical talents. There is no 996, no punching in and out, remote office, welcome interested students to contact us, look forward to dreaming and ideal you to join our company.
-
+We are looking forward to your dream and ideal to join us. [APISIX architecture](https://static.apiseven.com/202108/20210625005.png)
-这次演讲主题需要一些背景，我们先说说后端架构演变史。先跟大家回顾一下这张图，右图部分从上到下它不是具体数据流程图，它是我们后端架构演变史。从最传统的单体大应用，然后变成面向服务架构(SOA)，然后是微服务，分别出现了 Spring Cloud 和 Kubernetes。Spring Cloud 架构主要服务 JAVA 语言开发者，Kubernetes 是容器编排支持任何语言，以及最近社区比较热的话题服务网格。
+The topic of this talk needs some background, so let's start with the history of back-end architecture evolution. First, let's review this diagram, the right part from top to bottom it is not a specific data flow diagram, it is the history of our backend architecture evolution. Spring Cloud architecture mainly serves JAVA language developers, Kubernetes is a container orchestration to support any language, as well as the recent community hot topic service grid.
-我经常跟公司同事说，咱们展望未来五年，甚至是十年之后，哪个架构是最终极方案？从目前信息看，服务网格会大概率胜出。即使当下它还有很多问题，但我相信这些问题都能被解决。
+I often say to colleagues, let's look at the next five years, or even ten years later, which architecture is the ultimate solution? From the current information, the service grid will probably win. Even if it still has many problems, I believe they can be solved.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625006.png)
-在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 SOA 也就是面向服务的架构，引入反向代理组件，选型通常是 NGINX，HAProxy。迭代到微服务架构后，通常会选择一些更现代的 API 网关产品，比如 Kong、Traefik ，当然也有一些用户因为惯性习惯，还会继续选择使用 NGINX，虽然它有能力弱、使用不方便等缺点，但胜在稳定、可靠。说句题外话，从全球市场占有率看，NGINX 成为占有率最高的 Web Server 是在 2019 年 4 月份，感兴趣的同学可以到看下最新的 netcraft 报告 April 2021 Web Server Survey。
+At the beginning of the venture, it was particularly interesting to go through this diagram in my head. We were able to see that as we gradually iterated on the back-end architecture, we introduced a variety of different components. For example, when we got to SOA, which is a service-oriented architecture, we introduced reverse proxy components, usually NGINX and HAProxy, and when we iterated to microservice architecture, we usually chose some more modern API gateway products, such as Kong and Traefik, and of course, some users would continue to use NGINX because of their habitual habits. Although it has weaknesses such as weaknesses and inconveniences, but it is stable and reliable. On a side note, from a global market share perspective, NGINX became the most dominant Web Server in April 2019.
-随着后端架构持续迭代，进入到了 Kubernetes 时代后，流量出入口 Ingress 大家默认会使用官方的 Kubernetes Ingress，这个项目是基于 NGINX 本地配置文件。在国内也有一些公司在使用 Traefik 作为 Ingress，这与国内 Golang 开发者基数比较大有很大关系。
+As the backend architecture continues to iterate and enters the Kubernetes era, the traffic portal Ingress will use the official Kubernetes Ingress by default, which is based on the NGINX local configuration file. Some companies in China are also using Traefik as Ingress, which has a lot to do with the large base of Golang developers in China.
-我们再看看左侧比较有意思的 JAVA ，Spring Cloud 内置 API 网关先后经历了 ZUUL、ZUUL2，但还是不好用，性能、架构官方都不满意，所以 Spring Cloud 官方发起了新项目 Spring Cloud Gateway，最终形成全家桶解决方案。
+Let's look at the left side of the more interesting JAVA, Spring Cloud built-in API gateway has experienced ZUUL, ZUUL2, but still not good, performance, architecture official are not satisfied, so Spring Cloud official launched a new project Spring Cloud Gateway, the final formation of the family bucket solution.
-最后说说右下角部分的服务网格，对于服务网格已经形成一种选择就是 istio(CP) + envoy(DP)。后面我们又看到了阿里巴巴开源的 mosn，一句话概括：Golang 版本的 envoy。
+Finally, the bottom right part of the service grid, for the service grid has formed a choice istio (CP) + envoy (DP). Later we see the Alibaba open source mosn, in a nutshell: Golang version of envoy.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625007.png)
-回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。
+Reviewing the previous architecture evolution diagram, I believe many students have found out where the problem is. From top to bottom, from left to right, for different scenarios, we finally "reasonably" introduced various components to solve our problems, the architect's rule of survival: choose the most suitable at the moment.
-当我们趁手工具不多，在功能、动态、性能等之间我们总是要妥协放弃一些，大家早已习惯甚至麻木。IT 技术发展迅速，时至今日它们是否还是最合适方案？5G、物联网等发展迅速，如何弹性扩缩容、动态统一管理等新问题，逼着我们重新思考。
+When we have few tools at hand, we always have to compromise between functionality, dynamics, performance, etc. We have long been accustomed to and even numb to the rapid development of IT technology, are they still the most appropriate solution today?
-
+! [Nginx](https://static.apiseven.com/202108/20210625008.png)
-如图这些都是 NGINX 缺点，比如 NGINX 的低活跃度社区。虽然我们可以在公司层面投入更多资源，但他的社区是真不友好，不友好到什么程度呢？上面这张图可以看得到，NGINX 在 Github 的仓库只是镜像，issue 功能是关闭的，想提交 issue 不可能了，即使你提交 PR 官方也是不会合并的。
+As you can see, these are NGINX drawbacks, such as NGINX's low activity community. While we could invest more resources at the corporate level, his community is really unfriendly, and how unfriendly is it? As you can see in the picture above, the NGINX repository in Github is only a mirror, the issue function is closed, it is impossible to submit an issue, and even if you submit a PR the official will not merge it.
-除此之外 NGINX 自身路由比较弱，比如说我要根据某个请求参数比如 id 取模运算做灰度，你会发现 NGINX 完全无法实现。所以我们能看到很多小的开源系统，只要解决了上面的灰度场景，就可以是个独立开源项目。此外 gRPC 调用在微服务调用中越来越流行，但 NGINX 对它的支持只能是“简单能用”。
+In addition, NGINX is weak in its own routing, for example, I want to do grayscale based on a request parameter such as id, you will find that NGINX is completely unable to achieve. So we can see a lot of small open source systems, as long as the above grayscale scenario is solved, it can be an independent open source project. In addition, gRPC calls are becoming more and more popular in microservice calls, but NGINX support for it is only "simple to use".
-最后就是 NGINX 集群统一管理，几乎每家互联网厂商都有自己的 NGINX 配置管理系统，系统虽然大同小异但就是没有统一方案，十几年了一直空白。
+Finally, the NGINX cluster management, almost every Internet vendor has its own NGINX configuration management system, although the system is similar but there is no unified solution, more than a decade has been blank.
-
+The system is similar but there is no unified solution, which has been blank for more than ten years. [Kong](https://static.apiseven.com/202108/20210625009.png)
-在进一步聊 Kong 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 Kong 不完全满足第二条，官方主推的 PostgreSQL 关系型数据库是单点，无法支持弹性扩缩容，是它架构选型硬伤。
+Before talking further about Kong, I would like to talk to you about what is cloud-native. This term has been around for a long time, but there is no unified and clear definition until now. I synthesize several cloud vendors' definitions and outline two main cloud-native features: first, it should support containers, and second, it should support elastic and scalable deployment. I think Kong does not fully meet the second, the official main PostgreSQL relational database is a single point, can not support elastic expansion and contraction of capacity, is its architecture selection hard.
-
+The architecture is hard to choose. [Nginx Kong](https://static.apiseven.com/202108/20210625010.png)
-最后简单总结一下 NGINX 和 Kong 的问题：
+Finally, a brief summary of the problems with NGINX and Kong.
-- NGINX 和 Kong 都有各自不同应用场景；
+- NGINX and Kong both have their own different application scenarios.
-- NGINX 缺少官方集群统一管理方案；
+- NGINX lacks an official cluster management solution.
-- Kong 的控制面不是完全云原生架构。
+- Kong's control plane is not completely cloud-native architecture.
-在介绍 APISIX 之前，还是有必要先感谢两位前辈，站在巨人肩膀思考，确实让我们从一开始就有更高起点。APISIX 已经两岁多，请看架构图：
+Before introducing APISIX, it is necessary to thank the two predecessors for thinking on the shoulders of giants, which really gives us a higher starting point from the beginning.
-
+! [APISIX architecture](https://static.apiseven.com/202108/20210625011.png)
-这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。
+The left and right of this diagram are DP (Date Plane) and CP (Control Plane), which are the same as the familiar backend service system. APISIX did not try to build something new by itself from the first day of the architecture, so we chose the most mature etcd for the configuration center.
-在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 APISIX 正常对外提供服务的能力。当整体架构中的每一个点都支持高可用时，用户生产系统的高稳定性就非常容易实现。
+In this architecture, you can't find a single point. Any abnormal downtime of any of the services here will not affect APISIX's ability to provide services to the public. When every point in the overall architecture supports high availability, the high stability of the user's production system is very easy to achieve.
-
+! [APISIX eco](https://static.apiseven.com/202108/20210625012.png)
-这是 APISIX 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 7 层协议有 HTTP(S)、HTTP2、Dubbo、QUIC 和物联网协议 MQTT 等，4 层协议有 TCP/UDP 。右侧部分则是一些开源或者 SaaS 服务，比如 SkyWalking、Prometheus 、Vault 等。下面就是一些比较常见的操作系统环境、云厂商和硬件环境，作为一家全球化公司，我们也支持 ARM64 等更丰富的平台。
+This is a diagram of the APISIX eco, from which you can see exactly what peripheral ecologies are currently supported. On the left side are the supported protocols, you can see the common Layer 7 protocols such as HTTP(S), HTTP2, Dubbo, QUIC and IoT protocol MQTT, and the Layer 4 protocols such as TCP/UDP. On the right are some open source or SaaS services such as SkyWalking, Prometheus, Vault, etc. Below are some of the more common OS environments, cloud vendors and hardware environments. As a global company, we also support richer platforms such as ARM64.
-
+! [APISIX Advantages](https://static.apiseven.com/202108/20210625013.png)
-给大家简单地汇报一下 APISIX 当前状态，APISIX 从开源到现在两年的时间，APISIX 已经成为了全世界最活跃的开源 API 网关项目，而且这个状态已经持续了一年多。请记住最下面一句话，APISIX 已经**生产可用，功能、性能、架构全面优于 Kong**。在 2019 年 9 月份贝壳找房就已经把 APISIX 项目用到生产环境。
+To give you a brief report on the current state of APISIX, APISIX has become the most active open source API gateway project in the world in the two years since it became open source, and this state has been going on for more than a year. Remember the bottom sentence, APISIX has been **production available, with better features, performance, and architecture across the board than Kong**. In September 2019 Shell has already used the APISIX project in production environments.
-
+APISIX Community [APISIX Community](https://static.apiseven.com/202108/20210625014.png)
-简单解释一下这张图，可以叫它贡献者增长曲线。横坐标是时间线，纵坐标是贡献者总数。能够看到 APISIX 和 Kong 这两个项目相对更活跃，APISIX 的增长速度从开源第一天就保持着非常不错的增长率，在接近 Kong 两倍的速度成长，可见 APISIX 受欢迎程度。当然评价一个项目活跃度还有很多其他方法，比如查看每月活跃 issue、PR 总数等方式，很开心的和大家说，这些方式看 APISIX 的活跃度依然第一。
+To briefly explain this graph, you can call it a contributor growth curve. The horizontal coordinate is the timeline and the vertical coordinate is the total number of contributors. We can see that APISIX and Kong are two relatively more active projects. APISIX has been growing at a very good rate since the first day of open source, and is growing at nearly twice the rate of Kong, which shows how popular APISIX is. Of course there are many other ways to evaluate the activity of a project, such as checking monthly active issues, PR totals, etc. I'm happy to say that APISIX is still number one in terms of activity in these ways.
-
+APISIX is still number one in these ways! [APISIX Advantages](https://static.apiseven.com/202108/20210625015.png)
-经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 NGINX C 和 Lua 这两个技术栈是空白。前些日子 APISIX 已经正式宣布支持多语言，目前已经支持了 Java 语言，后续也将逐步支持 Golang 、Rust、NodeJS 等语言。
+After our actual customer visits, the feature of supporting multiple languages is very necessary. After all, for many companies, they have their own familiar technology stacks, and many companies are blank for NGINX C and Lua. APISIX has officially announced multilingual support a few days ago, and currently supports Java, and will gradually support Golang, Rust, NodeJS and other languages.
-APISIX 的全动态、高性能，其实和高质量的周边生态是分不开的。APISIX 的路由使用我司主导并开源的项目叫 resty-radixtree ，简单来说它使用 radixtree 方式完成路由匹配，匹配效率相比竞品提升了一到两个数量级。其他还有 jsonschema、ipmatcher 等周边库，它们都比同类开源项目性能强几个数量级。
+APISIX's full dynamic and high performance is actually inseparable from the high quality of the surrounding ecology. Other peripheral libraries such as jsonschema, ipmatcher, etc. are several orders of magnitude better than similar open source projects.
-
+! [APISIX arch](https://static.apiseven.com/202108/20210625016.png)
-APISIX 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。
+APISIX support for multi-language features have been put into the open source project, interested students are welcome to follow and participate at any time. The advantage of this implementation is that it is simple and universal, and everyone can natively use their familiar language.
-
+! [Apache APISIX](https://static.apiseven.com/202108/20210625017.png)
-聊了这么多，给大家介绍下 APISIX 有哪些优势？请看上图。
+After all this talk, what are the advantages of APISIX for you? See the image above.
-前面三个（基金会项目、安全、稳定）我觉得是最重要的，作为基金会项目，它已经不属于某个人或某家公司，而是全人类的财产，我们可以永远使用它。与之相对应的是商业公司开源项目，它可以随时修改开源项目 License，大家最近都听过类似的消息。APISIX 的安全和稳定得益于它的基石 NGINX，能够成为目前最流行、使用量最广的 web server，底蕴还是很厉害的。
+The first three (foundation project, security, stability) I think are the most important. As a foundation project, it no longer belongs to a person or a company, but is the property of all mankind, and we can use it forever. The security and stability of APISIX is due to its cornerstone, NGINX, which has become the most popular and widely used web server, and its heritage is still very impressive.
-高性能、动态、社区活跃是 APISIX 的王牌，它们已经形成了良性互动。
+High performance, dynamics, and an active community are the trump cards of APISIX, and they have formed a healthy interaction.
-如果一句话概括 APISIX 的自豪，我认为是：**APISIX，全世界最活跃的 API 网关项目**。在此共识下，我们把更多资源倾斜给社区，我们相信社区会让 APISIX 稳健健康成长。
+If one sentence sums up the pride of APISIX, I think it is:**APISIX, the most active API gateway project in the world**. With this consensus, we tilt more resources to the community, and we believe the community will make APISIX grow soundly and healthily.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625018.png)
-看到这张图台下的你估计一下子就明白了 APISIX 要干什么。APISIX 目标：**统一代理基础设施**。
+The APISIX goal: **Unified Proxy Infrastructure**.
-也许台下的你这里会有疑问：APISIX 要支持这么多场景，是否会让 APISIX 变得四不像？这里我简单解释一下，APISIX 的核心是高性能代理服务，自身不绑定任何环境属性。当它演变为 Ingress、服务网格等产品，都是外部服务与 APISIX 配合，变化的是外部程序而不是 APISIX 自身，后面逐步为大家说明 APISIX 是如何具体支持这些场景。
+You may be wondering if APISIX is going to support so many scenarios. Here I will explain briefly that the core of APISIX is a high-performance proxy service that does not bind any environment properties itself. When it evolves into Ingress, Service Grid, etc., it is the external service that works with APISIX, and it is the external program that changes rather than APISIX itself, and we will explain how APISIX supports these scenarios step by step.
-
+! [API gateway](https://static.apiseven.com/202108/20210625019.png)
-针对传统的 LB 和 API Gateway 场景，APISIX 比较大的优势就是从静态变成全部动态，再也不需要 reload，要知道很多科技公司的 NGINX reload 是半小时起步。前面提到的根据请求 id 取模运算灰度场景，在 APISIX 里使用精细化路由可以很容易完成。
+For traditional LB and API Gateway scenarios, APISIX has the advantage of going from static to all dynamic, no more reloads, as many tech companies start with a half hour NGINX reload. The aforementioned grayscale scenario of moduloing based on request id can be easily done in APISIX using fine-grained routing.
-
+! [API gateway](https://static.apiseven.com/202108/20210625020.png)
-
+! [APISIX Ingress Controller](https://static.apiseven.com/202108/20210625021.png)
-APISIX Ingress Controller 则完整解决了上面提到的所有问题，继承了 APISIX 的所有优势，此外还支持原生 k8s CRD ，方便用户迁移。
+APISIX Ingress Controller solves all the problems mentioned above, and inherits all the advantages of APISIX, in addition to supporting native k8s CRD for easy migration.
-
+! [service mesh](https://static.apiseven.com/202108/20210625022.png)
-服务网格，这里面有必要跟大家重点聊聊。未来五年或者十年之后，最有可能主流的服务端架构是什么？如果让我回答，我选择服务网格。
+Service mesh, it is necessary to talk to you about it. In the next five or ten years, what is the most likely mainstream server-side architecture? If I were to answer, I would choose the service mesh.
-
+! [APISIX Mesh](https://static.apiseven.com/202108/20210625023.png)
-右图部分就是 APISIX Mesh 的内部架构图。
+The diagram on the right shows the internal architecture of APISIX Mesh.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625024.png)
-聊了这么多 APISIX 的当下，也和大家聊聊 APISIX 的未来。
+After talking so much about the present of APISIX, let's also talk about the future of APISIX.
-因为 APISIX 目前是 Apache 基金会项目，所以它已经不再属于个人或公司，而是全人类共享财产。这样社区中的每一个你，都有权利决定他往哪个方向发展。
+Because APISIX is currently an Apache Foundation project, it is no longer the property of individuals or companies, but of all humanity. This gives every one of you in the community the right to decide which direction it will go.
-开源版本 APISIX 目前默认搭配的配置中心是 etcd ，虽然目前它依旧是最好的选择，但我们在和用户沟通时依然经常会听到是否支持其他配置中心，比较常见的原因是 etcd 这个产品太新了，公司现有运维产品支持列表中没有它。所以我们计划让 APISIX 可以与其他配置中心协作。
+The default configuration center for the open source version of APISIX is etcd, and while it is still the best choice, we still often hear about support for other configuration centers when we talk to users, more often than not because etcd is so new that it is not on the list of supported products in the company's existing operations and maintenance products. So we plan to make APISIX work with other configuration centers.
-
+! [APISIX data plane](https://static.apiseven.com/202108/20210625025.png)
-APISIX 已经走在全流量数据面这条路上，相信大家都会问一些问题，比如：为什么要统一流量转发？统一是否给企业带来价值？对技术人员有什么收益？带着这些问题，我们看下图：
+APISIX is already on the road to full traffic data plane, and I believe we all ask questions such as: Why do we need to unify traffic forwarding? Does unification bring value to the enterprise? What are the benefits to the technical staff? With these questions in mind, let's look at the following diagram.
-
+! [APISIX goal](https://static.apiseven.com/202108/20210625026.png)
-统一本身不是目标，统一之后的收益才是我们追求的背后逻辑，下面分别给出几个不同角度来分别阐述。
+Unification itself is not the goal, but the benefits after unification is the logic behind our pursuit, and several different perspectives are given below to elaborate separately.
-- 运维角色：使用相同的运维工具收集日志、Metric 指标等，复用已有积累；
+- Operation and maintenance role: use the same operation and maintenance tools to collect logs, Metric metrics, etc., and reuse existing accumulations.
-- 开发角色：基于标准化的 APISIX 插件开发，能力可以方便复用，并且积累的经验可以应用到 LB、API Gateway、K8s Ingress 等不同产品线；
+- Development role: based on standardized APISIX plug-in development, the capabilities can be easily reused, and the accumulated experience can be applied to different product lines such as LB, API Gateway, K8s Ingress, etc.
-- 公司价值：统一技术栈，降低公司运营成本，降低过渡到微服务、云原生的难度，加速企业数字化转型。
+- Company value: Unify technology stack, reduce company operation cost, reduce the difficulty of transitioning to microservices and cloud-native, and accelerate enterprise digital transformation.
-
+! [connect APISIX](https://static.apiseven.com/202108/20210625027.png)
Review comment:
```suggestion
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org