Chris Ross

This could also come into play for rolling upgrades: https://github.com/microsoft/reverse-proxy/issues/190#issuecomment-632798853 1. Remove some nodes from pool1 2. Shut down those nodes 3. Upgrade and restart them 4. Add those nodes...

Note: Backed.PartitioningOptions seems to be related to this scenario, but it's not actually implemented anywhere. Implement or remove this option section. The same for quota and circuit breaker options.

Notes from a partner discussion: ``` Routing - One Catch-All - Partitioning function to select cluster Clusters, each with one destination - Next - Current - Previous ```

@johnazariah to your question from: https://github.com/microsoft/reverse-proxy/issues/405#issuecomment-689092153 You could still use the headers to decide where requests get assigned, but it would be applied at a stage after routing and would...

Related: partitioning and shuffle sharding, great talk from AWS: https://www.youtube.com/watch?v=swQbA4zub20

E-Core3 is using IHttpProxy directly and does not need anything from us here. There is still general community interest so I'll do some prototyping and see what works.

Here's a partial proposal for 1.1 that should let people build their own A/B features without us having to be too opinionated on their design: Routes would need a default...

Can everyone here please take a look at https://github.com/microsoft/reverse-proxy/pull/1538. It doesn't fully implement A/B or related systems, but it does provide some of the raw components to unblock people building...

RE: https://github.com/microsoft/reverse-proxy/issues/1095

There are two parts to this problem. A) inbound requests - WebApplicationFactory/TestServer _should_ work for this part, YARP runs in a normal ASP.NET app. B) outbound request - You'd need...