# microsoftlearning/az-204-developingsolutionsformicrosoftazure architecture

> Architecture diagram of the GitHub repository microsoftlearning/az-204-developingsolutionsformicrosoftazure, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-02-14). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure
- Repository: https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure

## Overview

##### Project Type and Purpose
- The repository is an educational lab resource for the AZ-204 course.
- It contains modular labs exploring various Azure solutions: from full-stack API/web apps (e.g., Lab 01), serverless functions (Lab 02 and Lab 07), container-based solutions (Lab 05), identity and access management using OIDC (Lab 06), and several messaging/event publishing scenarios (Labs 09 & 10), among others.

##### File Structure
- Top-level directories include .github, .vscode, Allfiles, and Instructions – with Allfiles being the primary repository for lab examples.
- Within Allfiles, the “Labs” directory is segmented by numbered labs (e.g., Labs/01, Labs/02, … Labs/14). Inside each lab folder, you notice a “Starter” (the lab’s initial template) and a “Solution” (the completed lab).
- Each lab demonstrates specific architectural patterns and technologies (e.g., Lab 01 separates API and Web projects, Lab 04 (AdventureWorks) splits the system into a data context, models, upload, and web application, etc.).
- The presence of multiple .csproj files, solution files, Dockerfiles, and configuration files (e.g., appsettings.json) hints at projects built using .NET Core, ASP.NET Core MVC for web apps, Azure Functions for serverless, Docker containers, and integration with various Azure services.

##### README for Additional Insights

a. Main Components
- Lab Delivery Manager: A top-level component that groups all the labs.
- Individual Labs: Each numbered lab (e.g., Lab 01, Lab 02, etc.) is its own module.
– Within some labs, split further into sub-components:
- API Components (e.g., Lab 01’s API project, Lab 11’s Simple API)
- Web Components (e.g., Lab 01’s Web project, Lab 06’s OIDCClient web app, Lab 13/14 web apps)
- Serverless Functions (e.g., Labs 02 and 07)
- Data Access Components (e.g., Lab 04’s AdventureWorks Context & Models)
- Messaging/Event Components (e.g., Labs 09 & 10 with MessagePublisher/MessageReader)
- Containerization (e.g., Lab 05 with Dockerfile)
- Supporting Materials: “Instructions” for demos, exercises, and labs which serve as guidance and not part of the execution runtime.
- Developer & Contributor Infrastructure: Files and directories like .github and .vscode which support collaboration and code quality.

b. Relationships and Interactions:
- Within each lab module, show how the different sub-projects interact (e.g., the API sends data to the Web app, or the Function App processes data and interacts with storage).
- External integrations where applicable (e.g., Azure Storage, Cosmos DB, Azure AD for OIDC, or Docker container orchestration).

c. Architectural Patterns and Design Principles:
- Component Isolation: Each lab is isolated (Starter and Solution) to demonstrate individual concepts.
- Use of MVC: Many web labs (with Pages, Controllers) leverage MVC or Razor Pages patterns.
- Microservices and Serverless: Some labs (Functions, Messaging) illustrate decoupled designs using Azure Functions and messaging patterns.
- Infrastructure-as-Code: Presence of Dockerfiles and configuration scripts hints at automated and repeatable deployments.

d. Relevant Technologies, Frameworks, or Libraries:
- .NET Core/ASP.NET Core (indicated by .csproj and Program.cs files).
- Azure Functions for serverless computing.
- Docker technology (Lab 05 Dockerfile).
- Identity management with OIDC (Lab 06).
- Frontend libraries and frameworks like Bootstrap and jQuery (various web labs).

##### Final Recommendations
- While it might be tempting to include every lab’s internal detail, focus on a high-level modular depiction that captures the pedagogical purpose.

## Diagram (Mermaid)

