yzeng25 commented on a change in pull request #682: URL: https://github.com/apache/apisix-website/pull/682#discussion_r738211235
########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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 --> Review comment: ```suggestion <!--truncate--> ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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) Review comment: ```suggestion I'll start by sharing with you the evolution of the backend architecture, which is very important.  ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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. Review comment: ```suggestion First of all, I would like to introduce myself, my name is Yuansheng Wang. 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. ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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) Review comment: ```suggestion We are looking forward to your dream and ideal to join us.  ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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) Review comment: ```suggestion  I've been a teacher and eventually a community leader. ``` ########## File path: website/blog/2021/07/25/apachecon-asia.md ########## @@ -1,167 +1,153 @@ --- -title: "ApacheCon Asia 2021：Apache APISIX 技术议题一览" -author: "Apache APISIX 社区" +title: "ApacheCon Asia 2021: Apache APISIX Technical Topics" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Apache APISIX - ApacheCon -description: ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +description: ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore "tomorrow's technologies" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia is an online ApacheCon conference organized by the ApacheCon organizing committee for the Asia-Pacific region with the primary goal of better serving the rapidly growing number of Apache users and contributors in the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. tags: [Events] --- -> ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +> ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. -<!--truncate--> +<! --truncate--> Review comment: ```suggestion <!--truncate--> ``` ########## File path: website/blog/2021/07/25/apachecon-asia.md ########## @@ -1,167 +1,153 @@ --- -title: "ApacheCon Asia 2021：Apache APISIX 技术议题一览" -author: "Apache APISIX 社区" +title: "ApacheCon Asia 2021: Apache APISIX Technical Topics" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Apache APISIX - ApacheCon -description: ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +description: ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore "tomorrow's technologies" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia is an online ApacheCon conference organized by the ApacheCon organizing committee for the Asia-Pacific region with the primary goal of better serving the rapidly growing number of Apache users and contributors in the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. tags: [Events] --- -> ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +> ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. -<!--truncate--> +<! --truncate--> -## 关于 ApacheCon Asia 2021 +## About ApacheCon Asia 2021 -ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。 +ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. -ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +ApacheCon Asia is the ApacheCon organizing committee's online ApacheCon conference for the Asia-Pacific region, with the primary goal of better serving the rapidly growing number of Apache users and contributors in the region. ApacheCon Asia 2021 will be held online from August 6-8 this year.  -近期 ApacheCon Asia 2021 团队正式公布了大会日程，Apache APISIX 社区积极参与本次年度开源盛会，共提报了 8 个 API/微服务技术相关的议题，内容丰富，欢迎关注。同时，ApacheCon Asia 2021 也为无法参加在线会议的各位开源爱好者提供了每个议题的回放和录播视频，详情请移步 [Apache Local Community 北京本地社区](https://space.bilibili.com/609014805)。 +The ApacheCon Asia 2021 team has recently announced the conference program. The Apache APISIX community is actively involved in this annual open source event, and has proposed a total of 8 API/microservices technology-related topics, which are rich in content and welcome your attention. For those who cannot attend the online conference, ApacheCon Asia 2021 also provides a replay and recorded video of each topic, please visit [Apache Local Community](https://space.bilibili.com/609014805). -## 关于 API / 微服务技术议题 +## About API / Microservices Technology Topics -API 是服务连接的基石，通过 API 我们可以将各种服务进行搭建，并提供给用户使用；随着应用的复杂度越来越高，单体应用逐渐被拆分为微服务，产品可以快速迭代的同时也带来安全、维护和可观测性方面的技术挑战。 +APIs are the cornerstone of service connectivity, allowing us to build services and make them available to users; as applications become more complex, monolithic applications are gradually being split into microservices, allowing for rapid iteration of products while also creating technical challenges in security, maintenance, and observability. -Apache APISIX 是 Apache 顶级项目，也是全球最活跃的开源网关项目。在这个专题中，大家不仅可以了解 Apache APISIX 设计理念，也会学习到 Apache APISIX 项目的最佳实践。 +Apache APISIX is the top project of Apache and the most active open source gateway project in the world. In this topic, you will not only learn about the Apache APISIX design philosophy, but also learn about the best practices of the Apache APISIX project. -## Apache APISIX 在移动云对象存储 EOS 的应用与实践 +## Application and Practice of Apache APISIX in Mobile Cloud Object Storage EOS -### 议题简介 +### Session Description -该演讲主题主要是讲述 Apache APISIX 在中国移动公有云对象存储 EOS 中的应用与实践经验分享。首先介绍了中国移动公有云建设规划及对象存储产品发展演进历程，然后阐述了我们为什么选择 Apache APISIX 作为负载均衡网关，并对 EOS 流量治理架构演进三个阶段进行进行了详细介绍。同时，我们还分享了基于 Apache APISIX 我们解决了哪些实际生产问题，做了哪些方案及开发工作，最后对我们未来的演进做了一些规划说明。 +This talk is about the application and practice of Apache APISIX in China Mobile's public cloud object storage EOS. First, we introduce the construction plan of China Mobile's public cloud and the evolution of object storage products, then we explain why we chose Apache APISIX as the load balancing gateway, and introduce the three stages of EOS traffic management architecture evolution. At the same time, we also shared what practical production problems we solved based on Apache APISIX, what solutions and development work we did, and finally, we explained some of our future evolution plans. -### 分享嘉宾 +### Sharing Guests - +! Yanshan [Chen](/img/blog_img/2021-07-25-2.png) Review comment: ```suggestion  ``` ########## File path: website/blog/2021/07/25/apachecon-asia.md ########## @@ -1,167 +1,153 @@ --- -title: "ApacheCon Asia 2021：Apache APISIX 技术议题一览" -author: "Apache APISIX 社区" +title: "ApacheCon Asia 2021: Apache APISIX Technical Topics" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Apache APISIX - ApacheCon -description: ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +description: ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore "tomorrow's technologies" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia is an online ApacheCon conference organized by the ApacheCon organizing committee for the Asia-Pacific region with the primary goal of better serving the rapidly growing number of Apache users and contributors in the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. tags: [Events] --- -> ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +> ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. ApacheCon Asia is the ApacheCon organizing committee's online conference for the Asia-Pacific region. ApacheCon Asia 2021 will be held online from August 6-8 this year. -<!--truncate--> +<! --truncate--> -## 关于 ApacheCon Asia 2021 +## About ApacheCon Asia 2021 -ApacheCon 是 Apache 软件基金会的官方全球系列会议。自 1998 年以来，ApacheCon 一直吸引着各个层次的参与者，在 350 多个 Apache 项目及其不同的社区中探索 “明日的技术”。 +ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels to explore the "technologies of tomorrow" across more than 350 Apache projects and their diverse communities. -ApacheCon Asia 是 ApacheCon 组委会针对亚太地区举办的 ApacheCon 在线会议，主要目标在于更好地服务亚太地区快速增长的 Apache 用户和贡献者。ApacheCon Asia 2021 将于今年 8 月 6-8 日在线举办。 +ApacheCon Asia is the ApacheCon organizing committee's online ApacheCon conference for the Asia-Pacific region, with the primary goal of better serving the rapidly growing number of Apache users and contributors in the region. ApacheCon Asia 2021 will be held online from August 6-8 this year.  -近期 ApacheCon Asia 2021 团队正式公布了大会日程，Apache APISIX 社区积极参与本次年度开源盛会，共提报了 8 个 API/微服务技术相关的议题，内容丰富，欢迎关注。同时，ApacheCon Asia 2021 也为无法参加在线会议的各位开源爱好者提供了每个议题的回放和录播视频，详情请移步 [Apache Local Community 北京本地社区](https://space.bilibili.com/609014805)。 +The ApacheCon Asia 2021 team has recently announced the conference program. The Apache APISIX community is actively involved in this annual open source event, and has proposed a total of 8 API/microservices technology-related topics, which are rich in content and welcome your attention. For those who cannot attend the online conference, ApacheCon Asia 2021 also provides a replay and recorded video of each topic, please visit [Apache Local Community](https://space.bilibili.com/609014805). -## 关于 API / 微服务技术议题 +## About API / Microservices Technology Topics -API 是服务连接的基石，通过 API 我们可以将各种服务进行搭建，并提供给用户使用；随着应用的复杂度越来越高，单体应用逐渐被拆分为微服务，产品可以快速迭代的同时也带来安全、维护和可观测性方面的技术挑战。 +APIs are the cornerstone of service connectivity, allowing us to build services and make them available to users; as applications become more complex, monolithic applications are gradually being split into microservices, allowing for rapid iteration of products while also creating technical challenges in security, maintenance, and observability. -Apache APISIX 是 Apache 顶级项目，也是全球最活跃的开源网关项目。在这个专题中，大家不仅可以了解 Apache APISIX 设计理念，也会学习到 Apache APISIX 项目的最佳实践。 +Apache APISIX is the top project of Apache and the most active open source gateway project in the world. In this topic, you will not only learn about the Apache APISIX design philosophy, but also learn about the best practices of the Apache APISIX project. -## Apache APISIX 在移动云对象存储 EOS 的应用与实践 +## Application and Practice of Apache APISIX in Mobile Cloud Object Storage EOS -### 议题简介 +### Session Description -该演讲主题主要是讲述 Apache APISIX 在中国移动公有云对象存储 EOS 中的应用与实践经验分享。首先介绍了中国移动公有云建设规划及对象存储产品发展演进历程，然后阐述了我们为什么选择 Apache APISIX 作为负载均衡网关，并对 EOS 流量治理架构演进三个阶段进行进行了详细介绍。同时，我们还分享了基于 Apache APISIX 我们解决了哪些实际生产问题，做了哪些方案及开发工作，最后对我们未来的演进做了一些规划说明。 +This talk is about the application and practice of Apache APISIX in China Mobile's public cloud object storage EOS. First, we introduce the construction plan of China Mobile's public cloud and the evolution of object storage products, then we explain why we chose Apache APISIX as the load balancing gateway, and introduce the three stages of EOS traffic management architecture evolution. At the same time, we also shared what practical production problems we solved based on Apache APISIX, what solutions and development work we did, and finally, we explained some of our future evolution plans. -### 分享嘉宾 +### Sharing Guests - +! Yanshan [Chen](/img/blog_img/2021-07-25-2.png) -陈焱山 — 毕业后一直从事分布式存储软件开发及架构方案设计工作，深度参与了移动云建设过程，重点完成了对象存储相关的主要技术方案选型及落地开发建设工作。同时，在分布式对象存储领域拥有丰富的实战经验，目前正在思考基于 APISIX 七层网关实现对象存储流量治理工作，实现架构进一步升级。 +Yanshan Chen - After graduation, he has been working on distributed storage software development and architecture design, and has been deeply involved in the construction process of mobile cloud, focusing on the selection of major technology solutions and landing development and construction work related to object storage. At the same time, he has rich practical experience in the field of distributed object storage, and is currently thinking about implementing object storage traffic governance based on APISIX seven-tier gateway to achieve further architectural upgrade. -### 分享时间 +### Share Time 2021-08-07 15:30 GMT+8 -## 使用 Apache APISIX 实现限流限速 +## Using Apache APISIX to implement flow limiting and speed limiting -### 议题简介 +When it comes to speed limiting, Nginx is the first thing that comes to mind, but Nginx is implemented through a configuration file that requires reloads for each change, making it extremely cumbersome to run and maintain. On the other hand, speed limiting conditions are limited to Nginx variables, making it difficult to achieve fine-grained speed limiting for business purposes. -谈到限流限速，人们往往最先想到的是 Nginx。然而 Nginx 通过配置文件的方式实现，每次变更都需要 reload，这让运维工作极其繁杂。另一方面，限速的条件被限制在 Nginx 的变量范围内，使得 Nginx 难以实现业务上精细化的限流限速需求。 +This session will show how to use Apache APISIX to achieve dynamic, fine-grained, and distributed reload limiting, and how to use plug-in orchestration to achieve reload limiting that better meets business needs. -本次分享将带来如何使用 Apache APISIX 来实现动态、精细化、分布式的限流限速，以及如何通过插件编排来实现更符合业务需求的限流限速。 +### Guest Speakers -### 分享嘉宾 + - +Junxu Chen - Internet veteran, worked in Sina, Xunlei, 360 and other well-known Internet companies, Apache APISIX Committer. -陈军旭 — 互联网老兵，曾任职于新浪、迅雷、360 等知名互联网公司，Apache APISIX Committer。 - -### 分享时间 +### Share time 2021-08-06 13:30 GMT+8 -## 用混沌网测试 Apache APISIX 的恢复能力 - -### 议题简介 +## Testing Apache APISIX recovery with Chaos.com -Apache APISIX 是领先的 API 网关 OSS 之一。为了确保一切按计划进行，APISIX 使用了不同种类的测试，包括单元、e2e 和模糊测试。然而，我们仍然不确定，当一些不正常但不可避免的情况发生时，例如网络故障、IO 压力或 pod 故障，APISIX 会如何表现。 +Apache APISIX is one of the leading API gateways OSS. To ensure that everything goes as planned, APISIX uses different kinds of tests, including unit, e2e and fuzzy tests. However, we are still not sure how APISIX will behave when some abnormal but unavoidable circumstances occur, such as network failure, IO stress or pod failure. -因此，在这里我们使用 Chaos Mesh，一个基于 Kubernetes 的混沌工程平台，可以顺利地注入不同种类的混沌，并将其整合到我们的 CI 管道中。在这个讲座的最后，听众会了解到混沌工程会在哪些方面给 API 网关带来好处，以及如何将混沌网整合到你自己的测试管道中。 +Therefore, here we use Chaos Mesh, a Kubernetes-based chaos engineering platform that can smoothly inject different kinds of chaos and integrate them into our CI pipeline. At the end of this talk, the audience will learn where Chaos Engineering will benefit the API gateway and how to integrate Chaos Mesh into your own test pipeline. -### 分享嘉宾 +### Sharing Guests - +! Yang [Shu Yang Wu](/img/blog_img/2021-07-25-4.png) -吴舒旸 — Apache APISIX 和 Chaos Mesh 的 Committer，他领导了 Chaos Mesh 与 Apache APISIX CI 的整合工作。 +Yang Wu - Committer for Apache APISIX and Chaos Mesh, he leads the integration of Chaos Mesh with Apache APISIX CI. -### 分享时间 +### Share Time 2021-08-06 14:50 GMT+8 -## 使用 Apache APISIX 进行认证和授权 +## Authentication and Authorization with Apache APISIX -### 议题简介 +Authentication and authorization are very necessary features in API gateways. This way, the services located behind the gateway are protected from unauthorized or malicious access, data leakage, and hacking. Apache APISIX is a dynamic, real-time, high-performance API gateway. And it provides many plug-ins, including authentication and authorization like key-auth, Open-ID, wolf-RBAC, etc. This proposal describes how to use Apache APISIX for authentication and authorization. -认证和授权是 API 网关中非常必要的功能。这样一来，位于网关后面的服务就可以得到保护，避免未经授权或恶意的访问、数据泄露和黑客攻击。Apache APISIX 是一个动态、实时、高性能的 API 网关。而且它提供了许多插件，包括像 key-auth、Open-ID、wolf-RBAC 等认证和授权。本提案介绍了如何使用 Apache APISIX 来进行认证和授权。 +### Sharing Guests -### 分享嘉宾 + - +Xinxin Zhu - Apache APISIX Committer, with years of CDN experience and familiar with gateways. -朱欣欣 — Apache APISIX Committer，有多年 CDN 工作经验，熟悉网关。 - -### 分享时间 +### Share time 2021-08-06 15:30 GMT+8 -## 依托社区让 Apache APISIX 高速发展 - -### 议题简介 +## Relying on the community to make Apache APISIX grow fast -在过去的一年里，Apahce APISIX 已经成为全世界最活跃的 API 网关项目，除了自身技术先进外，更得益于社区的高度活跃。截止目前，已经有来自世界各地 225 位贡献者参与贡献，并且还在保持高速增长。本次分享会介绍 APISIX 在践行“社区重于代码”过程的一些心得。作为一个理想主义创业者，又是如何与 Apache 文化结合，让创业公司也能高速发展。 +In the past year, Apahce APISIX has become the most active API gateway project in the world, not only because of its advanced technology, but also because of the highly active community. As of today, there are 225 contributors from all over the world, and the number is still growing rapidly. This session will introduce APISIX's experience in practicing "community over code". As an idealistic startup, how to combine with Apache culture to make the startup grow fast. -### 分享嘉宾 +### Guest Speakers - +Wang Yansheng [Yansheng Wang](/img/blog_img/2021-07-25-6.png) Review comment: ```suggestion  ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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.  -在创业之初，在脑子里过这张图的时候特别有意思。我们能够看到，随着我们后端架构的逐步迭代，我们引入了各种不同组件。比如到了 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.  -回顾前面的架构演变图，相信很多同学都已经发现问题在哪里。从上到下，从左到右，针对不同场景，我们最终“合理”的引入了各种组件来分别解决我们的问题，架构师生存法则：选择当下最适合的。 +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 缺点，比如 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 之前，想和大家聊一下什么是云原生。这个名词从诞生到现在很久，但到现在没有统一明确的定义。我综合几家云厂商定义，概括云原生特征主要有两点：第一要支持容器，第二要支持弹性伸缩部署。我认为 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 的问题： +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.  -这张图的左右分别是 DP（Date Plane）和 CP（Control Plane），跟大家所熟悉的后端服务体系一样。APISIX 从架构第一天就没有想去自己造新东西，所以关于配置中心选择了当下最成熟的 etcd。 +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. -在这个架构里面，你找不到一个单点。这里的任何一个服务出现异常宕机等事故，都不会影响 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 的生态图，从该图可以准确看到目前都支持了哪些周边生态。左侧是支持的协议，可以看到常见的 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 当前状态，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 和 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 -经过我们实际的客户走访，支持多语言这个特性是非常有必要的。毕竟对于很多公司而言，都有自己熟悉的技术栈，很多公司对 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 支持多语言的特性，已经放到开源项目，欢迎感兴趣的同学可以随时关注并参与。这个实现方案的优势是简单、通用，大家可以原生的使用自己熟悉语言。 +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.  -聊了这么多，给大家介绍下 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 要干什么。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.  -针对传统的 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.   -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, 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 的内部架构图。 +The diagram on the right shows the internal architecture of APISIX Mesh.  -聊了这么多 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 已经走在全流量数据面这条路上，相信大家都会问一些问题，比如：为什么要统一流量转发？统一是否给企业带来价值？对技术人员有什么收益？带着这些问题，我们看下图： +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.  -统一本身不是目标，统一之后的收益才是我们追求的背后逻辑，下面分别给出几个不同角度来分别阐述。 +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, 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.  -最后是 APISIX 的 QQ 群，有任何问题都可以在这里或者 [Github issue](https://github.com/apache/apisix/issues) 留言，会有专人快速响应，再次感谢大家。 +Last but not least is the APISIX [Slack channel](https://apisix.apache.org/docs/general/community#slack), 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. -点击观看[视频](https://www.bilibili.com/video/BV1w54y1V73Z?p=1&share_medium=android&share_plat=android&share_source=COPY&share_tag=s_i×tamp=1621812452&unique_k=PEusrt) +Click to watch the [video](https://www.bilibili.com/video/BV1w54y1V73Z?p=1&share_medium=android&share_plat=android&share_source=COPY&share_tag=s_i&;) timestamp=1621812452&unique_k=PEusrt) Review comment: ```suggestion Click to watch the [video](https://www.bilibili.com/video/BV1w54y1V73Z?p=1&share_medium=android&share_plat=android&share_source=COPY&share_tag=s_i×tamp=1621812452&unique_k=PEusrt) ``` ########## File path: website/blog/2021/06/28/why-we-need-Apache-APISIX.md ########## @@ -1,176 +1,178 @@ --- -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".  -之所以我们要做 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) Review comment: ```suggestion The sad thing is that mankind doesn't need a history anymore.  ``` ########## File path: website/blog/2021/07/21/Apache-APISIX-Kubernetes.md ########## @@ -1,44 +1,43 @@ --- -title: "Apache APISIX x Kubernetes：恰到好处｜直播预告" -author: "Apache APISIX 社区" +title: "Apache APISIX x Kubernetes: Just Right｜Live" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Kubernetes -- 直播预告 -description: 直播预告：北京时间 2021 年 7 月 23 日星期五 00:00，Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +description: 'Live Preview: On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will present "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for global developers. The topic will be "Run Apache APISIX in Kubernetes".' tags: [Events] --- -> 北京时间 2021 年 7 月 23 日星期五 00:00， Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +> On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will share the topic "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for developers around the world. -<!--truncate--> +<! --truncate--> -张晋涛将在本次演讲中分享在 Kubernetes 上运行 Apache APISIX，以及如何将 Apache APISIX 作为 Ingress Controller 来使用的经验。感兴趣的小伙伴不要错过，赶紧报名约起来~ +In this talk, Jintao Zhang will share his experience of running Apache APISIX on Kubernetes and how to use Apache APISIX as an Ingress Controller. If you're interested, don't miss it, sign up now! -## 参与方式 +## How to participate -- 方式一：点击 [此处](https://www.meetup.com/Data-on-Kubernetes-community/events/278922486/) 跳转报名网页，注册报名。 +- Method 1: Click [here](https://www.meetup.com/Data-on-Kubernetes-community/events/278922486/) to visit the registration page and register. -- 方式二：在直播开始时通过 Zoom 链接进入会议室聆听分享：[会议室直播间](https://zoom.us/webinar/tJYofuChrzktGtI3wr8SZHACRnNkxr5cWgny)。 +- Way 2: Go to the Zoom link at the beginning of the live broadcast to listen to the sharing: [Meeting Room Live](https://zoom.us/webinar/tJYofuChrzktGtI3wr8SZHACRnNkxr5cWgny). -## 来不及看直播怎么办 +## What to do if you can't make it to the live stream -Meetup 结束后，我们会在 Apache APISIX 的 bilibili 账号上传 Meetup 录播。欢迎大家关注 Apache APISIX bilibili 账号 [Apache-APISIX](https://space.bilibili.com/551921247)。 +After the Meetup, we will upload the Meetup recording on Apache APISIX's bilibili account. Welcome to follow the Apache APISIX bilibili account [Apache-APISIX](https://space.bilibili.com/551921247). -## 讲师介绍 +## Lecturer Introduction -张晋涛，支流科技云原生技术专家、Apache APISIX committer、Kubernetes ingress-nginx reviewer。他同时作为 containerd/Docker/Helm/Kubernetes/KIND 等众多开源项目 contributor 在开源社区活跃，是 『K8S 生态周报』的维护者之一。 -从业 7 年，张晋涛对 Docker 和 Kubernetes 等容器化技术有大量实践和深入源码的研究，是业内多个知名大会讲师，PyCon China 核心组织者之一。同时著有 《Kubernetes 上手实践》和 《Docker 核心知识必知必会》等专栏。运营有公众号：MoeLove。 +Jintao Zhang is a cloud native technologist at Tributary Technology, Apache APISIX committer, Kubernetes ingress-nginx reviewer, and contributor to many open source projects such as containerd/Docker/Helm/Kubernetes/KIND. He is also active in the open source community as a contributor, and is one of the maintainers of the K8S Weekly Eco Report. +With 7 years in the industry, Jintao Zhang has a lot of practice and deep source code research on containerization technologies such as Docker and Kubernetes, and is one of the core organizers of PyCon China. He is also the author of "Kubernetes Hands-on" and "Docker Core Knowledge Must Know". He runs the public number: MoeLove. - +He is also the author of Kubernetes Hands-on and Docker Core Knowledge. [Lecturer-Jintao Zhang](https://static.apiseven.com/202108/1630382172445-cf20986b-c939-497e-86a4-92da7064ae97.PNG) Review comment: ```suggestion He is also the author of Kubernetes Hands-on and Docker Core Knowledge.  ``` ########## File path: website/blog/2021/07/21/Apache-APISIX-Kubernetes.md ########## @@ -1,44 +1,43 @@ --- -title: "Apache APISIX x Kubernetes：恰到好处｜直播预告" -author: "Apache APISIX 社区" +title: "Apache APISIX x Kubernetes: Just Right｜Live" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Kubernetes -- 直播预告 -description: 直播预告：北京时间 2021 年 7 月 23 日星期五 00:00，Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +description: 'Live Preview: On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will present "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for global developers. The topic will be "Run Apache APISIX in Kubernetes".' tags: [Events] --- -> 北京时间 2021 年 7 月 23 日星期五 00:00， Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +> On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will share the topic "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for developers around the world. -<!--truncate--> +<! --truncate--> Review comment: ```suggestion <!--truncate--> ``` ########## File path: website/blog/2021/07/21/Apache-APISIX-Kubernetes.md ########## @@ -1,44 +1,43 @@ --- -title: "Apache APISIX x Kubernetes：恰到好处｜直播预告" -author: "Apache APISIX 社区" +title: "Apache APISIX x Kubernetes: Just Right｜Live" +author: Apache APISIX keywords: -- API 网关 +- API Gateway - APISIX - Kubernetes -- 直播预告 -description: 直播预告：北京时间 2021 年 7 月 23 日星期五 00:00，Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +description: 'Live Preview: On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will present "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for global developers. The topic will be "Run Apache APISIX in Kubernetes".' tags: [Events] --- -> 北京时间 2021 年 7 月 23 日星期五 00:00， Apache APISIX committer 张晋涛将在 Data on Kubernetes Community 的 Meetup 上，面向全球开发者做主题为《Run Apache APISIX in Kubernetes》的分享。 +> On Friday, July 23rd, 2021 at 00:00 GMT, Apache APISIX committer Jintao Zhang will share the topic "Run Apache APISIX in Kubernetes" at the Data on Kubernetes Community Meetup for developers around the world. -<!--truncate--> +<! --truncate--> -张晋涛将在本次演讲中分享在 Kubernetes 上运行 Apache APISIX，以及如何将 Apache APISIX 作为 Ingress Controller 来使用的经验。感兴趣的小伙伴不要错过，赶紧报名约起来~ +In this talk, Jintao Zhang will share his experience of running Apache APISIX on Kubernetes and how to use Apache APISIX as an Ingress Controller. If you're interested, don't miss it, sign up now! -## 参与方式 +## How to participate -- 方式一：点击 [此处](https://www.meetup.com/Data-on-Kubernetes-community/events/278922486/) 跳转报名网页，注册报名。 +- Method 1: Click [here](https://www.meetup.com/Data-on-Kubernetes-community/events/278922486/) to visit the registration page and register. -- 方式二：在直播开始时通过 Zoom 链接进入会议室聆听分享：[会议室直播间](https://zoom.us/webinar/tJYofuChrzktGtI3wr8SZHACRnNkxr5cWgny)。 +- Way 2: Go to the Zoom link at the beginning of the live broadcast to listen to the sharing: [Meeting Room Live](https://zoom.us/webinar/tJYofuChrzktGtI3wr8SZHACRnNkxr5cWgny). -## 来不及看直播怎么办 +## What to do if you can't make it to the live stream -Meetup 结束后，我们会在 Apache APISIX 的 bilibili 账号上传 Meetup 录播。欢迎大家关注 Apache APISIX bilibili 账号 [Apache-APISIX](https://space.bilibili.com/551921247)。 +After the Meetup, we will upload the Meetup recording on Apache APISIX's bilibili account. Welcome to follow the Apache APISIX bilibili account [Apache-APISIX](https://space.bilibili.com/551921247). -## 讲师介绍 +## Lecturer Introduction -张晋涛，支流科技云原生技术专家、Apache APISIX committer、Kubernetes ingress-nginx reviewer。他同时作为 containerd/Docker/Helm/Kubernetes/KIND 等众多开源项目 contributor 在开源社区活跃，是 『K8S 生态周报』的维护者之一。 -从业 7 年，张晋涛对 Docker 和 Kubernetes 等容器化技术有大量实践和深入源码的研究，是业内多个知名大会讲师，PyCon China 核心组织者之一。同时著有 《Kubernetes 上手实践》和 《Docker 核心知识必知必会》等专栏。运营有公众号：MoeLove。 +Jintao Zhang is a cloud native technologist at Tributary Technology, Apache APISIX committer, Kubernetes ingress-nginx reviewer, and contributor to many open source projects such as containerd/Docker/Helm/Kubernetes/KIND. He is also active in the open source community as a contributor, and is one of the maintainers of the K8S Weekly Eco Report. +With 7 years in the industry, Jintao Zhang has a lot of practice and deep source code research on containerization technologies such as Docker and Kubernetes, and is one of the core organizers of PyCon China. He is also the author of "Kubernetes Hands-on" and "Docker Core Knowledge Must Know". He runs the public number: MoeLove. - +He is also the author of Kubernetes Hands-on and Docker Core Knowledge. [Lecturer-Jintao Zhang](https://static.apiseven.com/202108/1630382172445-cf20986b-c939-497e-86a4-92da7064ae97.PNG) -## 关于 Apache APISIX +## About Apache APISIX -Apache APISIX 是一个动态、实时、高性能的开源 API 网关，提供负载均衡、动态上游、灰度发布、服务熔断、身份认证、可观测性等丰富的流量管理功能。Apache APISIX 可以帮忙企业快速、安全的处理 API 和微服务流量，包括网关、Kubernetes Ingress 和服务网格等。 +Apache APISIX is a dynamic, real-time, high-performance open source API gateway that provides rich traffic management features such as load balancing, dynamic upstream, grayscale publishing, service fusion, authentication, observability, etc. Apache APISIX can help enterprises quickly and securely handle API and microservice traffic, including gateways, Kubernetes Ingress and Service Grid. -全球已有数百家企业使用 Apache APISIX 处理关键业务流量，涵盖金融、互联网、制造、零售、运营商等等，比如美国航空航天局（NASA）、欧盟的数字工厂、中国航信、中国移动、腾讯、华为、微博、网易、贝壳找房、360、泰康、奈雪的茶等。 +Apache APISIX has been used by hundreds of enterprises worldwide to handle business-critical traffic, including finance, Internet, manufacturing, retail, carriers, and more, such as NASA, the European Union's Digital Factory, China Airlines, China Mobile, Tencent, Huawei, Weibo, NetEase, Shell, 360, Taikang, and Nespresso Tea. -200 余位贡献者，一同缔造了 Apache APISIX 这个世界上最活跃的开源网关项目。聪明的开发者们！快来加入这个活跃而多样化的社区，一起来给这个世界带来更多美好的东西吧！ +More than 200 contributors have come together to create Apache APISIX, the world's most active open source gateway project. Smart developers! Come join this active and diverse community and come together to bring more good things to the world! -[Apache APISIX GitHub 项目地址](https://github.com/apache/apisix) +[Apache APISIX GitHub project address](https://github.com/apache/apisix) Review comment: ```suggestion [Apache APISIX GitHub project](https://github.com/apache/apisix) ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
