Architecture characteristics - otherwise known as “ilities”, non-functional requirements, and system quality attributes - define the qualities an architecture must support, whether it be performance, scalability, reliability, etc. They form the basis for not only selecting the right architecture style, but also for analyzing tradeoffs to make architecture decisions. Through consulting gigs, training classes, conferences, and social media I get lots of great questions about architecture. In this lesson Mark Richards answers some of the questions he frequently gets regarding architecture characteristics.
Reference Links:
Performance vs. Responsiveness: https://www.developertoarchitect.com/lessons/lesson83.html
Scalability vs. Elasticity: https://www.developertoarchitect.com/lessons/lesson85.html
Defining Testability: https://www.developertoarchitect.com/lessons/lesson82.html
Defining Deployability: https://www.developertoarchitect.com/lessons/lesson84.html
George A. Miller: The Magic Number 7: http://psychclassics.yorku.ca/Miller/
97 Things Every Software Architect Should Know: https://www.amazon.com/Things-Every-Software-Architect-Should/dp/059652269X
The Story of the Vasa (Mark Richards): https://github.com/97-things/97-things-every-software-architect-should-know/blob/master/22.tex
The Vasa - Wikipedia: https://en.wikipedia.org/wiki/Vasa_(ship)
Software Architecture Monday: https://bit.ly/3dadEe3
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2
Training Classes: https://www.developertoarchitect.com/training/