4 ms·
I see. So it can operate in-process? Could in theory be much faster than nginx out-of-process model.
by rafale 5y ago
I see. So it can operate in-process? Could in theory be much faster than nginx out-of-process model.
- tremon 5y agoWhy would someone need an in-process reverse proxy? I don't see what an in-process proxy would add that a request routing engine couldn't do. Or is the point that you can now add your reverse proxy configuration as just another project within the same solution?
- kcb 5y agoI was assuming more the latter. Also benefit is you can extend and customize in C#.
- rafale 5y agoAnd you could dynamically and efficiently add/remove web apps and endpoints assuming your entire codebase is in C#.
- bob1029 5y agoYou can also block the clients for a brief period while you make routing changes, or wait for any other arbitrary event to complete. This is one way to achieve zero-downtime upgrades, even in situations where the service is running as a single binary on a single host.
- 9wzYQbTYsAIc 5y agoYou might need to deploy a single executable rather than multiple.
- AlfeG 5y agoWe use it to proxy request from "modern" part of application moved to .net core to legacy parts of application, that are yet to be converted.
- davidfowl 5y agoThis is a "premiere use case" we've seen people use YARP for.
- oaiey 5y agoI think it either operates as a traditional (heavily customizable) reverse proxy OR you have a app and forwards x% of your API surface to second tier services. Imho: no in-procees reverse proxying. That should not make sense.