Azure PaaS lab

Small app, visible infrastructure path

Use this app to watch a web request touch the same kinds of parts you will inspect in Azure: app host, database, blob storage, queue, worker, and telemetry.

Environment azure Version 0.1.0 Queue mode Service Bus

1. Create task

Component map

web host
Flask local server; later Azure App Service
task store
SQLite at /home/site/data/lab.db; later Azure SQL Database
blob store
Azure Blob Storage container lab-notes
queue
Azure Service Bus queue lab-jobs
worker
Local process button; later Azure Function queue trigger

Tasks

Health probe

Task #5

Trace one Azure dependency path

Created from the Flask web app.

Status: queued | Message: ff2689c603

Task #4

Trace one Azure dependency path

Created from the Flask web app.

Status: queued | Blob: lab-notes/task-4-c73a6401.txt | Message: ddf86c4de0

Task #3

Finish lab build

Finish this build under $200

Status: queued | Blob: lab-notes/task-3-ef23a1d0.txt | Message: 4f90aff153

Task #2

Trace one Azure dependency path

Created from the Flask web app.

Status: queued | Message: cfd375b046

Task #1

Trace one Azure dependency path

Created from the Flask web app.

Status: queued | Blob: lab-notes/task-1-72b806e9.txt | Message: db9081bc3b

4. Process next queued job

This simulates the queue-triggered Function App. In Azure, Service Bus will trigger a Function instead of this local button.

What to look for

  • Task rows are the SQL part.
  • Attached notes are the Blob Storage part.
  • Queued jobs are the Service Bus part.
  • Processing is the Function App part.
  • The health probe is the public-safe monitoring check.