知识卡片
代理可成为网关的底座
NGINX、Envoy 等通用七层代理可以独立部署,也可被网关项目包裹以增加平台集成与自助能力。网关项目的治理功能与底层代理的数据处理职责不同,复用同一代理也不代表功能完全相同。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 相关技术比较 · 查看原书依据
NGINX As a stable, efficient, ubiquitous L7 proxy, NGINX is commonly found at the core of API gateways. It may be used on its own or wrapped with additional features to facilitate container orchestrator native integration or additional self-service functionality for developers. For example: API Umbrella uses NGINX Kong uses NGINX OpenResty uses NGINX Envoy The Envoy project has also been used as the foundation for API gateways: Ambassador With
参考来源
- 位置:《The Enterprise Path to Service Mesh Architectures, 2nd Edition》第02章《相关技术比较》(来源项目book-sources;源文件:extracted/The Enterprise Path to Service Mesh Architectures, 2nd Edition/_epub-src/OEBPS/ch02.xhtml)
- 结论依据:原文在此说明该机制、范围或取舍;本卡保留其历史语境,不将预测、产品状态或命令作为当前已核验事实。
- 原始内容:NGINX As a stable, efficient, ubiquitous L7 proxy, NGINX is commonly found at the core of API gateways. It may be used on its own or wrapped with additional features to facilitate container orchestrator native integration or additional self-service functionality for developers. For example: API Umbrella uses NGINX Kong uses NGINX OpenResty uses NGINX Envoy The Envoy project has also been used as the foundation for API gateways: Ambassador With