Do our #ArmchairArchitects think differently about the architectural patterns and characteristics of applications that are mission critical? On this episode of the #AzureEnablementShow, Uli, Eric (https://www.youtube.com/channel/UCbQ5FSOvQ311EM3v_e7QwlQ) and David have a lively discussion about what architects need to consider when designing solutions such as emergency services that must always work. The discussion continued even after the cameras stopped rolling, so be sure to catch the Mission Critical Apps bonus episode (https://aka.ms/azenable/86) to see where the conversation went next! Resources • Azure Architecture Center https://aka.ms/azenable/82/01 • Microsoft Azure Well-Architected Framework https://aka.ms/azenable/82/02 • Cloud Design Patterns https://aka.ms/azenable/85/01 • Azure Monitor overview https://aka.ms/azenable/85/02 • Blog: Guidance for Architecting Mission Critical Apps on Azure https://aka.ms/azenable/85/03 Related Episodes • Armchair Architects https://aka.ms/armchairarchitects • Well-Architected Series https://aka.ms/azenable/yt/wa-playlist • Azure Enablement Show https://aka.ms/azenable • Armchair Architects: Architecting Mission Critical Apps (bonus episode) https://aka.ms/azenable/86 Chapters 00:00 Introduction 01:09 How is the architecture for mission critical apps different than for other apps? 02:22 Do we need to treat this class of applications differently than other apps? 04:17 Does mission criticality mean more expense? 07:37 Can mission critical apps have different levels of availability and performance? 08:15 Within a solution, can workloads can be mission critical for different reasons? 11:45 Would an architect ever plan on changing design patterns on the fly? #AzureEnablementShow #Armchair Architects #Azure