David Tielke
Modern software architectures
#1about 5 minutes
Understanding the business impact of software quality
The ISO 9126 model illustrates how neglecting internal quality attributes like maintainability leads to the most expensive and long-term technical debt.
#2about 4 minutes
Differentiating system architecture, software architecture, and design
Software development involves building hierarchical structures, with system architecture defining services, software architecture structuring each service, and software design ensuring sustainable implementation.
#3about 5 minutes
Choosing the right modularization based on scope
Effective modularization depends entirely on the project's scope, which for software architecture is driven by internal quality attributes like analyzability, changeability, and testability.
#4about 4 minutes
Aligning code structure with the business domain
To maintain low complexity and high analyzability, the software's structure should directly mirror the structure of the business domain it represents.
#5about 3 minutes
Applying principles for practical software design
The Single Responsibility Principle and consistent naming patterns are crucial tools for the entire team to create a maintainable and testable software design.
#6about 3 minutes
Decoupling dependencies at every architectural level
Use the Dependency Inversion Principle with contracts or interfaces to systematically decouple dependencies between classes, components, and architectural layers.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
23:43 MIN
Aligning architecture with non-functional requirements
Why (most) software projects fail silently...
00:04 MIN
The myth of future-proof software architecture
There is no such thing as future-proof architecture! Here is how to prepare for it.
24:47 MIN
Understanding critical architectural trade-offs and anti-patterns
Azure-Well Architected Framework - designing mission critical workloads in practice
04:37 MIN
Why architecture must evolve iteratively
There is no such thing as future-proof architecture! Here is how to prepare for it.
08:37 MIN
Addressing the challenge of growing software complexity
Model Based Systems Engineering in an Agile Product Development Process
02:41 MIN
The primary goal of software architecture is speed
Why you shouldn’t build a microservice architecture
23:08 MIN
Prioritizing business requirements over technical trends
Autonomous microservices with event-driven architecture
16:57 MIN
The danger of a future-proof mindset
There is no such thing as future-proof architecture! Here is how to prepare for it.
Featured Partners
Related Videos
We (don't) need a software architect!?!
Hendrik Lösch
Resolving technical debts in software architecture
Carola Lilienthal
There is no such thing as future-proof architecture! Here is how to prepare for it.
Eberhard Wolff
The Lifehacker's Guide to Software Architecture
Julian Lang
Move fast with Software Architecture
Simon Lasselsberger
Architectures that we can use with .NET
Alexej Sommer
Building Systems that Last
Werner Vogels
Why (most) software projects fail silently...
Hendrik Lösch
From learning to earning
Jobs that call for the skills explored in this talk.

Solution Architect (m/w/d)
DMG MORI Digital GmbH
München, Germany
Intermediate
Senior
Cloud (AWS/Google/Azure)

IT-Architekt*in (m/w/d)
Deutsche Fachpflege Holding GmbH
Frankfurt am Main, Germany
Senior
Enterprise Architecture
Cloud (AWS/Google/Azure)



Principal Backend Architect - Java Refactoring & Modernization
primion Technology GmbH
Remote
API
XML
Java
Spring
+3

Principal Backend Architect - Java Refactoring & Modernization
primion Technology GmbH
Remote
API
XML
Java
Spring
+3


