Availability: Adds optimization to reduce metadata calls for addresses

[j82w]

Pull Request Template

Description

If multiple requests are running it's possible that one request refreshes the cache.
Old:

sequenceDiagram
    participant Request1
    participant Request2
    Request1->>GatewayAddressCache: Force refresh partition key range 0
    GatewayAddressCache->>Cosmos Gateway: Get addresses for range 0
    Request2->>GatewayAddressCache: Get partition key range 0
    GatewayAddressCache->>Request2: Return [1,2,3,4]
    Cosmos Gateway->>GatewayAddressCache: Return [1,2,3,5]
    GatewayAddressCache->>Request1: Return [1,2,3,5]
    Request2->>GatewayAddressCache: Force refresh partition key range 0
    GatewayAddressCache->>Cosmos Gateway: Get addresses for range 0
    Cosmos Gateway->>GatewayAddressCache: Return [1,2,3,5]
    GatewayAddressCache->>Request2: Return [1,2,3,5]

Loading

New optimized:

sequenceDiagram
    participant Request1
    participant Request2
    Request1->>GatewayAddressCache: Force refresh partition key range 0
    GatewayAddressCache->>Cosmos Gateway: Get addresses for range 0
    Request2->>GatewayAddressCache: Get partition key range 0
    GatewayAddressCache->>Request2: Return [1,2,3,4]
    Cosmos Gateway->>GatewayAddressCache: Return [1,2,3,5]
    GatewayAddressCache->>Request1: Return [1,2,3,5]
    Request2->>GatewayAddressCache: Force refresh partition key range 0
    GatewayAddressCache->>Request2: Return [1,2,3,5]

Loading

Type of change

Please delete options that are not relevant.

• [] Bug fix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [] This change requires a documentation update

Closing issues

To automatically close an issue: closes #IssueNumber

[ealsur]

Love the mermaid diagram!

[FabianMeiswinkel]

Nice description! Change LGTM