Reputation: 1990
When we first migrated to Azure, transient fault handling via the Enterprise Application Block 5.0 was the best game in town. We use it to automatically perform retries when getting an Azure SQL Connection, accessing ASP.NET Session objects and accessing ASP.NET Application objects. To do so, we make use of the following classes respectively:
Now according to Microsoft's Transient Fault Handling Patterns and Practices as of March 2014:
Recent versions of SDKs for both Azure Storage and Azure Service Bus natively support retries. It is recommended to use these instead of the Transient Fault Handling Application Block
What Azure SDK classes should we use to replace our dependencies on deprecated Enterprise Application Block Transient Fault Handling?
Upvotes: 1
Views: 815
Reputation: 2698
Please follow the following blog posts to implement retry logic(These are ADO.NET samples but you can replicate the logic in the language of your choice) https://msdn.microsoft.com/library/azure/ee336243.aspx
https://msdn.microsoft.com/en-us/library/azure/dn961167.aspx
The first one is implementing retry logic using the Enterprise Library and the second one shows you how to implement retry logic using custom code.
To answer your question :
What Azure SDK classes should we use to replace our dependencies on deprecated Enterprise Application Block Transient Fault Handling? You will have to use retry logic to improve connection resiliency. Unfortunately there is no Azure SDK that you can use currently to implement retry logic to connect to Azure SQL DB.
Let me know if this makes sense.
Best,
Meet Bhagdev
Program Manager, Microsoft
Upvotes: 3
Reputation: 1594
This site has examples for the native client support for each service
https://github.com/mspnp/azure-guidance/blob/master/Retry-Service-Specific.md
Upvotes: 1