In this video, Sadukie talks about the many things we need to consider as software architects and why "everything is a trade-off" is important to consider!

Contents:

0:35 - Non-Functional Requirements / "ilities" / Quality Characteristics
1:06 - Example: Security vs Usability
1:25 - Example: CAP Theorem
1:47 - Architectural Styles
2:20 - Example: Fraud Detection and Graph Databases
2:55 - Preparation and Documentation
3:40 - "I'm the architect. I don't get to pick my team."
4:10 - Data Concerns
5:13 - "When do I get to write the code?"
5:40 - Architecture is Deeper Than "Boxes and Arrows"
6:14 - It's About Understanding the Problem with a Toolbox for Solutions
6:40 - What About Clean Architecture?
7:08 - How Can You Learn About Architectures?
7:59 - Architecture Katas


🔗 Related Links:

- Learn Clean Architecture: https://bit.ly/learn-clean-architecture
- DevIQ: https://deviq.com
- Architecture Decision Records:   • Architecture Decision Records  
- Architecture Katas:    • Exploring Architecture Katas  
- Domain Storytelling:    • Domain Storytelling  
- EventStorming:    • How EventStorming Streamlines Complex...  |
- Modular Monolith:    • Modular Monolith  
- Exploring Vertical Slices, Clean Architecture, and Modular Monoliths:    • Architecting Adventures: Exploring Ve...