Episode

Designing a mission-critical workload on Azure

with David Blank-Edelman, Sebastian Bader, Martin Simecek

Azure Essentials Show

Do you design, build, or run a mission critical app for your organization? In this installment of the Azure Enablement Show, David Blank-Edelman is joined by Sebastian Bader and Martin Simecek from Microsoft Azure for a deep dive on how to get started designing, deploying, and monitoring mission critical applications, including a look at reference architectures and explanation of some of the terminology.

Chapters

  • 00:00 - Introduction
  • 01:20 - How does Microsoft define 'mission critical' on Azure?
  • 02:35 - What's the difference between 'mission critical' and 'well-architected'?
  • 03:30 - What are the two main components of the mission critical guidance?
  • 05:57 - An example of a baseline reference architecture diagram
  • 08:00 - Why does Microsoft recommend Azure Front Door instead of Traffic Manager?
  • 08:52 - What is the relationship between the regions and stamps?
  • 10:08 - What is the role of Azure Pipelines and GitHub?
  • 11:26 - How do customers deploy and manage the stamps?
  • 13:18 - How should customers think about different environments, like staging and production?
  • 14:57 - How does monitoring work in a mission critical world?
  • 17:25 - Are there reference architectures for more complex scenarios, such as those needing Azure Landing Zones?

Connect

Azure