How microsoftlearning/dp-420-cosmos-db-dev works
The project is not a production application per se but rather a curated, lab-based repository that supports a Microsoft course (DP-420) on “Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB.” Its purpose is to provide both lab instructions and code samples/demos that showcase various aspects of using Azure Cosmos DB—from connectivity and CRUD operations to performance measurement and indexing strategies. In short, the repository is divided into multiple lab modules (each in its own numbered directory) and a parallel set of instructions to guide both instructors and students through the labs.
Main Components
• Instruction Content: The “instructions” folder holds detailed markdown files guiding users through each lab. This should be represented as a separate component labeled “Lab Instructions” or “Teaching Guides.”
• Data and Configuration Files: The “data” folder (with its nested subdirectories) and configuration files (such as .gitignore, azuredeploy.json, deploy.bicep for container creation, etc.) suggest a shared environment for test data, deployment templates, and sample configuration. This can be shown as “Sample Data & Configuration.”
Relationships and Interactions
• Instructional Flow: Connect the “Lab Instructions” component to all lab modules to indicate that each lab module’s code is guided by corresponding documentation.
• External and Deployment Interactions: Illustrate how specialized labs (e.g., container deployment with ARM/bicep templates, key vault scenarios) engage with additional Azure services.
Architectural Patterns and Design Principles
• Separation of Concerns: The clear split between “lab instructions” and “lab code” demonstrates that business logic (or demo functionality) is decoupled from process documentation.
• Educational / Demo Focus: Emphasize that the repository’s design is tailored to hands-on learning and experimentation with Azure services, not a single production-grade system.
Relevant Technologies, Frameworks, or Libraries
• .NET (C#): The presence of .csproj, .cs scripts, and C# files indicates that each lab module is built using .NET.
• Azure-specific Templates: ARM and Bicep files are used in deployment scenarios.
• Azure Cosmos DB: Central to all the labs.
• MVC (in the case of the “28-key-vault” folder), and possibly Razor pages (Index.cshtml) suggest ASP.NET or related web technologies where needed.
• GitHub for collaboration, with standard templates for pull requests and issues.