Join us this February for an insightful exploration of how quality requirements and Domain-Driven Design can work together to create robust, maintainable software systems.
Stefan Priebsch: Domain-Driven Architecture
What if architecture didn’t start with frameworks and tech stacks, but with quality goals? Domain-Driven Architecture flips the script: architectural structure emerges from non-functional requirements, not premature technology choices. Inspired by Domain-Driven Design, it applies domain thinking directly to architectural decisions.
Through real-world successes and failures, this talk shows how clear boundaries and loose coupling enable systems to evolve safely over time. Without locking you into early decisions.
For architects and developers who see architecture as intentional, evolutionary, and continuously refined, not a fixed blueprint.
Stefan is widely considered a leading expert on software development.
I'm a software success consultant specializing in software architecture, design patterns, object-oriented design, and the design, build, and maintenance of complex systems.
He firmly believes that not technology, but humans should be put first. This is why Stefan uses and teaches Domain-Driven Design.
Stefan is an Open Source advocate and helped found The PHP Foundation. He is the CEO and Co-Founder of The PHP Consulting Company (thePHP.cc).
Matthias Kolb: SOLID APIs - Five Principles for Interface Design That Actually Scale
While SOLID principles have long been cornerstones of object-oriented design, their application to API design remains surprisingly underexplored. This discussion examines how each SOLID principle translates to RESTful APIs, offering practical strategies for building more maintainable, extensible, and resilient interfaces.
We'll explore how the Single Responsibility Principle guides endpoint design, how the Open/Closed Principle influences versioning strategies, and how Interface Segregation shapes resource modeling. Through real-world examples and anti-patterns, we'll demonstrate how SOLID principles can help teams avoid common API pitfalls such as endpoint sprawl, breaking changes, and tight service coupling. Whether you're designing microservices, public APIs, or internal service layers, these principles provide a robust framework for making better architectural decisions.
Matthias is a seasoned software architect. He is passionate about robust and resilient software. He enables teams to build better software.
