You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by yi...@apache.org on 2023/04/19 03:49:20 UTC
[apisix-website] branch master updated: New tags added (#1566)
This is an automated email from the ASF dual-hosted git repository.
yilinzeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 4a12ca42602 New tags added (#1566)
4a12ca42602 is described below
commit 4a12ca426020608cf37769d4810ac6d4265a654d
Author: Vishu Verma <01...@gmail.com>
AuthorDate: Wed Apr 19 09:19:14 2023 +0530
New tags added (#1566)
---
.../09/13/why-is-apache-apisix-the-best-api-gateway.md | 8 ++++----
.../2022/09/27/why-apache-apisix-is-best-apigateway.md | 14 +++++++-------
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md b/blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md
index cd6ef42bacc..8e4f424fe01 100644
--- a/blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md
+++ b/blog/en/blog/2022/09/13/why-is-apache-apisix-the-best-api-gateway.md
@@ -12,7 +12,7 @@ keywords:
- The Best API Gateway
- Apache APISIX
description: Why is Apache APISIX the best API Gateway? We will compare multiple API gateways (Kong, Tyk, Gloo) in terms of the popularity among developers, open source licenses, performances, and the ecosystem as a whole.
-tags: [Technology, Products]
+tags: [Community]
image: https://static.apiseven.com/2022/11/05/6365f2b8be5a7.png
---
@@ -69,9 +69,9 @@ Under such circumstances, choosing an Apache Software Foundation(ASF)'s open sou
A frequently asked question in the community: which one has the better performance, Envoy-based Gloo or NGINX-based APISIX? Although performance is not the most critical metric, it is inarguably the most direct metric. The table below shows the benchmark scores of Apache APISIX and Gloo. The QPS of Apache APISIX is 4.6 times that of Gloo, and the latency of Apache APISIX is merely 7% of Gloo’s.
-| **API Gateway** | Apache APISIX | Gloo Edge |
-| :-------------: | :----------------------------------------------------------------------: | :--------------------------------------------------------------------: |
-| **QPS** | 59122 | 12903 |
+| **API Gateway** | Apache APISIX | Gloo Edge |
+| :-------------: | :-------------------------------------------------------------------------: | :-----------------------------------------------------------------------: |
+| **QPS** | 59122 | 12903 |
| **Latency** | 50.000% 470.00us<br/>75.000% 648.00us<br/>90.000% 0.89ms<br/>99.000% 1.60ms | 50.000% 6.80ms<br/>75.000% 9.25ms<br/>90.000% 11.32ms<br/>99.000% 17.06ms |
The choice of NGINX or Envoy is not the main factor of the performance difference, but the underlying optimization APISIX did in its source code. Even compared to KONG, which is also NGINX-based, APISIX has a huge performance upper hand. The graph below is extracted from [GigaOm’s](https://gigaom.com/) report on testing Kong’s Enterprise Edition and AP7 Enterprise Edition ([You can contact us for the complete data](https://api7.ai/request-demo/)).
diff --git a/blog/zh/blog/2022/09/27/why-apache-apisix-is-best-apigateway.md b/blog/zh/blog/2022/09/27/why-apache-apisix-is-best-apigateway.md
index dc798ba6939..8785ef314ef 100644
--- a/blog/zh/blog/2022/09/27/why-apache-apisix-is-best-apigateway.md
+++ b/blog/zh/blog/2022/09/27/why-apache-apisix-is-best-apigateway.md
@@ -11,7 +11,7 @@ keywords:
- API 管理平台
- Apache APISIX
description: 本文从多个角度（在开发人员中的受欢迎程度、开源许可证、性能和整个生态系统）对比多个 API 网关（Kong、Tyk、Gloo）。
-tags: [Technology]
+tags: [Community]
image: https://static.apiseven.com/2022/10/19/634f6677742a1.png
---
@@ -47,8 +47,8 @@ Tyk 的贡献者月活跃人数，长期都是在 5 个人左右，很少超过
这四个开源 API 网关项目背后，都是有对应的商业化公司的，所以还有第三个指标数据，那就是开源项目贡献者和商业公司员工数的对比：
-| **API Gateway** | **APISIX** | **Kong** | **Tyk** | **Gloo** |
-| :----------------------: | :--------: | :------: | :-----: | :------: |
+| **API Gateway** | **APISIX** | **Kong** | **Tyk** | **Gloo** |
+| :--------------------: | :--------: | :------: | :-----: | :------: |
| 月度活跃人数 | 38 | 20 | 8 | 24 |
| 公司成员(数据来自领英) | 40+ | 500+ | 200+ | 100+ |
@@ -73,9 +73,9 @@ Tyk 的贡献者月活跃人数，长期都是在 5 个人左右，很少超过
在社区中经常会有用户提问：基于 Envoy 的 Gloo，和基于 NGINX 的 APISIX，谁的性能更胜一筹？
虽然性能并不是选型中最重要的指标，但它确实是最直接的指标。下表的表格是 Apache APISIX 和 Gloo 的 Benchmark 结果。从表格中可以看到，Apache APISIX 的 QPS 是 Gloo 的 4.6 倍，同时 Apache APISIX 的延迟还不到 Gloo 的 7%。
-| **API Gateway** | Apache APISIX | Gloo Edge |
-| :-------------: | :----------------------------------------------------------------------: | :--------------------------------------------------------------------: |
-| **QPS** | 59122 | 12903 |
+| **API Gateway** | Apache APISIX | Gloo Edge |
+| :-------------: | :-------------------------------------------------------------------------: | :-----------------------------------------------------------------------: |
+| **QPS** | 59122 | 12903 |
| **Latency** | 50.000% 470.00us<br/>75.000% 648.00us<br/>90.000% 0.89ms<br/>99.000% 1.60ms | 50.000% 6.80ms<br/>75.000% 9.25ms<br/>90.000% 11.32ms<br/>99.000% 17.06ms |
这并不仅仅是 NGINX 和 Envoy 之间的差异造成的，而是因为 APISIX 在底层做了大量的优化，所以同样基于 NGINX 的 APSIX 相对于 Kong 也有巨大的性能优势。
@@ -203,4 +203,4 @@ APISIX 目前已经支持了 80 多种插件，但仍然难以涵盖用户的所
本文从工程师、开源协议、性能评测、技术、生态系统等多个角度分析和比较了一些 API 网关产品，可以看出 Apache APISIX 是其中的佼佼者，引领了 API 网关领域的创新。
-Apache APISIX 不仅是一个可以处理南北向流量的 API 网关，同时也有 APISIX Ingress Controller、Service Mesh 等开源产品。本月底 APISIX 也将发布 3.0 预览版，带来全新功能与全方位产品提升，敬请期待！
+Apache APISIX 不仅是一个可以处理南北向流量的 API 网关，同时也有 APISIX Ingress Controller、Service Mesh 等开源产品。本月底 APISIX 也将发布 3.0 预览版，带来全新功能与全方位产品提升，敬请期待！