Kong 企业版的延迟对比。
图 2-3 在单节点和10krps 的情况下，API7 与 Kong 企业版性能对比
从中可以看出，API7的延迟表现非常稳定，99.9%的请求都在6毫秒内完成了处理；而Kong企业版的延迟是API7的几十倍。 5ea7b01c8263abfb38728/p18_2.jpg)
图 2-4 在开启 JWT 插件和 10krps 的情况下，API7 与 Kong 企业版性能对比
可以看到，在开启 JWT 插件后 API7 的请求延迟表现依然稳定，而 Kong 企业版的延迟是 API7 的数百倍，差距非常明显。
0 码力 |
19 页 |
1.12 MB
| 2 年前 3 [Image](/uploads/documents/d/f/4/2/df4204d40f8d9990146651d100a36efb/p26_1.jpg)
Qingkai Shi
Hong Kong University of Science and Technology, China
qshiaa@cse.ust.hk
Xiao Xiao
Sourcebrella Inc
China Sourcebrella Inc
China
jinguo@sbrella.com
Gang Fan
Hong Kong University of Science and Technology, China
gfan@cse.ust.hk
Rongxin Wu
Hong Kong University of Science and Technology, China
wurongxin@cse verification and validation;
Keywords Sparse program analysis, error detection, path-
Charles Zhang
Hong Kong University of Science and Technology, China
charlesz@cse.ust.hk
Flow Analysis for Million Lines 0 码力 |
39 页 |
6.88 MB
| 2 年前 3 the needs of the enterprise
• Different open source projects have different solutions to this
## Kong
• Native Support: Lua plugins
• Few developers are familiar with Lua
• Solution: Go plugin
## Envoy developers can write Lua
• Solution: WASM, not good enough in the short term
## Apache APISIX
- Both Kong and Envoy’s solutions are want more developers to develop plugins
• We are looking for silver bullet Gateway -> East-West Microservice
• East-west service mesh -> North-south access layer
• Envoy、Kong、Apache APISIX: full traffic access layer
• no longer the traditional functions of Nginx and F5
• 0 码力 |
28 页 |
1.19 MB
| 1 年前 3 other
Firewall
Spring Boot
OAuth2.0
Jenkins
SonarQube
Gitlab
Influxdb
MySQL
RESTful API
Kong Api Gateway
Access Layer
Cloud Managed Platform
Orchestration & Governance
Tencent cloud
Registry Center
Eureka
Job Scheduler
Quartz
Private Cloud
Public Cloud
Rest API
API Gateway (Kong)
Query
EventBus Ser
Service
Common
Sprint Boot
Log4j2
interceptor
Message bus
SDK
Message 0 码力 |
32 页 |
6.05 MB
| 2 年前 3 |18|Sony|Japan|Hardware|22|
|19|Cisco|USA|Hardware|21|
|20|Fujitsu|Japan|Hardware|20|
|21|PCCW|Hong Kong|Telco|20|
|22|NEC|Japan|Software|19|
|23|Oracle|USA|Hardware|18|
|24|MCI|USA|Telco|18|
|25|Sharp|Japan|Hardware|18|
In 1995, Japan had 30% (9 of 30) of the top tech companies and 0 in 2025. UK / Singapore / Hong Kong / Mexico / Malaysia had 1, now 0.
In 2025, new geographic entrants include China with 3, Germany Epoch AI
*Hong Kong is a Special Administrative Region (SAR) of China, not an independent country. Note: Epoch AI defines 0 码力 |
340 页 |
12.14 MB
| 1 年前 5 database, and brings higher quality and more loyal customers.
We have offices in Beijing, Shanghai, Hong Kong and Paris, providing international working environments with employees from all over the world.
CURIOSITYCHINA /0/1/0/50101877a71f1ea2a04c84709f316164/p40_1.jpg)
PLUGINS
CUSTOM
PLUGINS
RATE LIMIT
CLIENT
KONG
API
## V M 的应用 VULCAN etcd
 Leo and Soonho Kong
• Almost useless
• Brave (crazy?) users in 2014: Jeremy Avigad, Cody Roux and Floris van Doorn
• Lean 2 (2015) Leo and Soonho Kong
• First official release
• Emacs 0 码力 |
54 页 |
4.78 MB
| 2 年前 3
| 
APISEVEN 和Kong EE 的性能评测# APISEVEN 和 Kong EE 的性能评测 -- GigaOm 高性能API管理测试 产品评估：API7和Kong企业版  1 - 摘要3 API76 图1. API7技术架构7 Kong 企业版7 3-GigaOm API负载测试设置9 环境清单10 软件版本信息11 4-测试结果12 图2. 空转时的压力测试 API 的基线延迟12 图3. API7与Kong EE在20,000 rps时的对比13 图4. API7与Kong EE在10,000 rps时的JWT对比。13 图5. API7与Kong EE在10,000 rps时的1,000条路由的对比14 5-结论15 6-附录16 7-关于GigaOm19 8-关于API720 在本文中，我们展示了使用2个全生命周期API管理平台完成的性能测试结果：API7 和 Kong 企业版 (Kong EE)。 在我们的单节点设置中，API7所有的压力测试结果都优于Kong EE。在每秒10,000个请求的情况下，99.99%的情况API7的延迟比Kong EE低14倍。API7和Kong EE二者百分比越高延迟差异越明显。在我们所有的测试中，最大延迟差异体现得最明显的是达到990 码力 | 14 页 | 1.11 MB | 2 年前3