```mermaid
flowchart TD
    M["Lab Delivery Manager"]:::manager

    subgraph "Lab 01: Full-Stack"
        L01_API["Lab 01 API"]:::api
        L01_Web["Lab 01 Web"]:::web
        L01_API -->|"calls"| L01_Web
    end
    M --> L01_API
    M --> L01_Web

    subgraph "Lab 02: Serverless Functions"
        L02_Starter["Lab 02 Starter Function"]:::function
        L02_Solution["Lab 02 Solution Function"]:::function
        L02_Starter -->|"processes"| L02_Solution
    end
    M --> L02_Starter
    M --> L02_Solution

    subgraph "Lab 04: AdventureWorks"
        AW_Context["AdventureWorks Context"]:::data
        AW_Models["AdventureWorks Models"]:::data
        AW_Upload["AdventureWorks Upload"]:::data
        AW_Web["AdventureWorks Web"]:::web
        AW_Context --> AW_Upload
        AW_Models --> AW_Upload
        AW_Upload -->|"servesDataTo"| AW_Web
    end
    M --> AW_Context
    M --> AW_Models
    M --> AW_Upload
    M --> AW_Web

    L05["Lab 05 Containerization"]:::container
    M --> L05

    L06["OIDC Client (Lab 06)"]:::identity
    M --> L06

    subgraph "Lab 07: Serverless Functions"
        L07_Starter["Lab 07 Starter Function"]:::function
        L07_Solution["Lab 07 Solution Function"]:::function
        L07_Starter -->|"processes"| L07_Solution
    end
    M --> L07_Starter
    M --> L07_Solution

    L09["Lab 09 EventPublisher"]:::messaging
    M --> L09

    subgraph "Lab 10: Messaging"
        L10_Publisher["Lab 10 MessagePublisher"]:::messaging
        L10_Reader["Lab 10 MessageReader"]:::messaging
        L10_Publisher -->|"sendsTo"| L10_Reader
    end
    M --> L10_Publisher
    M --> L10_Reader

    L11["Lab 11 API"]:::api
    M --> L11

    L13["Lab 13 Web App"]:::web
    M --> L13

    L14["Lab 14 Web App"]:::web
    M --> L14

    SM["Supporting Materials (Instructions)"]:::support
    M --> SM

    DC["Dev & Contrib (.github)"]:::dev
    M --> DC

    VC["VSCode (.vscode)"]:::dev
    M --> VC

    %% Click Events
    click M "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs"
    click L01_API "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/01/Starter/API"
    click L01_Web "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/01/Starter/Web"
    click L02_Starter "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/02/Starter/func"
    click L02_Solution "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/02/Solution/func"
    click AW_Context "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/Allfiles/Labs/04/Solution/AdventureWorks/AdventureWorks.Context"
    click AW_Models "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/Allfiles/Labs/04/Solution/AdventureWorks/AdventureWorks.Models"
    click AW_Upload "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/Allfiles/Labs/04/Solution/AdventureWorks/AdventureWorks.Upload"
    click AW_Web "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/Allfiles/Labs/04/Solution/AdventureWorks/AdventureWorks.Web"
    click L05 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/05/Solution/Dockerfile"
    click L06 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/06/Solution/OIDCClient"
    click L07_Starter "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/07/Starter/func"
    click L07_Solution "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/07/Solution/func"
    click L09 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/09/Starter/EventPublisher"
    click L10_Publisher "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/10/Starter/MessagePublisher"
    click L10_Reader "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/10/Starter/MessageReader"
    click L11 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/11/Solution/Api"
    click L13 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/13/Starter/webapp-sam-lab13"
    click L14 "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Allfiles/Labs/14/Starter/webapp-lab14"
    click SM "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/tree/master/Instructions"
    click DC "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/.github"
    click VC "https://github.com/microsoftlearning/az-204-developingsolutionsformicrosoftazure/blob/master/.vscode"

    %% Styles
    classDef manager fill:#aqua,stroke:#000,stroke-width:2px;
    classDef api fill:#FFA07A,stroke:#000,stroke-width:1px;
    classDef web fill:#90EE90,stroke:#000,stroke-width:1px;
    classDef function fill:#FFD700,stroke:#000,stroke-width:1px;
    classDef data fill:#FFB6C1,stroke:#000,stroke-width:1px;
    classDef container fill:#D3D3D3,stroke:#000,stroke-width:1px;
    classDef identity fill:#FFE4B5,stroke:#000,stroke-width:1px;
    classDef messaging fill:#FFDEAD,stroke:#000,stroke-width:1px;
    classDef support fill:#AFEEEE,stroke:#000,stroke-width:1px;
    classDef dev fill:#E6E6FA,stroke:#000,stroke-width:1px;
```
