Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Armchair Architects: Architectural Erosion and Technical Debt

Microsoft Developer
588K subscribers
<__slot-el>
<__slot-el>
1.3K views 2 years ago #Azure #AzureEnablementShow #ArmchairArchitects
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/tra... • Design workload architectures before migration https://learn.microsoft.com/en-us/azu... • Apply design principles and advanced operations https://learn.microsoft.com/en-us/azu... • Read Uli’s 2006 paper: A Business-Oriented Foundation for Service Orientation https://cdn.ymaws.com/www.businessarc... • Article: 7 Steps For Inventing The Fut …...more
...more

Introduction

0:00

Architectural erosion as defined by Eric

0:51

Uli adds the concepts of technical and business disruption to Eric’s definition

2:30

Uli mentions his 2006 paper “A Business-Oriented Foundation for Service Orientation” (link below)

4:55

Architectures should have half-lives

5:34

Eric discusses three levels of erosion: large technology disruptions, slow erosion, and living architecture

7:18

Keep in mind that business models take much longer to change

9:12

Uli paraphrases Alan Kay “the best way to predict the future is to invent it”

10:43

Research organizations help to identify signals coming from outside sources, like academia

10:58

How do identify if you’re in a situation that requires a fresh start

12:11
Armchair Architects: Architectural Erosion and Technical Debt
31Likes
1,389Views
2023Feb 14
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/tra... • Design workload architectures before migration https://learn.microsoft.com/en-us/azu... • Apply design principles and advanced operations https://learn.microsoft.com/en-us/azu... • Read Uli’s 2006 paper: A Business-Oriented Foundation for Service Orientation https://cdn.ymaws.com/www.businessarc... • Article: 7 Steps For Inventing The Future https://www.forbes.com/sites/chunkamu... • 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 Armchair Architects series, check out this playlist! https://aka.ms/armchairarchitects Chapters 0:00 Introduction 0:51 Architectural erosion as defined by Eric 2:30 Uli adds the concepts of technical and business disruption to Eric’s definition 4:55 Uli mentions his 2006 paper “A Business-Oriented Foundation for Service Orientation” (link below) 5:34 Architectures should have half-lives 7:18 Eric discusses three levels of erosion: large technology disruptions, slow erosion, and living architecture 9:12 Keep in mind that business models take much longer to change 10:43 Uli paraphrases Alan Kay “the best way to predict the future is to invent it” 10:58 Research organizations help to identify signals coming from outside sources, like academia 12:11 How do identify if you’re in a situation that requires a fresh start #AzureEnablementShow #ArmchairArchitects #Azure

Follow along using the transcript.

Microsoft Developer

588K subscribers