Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Gateway vs Reverse Proxy #28

Open
AwesomeYuer opened this issue Aug 18, 2020 · 0 comments
Open

API Gateway vs Reverse Proxy #28

AwesomeYuer opened this issue Aug 18, 2020 · 0 comments

Comments

@AwesomeYuer
Copy link
Owner

AwesomeYuer commented Aug 18, 2020

https://github.com/ProxyKit/

Ocelot is an API Gateway that also runs on ASP.
Ocelot是一个API网关,也运行在ASP上。

NET Core.
净的核心。

A key difference between API Gateways and general Reverse Proxies is that the former tend to be message based whereas a reverse proxy is stream based.
API网关和一般反向代理之间的一个关键区别是,前者倾向于基于消息,而反向代理是基于流的。

That is, an API Gateway will typically buffer every request and response message to be able to perform transformations.
也就是说,API网关通常会缓冲每个请求和响应消息,以便能够执行转换。

This is fine for an API Gateway but not suitable for a general reverse proxy performance wise nor for responses that are chunked-encoded.
这对于API网关很好,但不适合一般的反向代理性能,也不适合分块编码的响应。

See Not Supported Ocelot docs.

参见不支持的Ocelot文档。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant