Mission-Critical-Online/docs

Azure Mission-Critical - Reference Implementation - Solution Guide

As outlined in the Azure Mission-Critical introduction (➡️ learn.microsoft.com), Azure Mission-Critical has been developed to help customers with business critical systems to design and build a best practice Azure based solution that maximizes reliability. Azure Mission-Critical does this by giving customers prescriptive and opinionated guidance on how to build this best practice system as well as providing production ready technical artifacts for customers to quickly build that best practice system in their own environment.

Where the Azure Mission-Critical Design Principles (➡️ learn.microsoft.com) provide the thought and justification behind the Azure Mission-Critical architecture and product choices, this part of the repository tells you how to build your own production-ready Azure Mission-Critical solution using the technical artifacts provided within this repository i.e. Infrastructure-As-Code templates and CI/CD pipelines (via GitHub and Azure DevOps).

As with the Azure Mission-Critical Design Guidelines, the Reference Implementation section is divided into eight Design Areas, each giving clear instructions on how the solution is configured. When you are ready to start, the Getting Started guide outlines the process and required steps to deploy Azure Mission-Critical in your environment, including preparing Azure DevOps pipelines.

Design Areas

• Application Design
• Application Platform
• Networking anc connectivity
• Data Platform
• Deployment and testing
• Health Modeling

Additional content

• Business Continuity / Disaster Recovery
• SLO and Availability
• Operational Procedures
  • Key and Secret Rotation
• Networking Custom Domains
• Adding API Management
• ESLZ Alignment

Source Code Documentation

• Infrastructure
  • Terraform-based IaC
  • Grafana
• Application
  • Catalog Service
  • Health Service
  • Background Processor
  • UI Application
  • Unit Tests
  • Unit Tests
• Deployment Pipelines
• Configuration
• Testing

Helpful Information

• Getting started (or using CLI) outlines the process and required steps to deploy Azure Mission-Critical in your environment, including preparing Azure DevOps pipelines. It should be read in tandem with the Reference Implementation guidance.
• SLO and Availability outlines the SLO for Azure Mission-Critical (99.95%) and how this figure was calculated.
• Troubleshooting collects solutions to known issues during development and deployment.

Documentation Conventions

• Overarching topics concerning the Azure Mission-Critical architecture, design principles, design decisions, and cross-component integration are documented as separate markdown documents within the /docs/ folder.

• Each source code component for the reference implementation has it's own README.md file which explains how that particular component works, how it is supposed to be used, and how it may interact with other aspects of the Azure Mission-Critical solution.

  • Within the main branch, each README.md file must accurately represent the state of the associated component which will serve as a core aspect of PR reviews. Any modifications to source components must therefore be reflected in the documentation as well.

---

Azure Mission-Critical - Full List of Documentation

---

Azure Mission-Critical - Full List of Documentation