I want to know how much you cover some aspects of design architectures, like Domain-Driven Design in your book. Briefly, what's your opinion about DDD and on what type of projects it could be better suited?
Hi Manassés. Although my book is about software design, it's not about any specific design approach. It's actually agnostic of design approaches, technologies and architectural patterns. Instead, my book is about a higher level view of software architecture and looks at the sort of things that teams really should think about before they start coding ... but these are lightweight practices rather than big design up front.
I'm not a DDD expert by any means, but my understanding is that it's suited to teams who want to take a more OO approach to software development, where the business domain has some complexity. If I'm honest, I don't personally see many teams "doing DDD", although they do often use some of the underlying principles.
subject: Software Architecture for Developers - DDD