Armchair Architects: The role of Simplicity in Architecture

What are the tradeoffs between robust functionality, flexibility, simplicity, and ease of operation? How do our #ArmchairArchitects, design solutions that start as high as they want and go as low as they need? Uli, Eric, and David discuss these questions and more in this episode of the #AzureEnablementShow.
Resources
• Azure Architecture Center aka.ms/azenable/82/01
• Microsoft Azure Well-Architected Framework aka.ms/azenable/82/02
• Ten design principles for Azure applications aka.ms/azenable/84/01
• Rest API aka.ms/azenable/84/02
• Azure Event Grid aka.ms/azenable/84/03
• Scale units in a distributed hybrid topology aka.ms/azenable/84/04
Related Episodes
• Armchair Architects aka.ms/armchairarchitects
• Well-Architected Series aka.ms/azenable/yt/wa-playlist
• Azure Enablement Show aka.ms/azenable
Connect
David Blank-Edelman intent/follow?ori...
Eric Charran intent/follow?ori...
Chapters
[00:00] Introduction
[01:22] What role does simplicity play when architecting solutions?
[04:35] Is it possible to retain simplicity when adding features?
[07:00] Does new functionality require more complexity?
[09:52] How do architects think about simplicity vs. complexity?
[12:37] How should architects think about creating vs. reusing?
[13:15] How can simplicity impact the ability to maintain and update a solution?

[@erril8285]

I totally agree, simplicity is very important when architecting an application. Many people think that, the faster I create an application the better and they also throw several third party packages in, to accelerate the creation process, but at the end, they end up with a very hard to understand code with third party packages which later on nobody will remember what they actually do. We read code far more often than writing it! Therefore when developing, we should constantly think: Is this code easy to read and understand? If not, then split your code into different functions and give them appropriate names. Being more declarative.