tubeshowcase●1,671,863 videos♡ My collection 0
← Learn to Code

Learn to Code15:02

Armchair Architects: Architectural Erosion and Technical Debt

Microsoft Developer ↗

From the creator

Changes in requirements, infrastructure, or customer habits, plus other technical and business disruptions can lead to differing levels of architectural erosion, which in turn can cause technical debt, depending on how you react to the changes. In this episode of the #AzureEnablementShow, David Blank Edelman discusses with Uli and Eric (@mougue)—our #ArmchairArchitects—how to identify when architectural erosion requires a fresh start, and what technical debt can be acquired when implementing quick fixes. Resources • Get Trained on How to Identify technical debt https://learn.microsoft.com/en-us/training/modules/identify-technical-debt/ • Design workload architectures before migration https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/migrate/migration-considerations/assess/architect • Apply design principles and advanced operations https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/manage/design-principles • Read Uli’s 2006 paper: A Business-Oriented Foundation for Service Orientation https://cdn.ymaws.com/www.businessarchitectureguild.org/resource/resmgr/homann_article_on_capabiliti.pdf • Article: 7 Steps For Inventing The Future https://www.forbes.com/sites/chunkamui/2017/04/04/7-steps-for-inventing-the-future/?sh=2f814fd133bf • Microsoft Research https://www.microsoft.com/research/ To watch more episodes in the Well-Architected series, check out our playlist: https://aka.ms/azenable/yt/wa-playlist To watch more episodes in the Armc

Published 2023-02-14 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.

Keep exploring Learn to Code