Azure Storage Queue

What is Azure Queue Storage 

Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue may contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously.

Attributes of Azure Queue Storage

  • Azure storage queue lives under a storage account (Azure storage account also supports blob, file share, queues, tables and disk)
  • Within a storage account, you an have multiple queues
  • Every single queue can have multiple messages
  • The size of a message can't be more than 64 KB
  • The URL format of a queue is https://<storage account>.queue.core.windows.net/<queue>
  • For example - https://learnaboutazurestorage.queue.core.windows.net/add-weatherdata

    How to Create Azure Storage account and Azure Storage Queue

    • Login to https://portal.azure.com/
    • Create a resource group (you can ignore this step, if you already have a resource group)
    • Now create a storage account under the resource group. The storage account name should be between 3 - 24 characters and can contain only lower case characters and numbers
    • To create a queue - scroll to the data storage section of the storage account and click Queue - add queue - give a meaningful name for the queue and click ok
    • Azure storage account and Azure storage queue is successfully created

    Steps to implement Azure Queue Storage functionality

    • Let's create a sample Web API and write a post method to make an entry in the queue storage
    • Add Nuget package Azure.Storage.Queues
    • Write a simple post method to add data to storage queue
    • Create an object of QueueClient which comes from the namespace Azure.Storage.Queues and takes connectionString and queueName as parameter
    • To get the connectionString, go to storage account section of Azure, click on AccessKey, and copy the value of attribute connectionString
    • Copy the queueName from Queue section of storage account
    • Use the SendMessageAsync method of queueClient to send a message to queue
    • The method will finally look like the one below
        public async Task Post([FromBody] WeatherForecast data)
            {
                var connectionString = "Your Connection String";
                var queueName = "Your Queue Name";
                var message = JsonSerializer.Serialize(data);
                var queueClient = new QueueClient(connectionString, queueName);
                 await queueClient.SendMessageAsync(message);
            }

    •  If you call the post method with some data (using swagger or postman), the entry will be visible under queue storage of Azure and it will look like the one below

    • Each record is also assigned a unique ID, inserted time, expiration time (by default 7 days, it means that the record will automatically disappear after 7 days if no one uses this before that time) and dequeue count (default is 0)
    • If we want to change the default expiration time to a different value, we can do it while creating a message into queue.
    • For this, we need to use  queueClient.SendMessageAsync(message, null, TimeSpan.FromDays(10)); In this code, 3rd parameter is expiry time. This message will be staying in Queue for 10 days instead of 7 days.
    • If we will set the expiry time to a negative value, it means that this message will never expire. We can use queueClient.SendMessageAsync(message, null, TimeSpan.FromDays(-1)); to achieve this
    • The second parameter is Visibility time - it means after how much time, the entry will appear in queue. By default all queue entries immediately appear as soon as it is created, but if we set the value of 2nd parameter to 30 seconds, then the record will appear in queue only after 30 seconds of it's creation.
    • We can use queueClient.SendMessageAsync(message, TimeSpan.FromSeconds(30), TimeSpan.FromDays(10)); to achieve the above
    • We can also use the standalone desktop version of the software Azure Storage Explorer to see everything under a storage account

    Reference URL:

    Source Code: https://github.com/kumarabhimanyu/AzureQueueWithBackgroundTask

    https://docs.microsoft.com/en-us/azure/storage/queues/storage-queues-introduction

    https://www.youtube.com/watch?v=5oTX6srQdOE&t=2s

    Read data using background Task: https://techabhimanyu.blogspot.com/2022/08/read-azure-queue-storage-from-net-core.html


    Comments

    Post a Comment

    Popular posts from this blog

    Publish .Net Core Web API to Linux Host

    Image
    Publish .Net Core Web API to Linux Host In this post below, I am going to detail out the step of publishing a .NET Core Web API to Linux Host SSH the Linux host Open any SSH client like gitbash Go to the location where the .pem file exists ssh -i <pemfilename> -v <username>@<host_IP_Address> use sudo su for super admin access to run further command Create project folder Go to /var/www folder (cd /var/www) create a new folder for the project. For example SampleWebAPI (mkdir SampleWebAPI ) Publish project in release mode Open command prompt as administrator Go to Project folder - cd <foldername> dotnet publish  --configuration release Copy latest publish code to project folder Open file transfer tool like FileZilla Connect to linux host with right credentials Copy the file from local published folder to  /var/www/SampleWebAPI  Change the Nginx configuration file Go to cd /etc/nginx/sites-available/ Edit default config file: vim default...
    Read more

    Entity Relationship Using EF Core Code First Approach

     In this section, we are going to talk about the different kind of relationship between entities and how to establish that using C# code. Followings are the type of relationship One to Many An employee can have more than 1 education details. To Achieve this, we need to have a property in employee class like the below one. public ICollection<EmployeeEducation> EducationList { get; set; } Once we do this and add the migration, it will add a new column EmployeeID in EmployeeEducations table, but as a nullable attribute. In this case, if we try to add data in EmployeeEducations table, it will set EmployeeID as null To fix this, we need to add a cross reference in the EmployeeEducation Class, to denote that Every education record must have an employee ID. This will ensure that allow null attribute of EmployeeID column in EmployeeEducations  table is set to false. public Employee Employee { get; set; } If we try to insert values in EmployeeEducations table with below code...
    Read more

    Web API Using EF Core

    Image
    What is Web API  As the name suggests, is an API over the web which can be accessed using HTTP protocol. We can build Web API using different technologies such as Java, .NET etc.  Web API breaks the limitation of language. For example a web API written in .Net can be utilized by Java and vice verssa, because the request/response format of Web API is JSON which is understood by all language. For example, Twitter's  REST APIs  provide programmatic access to read and write data using which we can integrate twitter's capabilities into our own application. We can use tools like Fiddler, PostMan and Swagger for testing Web API .Net Core Web API -   Is an Ideal platform for building RESTful services. Is built on top of ASP.NET and supports ASP.NET request/response pipeline Maps HTTP verbs to method names. Supports different formats of response data. Built-in support for JSON, XML, BSON format. C...
    Read more