Lab: Blob and Queue Storage with Azurite

What you will learn in this TP

• Use Azurite and the development connection string
• Work with containers, blobs and SAS
• Send and consume queue messages

Introduction #

What you will learn in this section

• Use Azurite and the development connection string
• Work with containers, blobs and SAS
• Send and consume queue messages

Context. An application must store invoices and notify a processing service. You prototype storage and the queue on the official emulator before moving to Azure.

Prerequisites: Docker, Azure CLI, Azure Functions Core Tools and Python 3; the Azurite emulator (docker run mcr.microsoft.com/azure-storage/azurite) replaces Azure storage: no subscription required  ·  Estimated time: 40 min

Organised blobs, a time-limited SAS link and a working message queue.

Hands-on #

Guided steps, with their solution.

1. 1. Start Azurite

   Why? Azurite exposes Blob (10000), Queue (10001) and Table (10002) with a well-known development account.

   Start the emulator and export the development connection string.

2. 2. Containers and blobs

   Why? Blob names with "/" form a virtual tree, handy for organising by date.

   Create the factures container, upload two files with metadata, list them by prefix and download one.

3. 3. Share with a SAS

   Why? A SAS grants access limited in rights and time, without sharing the account key.

   Generate a read-only SAS valid for 15 minutes for one invoice and download it with curl.

4. 4. A message queue

   Why? The queue decouples invoice upload from processing.

   Create the a-traiter queue, send two messages, read one (it becomes invisible), then delete it.

Difficulty level : ●●○○○ (2/5)