The ability to cancel long-running tasks is important to help keep applications responsive. Whether the network connection is slow or disconnects, or the user just wants to cancel a long task, using a [`CancellationToken`][CancellationToken] in .NET makes it easy to cancel those long tasks.
Cancelling in-progress network operations is critical for applications to maintain responsiveness and avoid doing work that isn't needed anymore. There are many situations where you want to cancel on-going work. This article shows you how it is done.
This month, we have updated the App Configuration, Event Hubs, Key Vault, and Storage libraries. We've also released new previews for Cognitive Search, Event Hubs, Service Bus, and Text Analytics.
In my position with the Azure SDK team, I'm fortunate to talk to a lot of customers about their needs. Most applications can be categorized into big buckets where we can see the same design patterns repeated. One of those categories is data processing.
If you are developing an ASP.NET Core application, you know that there is a common way of structuring your application. The tooling within Visual Studio makes this very easy to accomplish. Similarly, when integrating the AZURE SDK, there are good and bad ways to structure your code. This article covers the best practices.
Todays topic is diagnostics with Python applications. I have a fairly complex application, and something is going wrong. Azure provides a capability within Azure Monitor called transaction monitoring that tracks a transaction (such as an API call) from your application all the way through to the service that fulfills the request. This is power
This months release contains updates to App Configuration, Event Hubs, Key Vault, and Storage, with new previews for Azure Identity, Cognitive Search, Cosmos DB, Key Vault, and Text Analytics.
The Azure SDK team generates many client libraries across multiple languages, so it should come as no surprise that we constantly think about the most efficient mechanism for storing, writing, and distributing those libraries. In an ongoing series, we're going to talk about some of the decisions we made and the implications of those decisions. The...
When we re-imagined the Azure SDK, we came up with some key principles that we would use when writing the SDK: There are more details behind these simple principles, but these are our guides when designing the client libraries. When we designed the initial HTTP pipeline for the Azure SDK for Java, we made specific choices that are well kno...
How do your apps identify themselves to the cloud resources you are using? This is one of the most important considerations when building a cloud-native app. When you write a service, you should be able to take the same code and run it on your dev box and in any of the Azure clouds without code changes.
