Architecture is often shaped early on by technological choices, such as frameworks, patterns and deployment models. But what if we reversed that process? What if architecture emerged only from the quality goals of a system?

This talk introduces Domain-Driven Architecture: an approach that derives architectural structure directly from non-functional requirements, or quality goals. Inspired by Domain-Driven Design, this approach explicitly applies those principles to architectural decision-making rather than just modelling.

Using real project examples, including successes and failures, I will demonstrate how systems can evolve over time, emphasizing loose coupling and intentional boundaries. This approach enables systems to change in a targeted and controlled way without becoming locked into premature technology decisions.

The presentation is aimed at software architects and developers who view architecture as an evolutionary discipline that can be consciously designed, evaluated and refined as the domain and its requirements evolve, rather than as a fixed blueprint.