We all know that algorithms are everywhere. I studied algorithms and data structures in the university, but I don't know them good enough. So I decided to enroll into Data Structures and Algorithms, University of California, San Diego & Higher School of Economics on Coursera. I hope it will be a good experience and lots of fun. I already know half of the material and used some of the advanced algorithms and data structures during my study in university, but I still have lots of gaps.
In previous post I have described stored access policies and provided basic code samples. In this post I am going to discuss another topic - attributes and metadata. Attributes is simple properties, metadata for a queue is stored as name-value pairs.
In the previous post I have described Shared Access Signature mechanism. In this post am going to talk about Stored Access Policies and how it should be used with SAS.
In the previous post I described OperationContext class and provided basic usage examples. In this post I am going to focus on the shared access signature concept.
In the previous post I described how QueueRequestOptions can be used and provided simple examples. In this post I will continue to work with Azure Storage Queue. I am going to describe an important parameter OperationContext.
In the previous post I described how MessageId and PopReceipt can be used and provided simple examples. In this post I will continue to work with Azure Storage Queue Service. I am going to describe an important parameter QueueRequestOptions.
In the previous post I described how to work with Azure Storage Queue Service and provided simple examples. In this post I will continue to work with Azure Storage Queue Service. I am going to describe more advanced scenarios and showcase them in code.
There are many ways to interact with Azure Storage Queue, one of them is from C# code using Windows Azure Storage Library. This client library enables working with the Microsoft Azure storage services which include the blob and file service for storing binary and text data, the table service for storing structured non-relational data, and the queue service for storing messages that may be accessed by a client. In this post I will show how to work with Azure Storage Queue Service.
Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. It provides cloud messaging between application components. In designing applications for scale, application components are often decoupled, so that they can scale independently. Queue storage delivers asynchronous messaging for communication between application components, whether they are running in the cloud, on the desktop, on an on-premises server, or on a mobile device. Queue storage also supports managing asynchronous tasks and building workflows.
There are two ways to manage resources in Azure: Classic and Resource Manager. Resource Manager is the recommended way now, you can read more about resource manager at Azure Resource Manager overview. Microsoft will enable Resource Manager for every service that is important for future solutions, but until the support is consistent, you need to know the current status for each service. For example it is possible to use Azure Storage cmdlets in a resource manager context, you can mix them easily.