From chaos to clarity: Mastering complexity with sustainable architectural work

Transcript

1. 75% FAIL!
2. COMPLICATED CONFUSION CLEAR COMPLEX CHAOTIC
4. 2025 MASTERING COMPLEXITY WITH SUSTAINABLE ARCHITECTURAL WORK FROM CHAOS TO CLARITY
5. FELIX RIESS Software Architect felix.riess@bcxp.de https://speakerdeck.com/felix185
6. Framing ▪ Motivation ▪ Goals ▪ Constraints
8. Understanding the business ▪ Event Storming ▪ Domain Storytelling
9. Event Storming
10. Event Storming
11. Event Storming
12. Strategic Domain Driven Design Bounded Context A Bounded Context B Bounded Context C
13. Strategic Domain Driven Design: Subdomains Bounded Context A Bounded Context B Bounded Context C Supporting Generic Core
14. Strategic Domain Driven Design: Context Mapping Bounded Context A Bounded Context B Bounded Context C
18. Software Architecture represents the set of significant decisions.
20. Software Product Quality (ISO 25010:2023) Functional Suitability Performance Efficiency Compatibility Interaction Capability Maintainability Reliability Flexibility Security Safety
21. Architecture Vision What? How?
22. Architecture Vision What? System context Constraints Quality goals (prioritized) Risks
23. Architecture Vision How? Big picture Concepts, patterns, principles Base technologies Hypotheses
24. Big design up front is dumb. Doing no design up front is even dumber. DAVE THOMAS
26. Organizational complexity ▪ Modularity ▪ Macro Architecture ▪ Anti-Viscosity ▪ Roles
28. Danger Zone Concepts & Patterns Platform, Language & Frameworks Conference Driven Design
29. AN ARCHITECTURAL PRINCIPLE IS A GUIDELINE FOR THE DESIGN OF ◼ an application landscape ◼ an application ◼ a component
30. An architectural principle is a generally valid, elementary instruction that can be applied to all levels of software development. Only through the sensible and appropriate use of all architectural principles can good architecture be created. Excessive use of just one principle, on the other hand, does not usually lead to good architecture.
31. OUR ARCHITECTURAL PRINCIPLES 1 SEPARATION OF CONCERNS 2 MINIMIZING DEPENDENCIES 3 PRINCIPLE OF SECRECY 4 CONTRACT- BASED DESIGN 5 LAYERING 6 REDUNDANCY- FREE 7 DATA SOVEREIGNTY 8 HOMOGENEITY 9 STRUCTURAL ORDER AND PATTERNS 10 SOFTWARE CATEGORIES
32. Our BCxP-Default-Construction Model Subsystem Daten Data < Component Type > Application Component Layers Component Interfaces Application Component Part Component Part Component Part Technical Infrastructure Technical Components Component Environment Technical Service Interfaces Component Environment Interface Subsystem Entity Types Transfer Objects
34. Wrap-up ▪ Domain Driven Design ▪ Technology is not an end in itself ▪ Appropriateness: Boring is the new cool ▪ Architecture must support evolving
35. It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove. ANTOINE DE SAINT-EXUPÉRY
36. FELIX RIESS Software Architect felix.riess@bcxp.de https://speakerdeck.com/felix185
37. Thank you! When technology becomes friendship
38. References • https://www.heise.de/blog/75-Prozent-aller-Softwareprojekt-scheitern-was-tun-9979648.html • https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 • https://dev.to/simonbrown/software-architecture-isn-t-about-big-design-up-front-4hol • Moderne Softwarearchitektur: Umsichtig planen, robust bauen mit Quasar (Johannes Siedersleben) • Vorgehensmuster für Softwarearchitektur (Stefan Toth)
39. Images • https://unsplash.com/de/fotos/rsGd-rXFGkM • https://unsplash.com/de/fotos/1K9T5YiZ2WU • https://unsplash.com/de/fotos/bH7kZ0yazB0 • https://unsplash.com/de/fotos/person-im-schwarzen-langarmhemd-halt-die-hand-einer-person- Y5bvRlcCx8k?utm_content=creditShareLink&utm_medium=referral&utm_source=unsplash • https://unsplash.com/de/fotos/VBPzRgd7gfc