知识卡片
网关控制调用不揽业务
API网关接收调用并路由至后端,提供安全、限流、监测与使用报告;开发者门户提供发现、文档与示例。复杂业务和聚合逻辑应由负责该语境的域组件承担,避免把网关重建为新的中央ESB。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Services and API Management · 查看原书依据
Modern applications and changes in protocols and message designs also started to influence the API architecture. A more lightweight integration component emerged, known as the API gateway. An API gateway doesn’t have the overhead of adapters or the complex integration functionality of the ESB but still allows encapsulation and provides the management capabilities to control, secure, manage, and report on API usage. It’s usually part
参考来源
- 位置:《Data Management at Scale》第05章《Services and API Management》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch05.html)
- 结论依据:原文对API gateway doesn’t have the overhead的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。
- 原始内容:Modern applications and changes in protocols and message designs also started to influence the API architecture. A more lightweight integration component emerged, known as the API gateway. An API gateway doesn’t have the overhead of adapters or the complex integration functionality of the ESB but still allows encapsulation and provides the management capabilities to control, secure, manage, and report on API usage. It’s usually part