Developing an extension library to add the request aggregation functionallity to the YARP.

[shokri-navid]

I am looking for the functionality of request aggregation inside YARP and this thread of GitHub issue caught my eye.

I see @samsp-msft's point. However, request aggregation could be an extension of the YARP. Is there a solution to add this functionality as a separate extension library that leaves the core untouched but makes programmers' lives easier?
Based on my experience performance is a MUST aspect for API Gateways / Reverse Proxies and it is the main motivation for engineers to use YARP. But, the Request aggregation is a common requirement these days especially when you are working with legacy code.
I want to check the possibility of this approach and some key hints to estimate that could I develop such an extension.

[MihaZupan]

See #1677 (reply in thread), #2386 (comment).

It's certainly possible to build a separate library that builds on top of YARP to add more functionality, but it's unclear what YARP features you would want to reuse/build on.

If the logic around how you combine responses together is always the same, there were examples posted in #1677 with code showing how that could be done.