3 ms·
I think this project is for when you need to do some fancy request modification that's hard/slow to do with Nginx or the like. It's not meant to compete speed-
by dikei 5y ago
I think this project is for when you need to do some fancy request modification that's hard/slow to do with Nginx or the like.
It's not meant to compete speed-wise with other off-the-shell reverse proxies.
- oneplane 5y agoWe're doing that with Envoy and OpenResty and both are (at this stage) faster and more flexible. We use Lua in both cases, so I suppose it becomes a .NET vs. Lua thing. But to me, when your infrastructure becomes a language/framework fight we're in the wrong battle anyway.
- zerkten 5y ago>> But to me, when your infrastructure becomes a language/framework fight we're in the wrong battle anyway. It is to me as well, but these fights are quite pervasive in our industry. It is especially problematic in the enterprise space. This is to the point as a C# dev, that I'm happy this exists, so that I have the facilities it provides, when more mature solutions are unavailable.
- oneplane 5y agoI can imagine a case where even some 'brand name box' proxy/balancer or rolling your own are the only choices available. In such a case, YARP wins instantly (at least from my perspective). If I can't inspect what critical elements in my request pipeline are doing I don't want them. This even applies when we get Big-IP/F5 buying nginx and putting that inside the name-brand boxes, it's still too opaque to be useful for me.