Residuality theory is a novel approach where the software architecture of a system emerges as a result of applying multiple stressors to the system. However, some seasoned software practitioners often design solid software architecture without knowing this theory.

We have reasons to consider that the heuristics from modern design approaches like Domain-Driven Design may well be congruent, to some extent, with what residuality theory would suggest. This talk by the author of the theory (Barry) and by a DDD long-timer (Cyrille) will explore the intersection between the two worlds, in a rigorous yet entertaining way.

About Cyrille Martraire

Cyrille Martraire (@cyriux) is CTO and partner at Arolla (@ArollaFr), the founder of the Paris Software Craftsmanship community and a regular speaker at international conferences. With 20+ years of experience in startups, software vendors and banks, Cyrille still calls himself a developer. He's passionate about design in every aspect: TDD, BDD and in particular DDD.

Cyrille also has an extensive knowledge of capital market finance, and he's the author of the book Living Documentation published by Addison-Wesley Professional in summer 2019.

About Barry O'Reilly

Barry is an Architect and researcher who has held Chief Architect positions at Microsoft, among others. He has also been a startup CTO, the Worldwide Lead for the Solutions Architecture Community at Microsoft, and founder of the Swedish Azure User Group. He is also a PhD candidate in software design and complexity science and the inventor of Residuality Theory.