What is the Fault tolerance, recovery, availability SLA for WCF relays created via Azure Relays service

Shagil IMAM 0 Reputation points
2024-10-31T04:43:53.1833333+00:00

What is the fault tolerance mechanism, recovery method, availability, and/or SLA for WCF relays created via Azure Relays service? I cannot find any documentation around this.

Azure Service Bus
Azure Service Bus
An Azure service that provides cloud messaging as a service and hybrid integration.
633 questions
Azure Fluid Relay
Azure Fluid Relay
An Azure service used to add real-time collaborative experiences to apps with Fluid Framework.
4 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Khadeer Ali 570 Reputation points Microsoft Vendor
    2024-11-04T01:08:56.2766667+00:00

    Hi Shagil IMAM,

    Azure Relays doesn't explicitly provide detailed documentation on the specific fault tolerance mechanisms, recovery methods, and SLAs for WCF Relays

    For WCF relays created via Azure Relay, the service offers an SLA of 99.9% availability, meaning that properly configured applications should be able to establish a connection to a deployed relay 99.9% of the time. This SLA is consistent across Azure's Service Bus Relays, which includes both WCF relays and Hybrid Connections.

    In terms of fault tolerance and recovery, Azure Relays rely on the broader fault-tolerance mechanisms inherent in Azure's infrastructure. If a relay connection drops, applications can generally reconnect automatically if they are configured to handle transient faults using retry policies, a best practice for Azure services. However, the service does not offer built-in redundancy or failover within a relay itself. Instead, you would need to architect the application to handle connectivity interruptions, especially for critical applications.

    If you find this answer helpful, please click "Accept Answer" and kindly upvote it.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.