Domain-Driven Design: Tackling Complexity in the Heart of Software

This is a serious book, it's an excellent read. To anyone who provides a negative comment on this book, it's because you don't understand it. To those who say the book is dull, are totally missing the point. This book deserves respect for the new paradigm being described and the clear and well structured way it has been described and explained. Its very possible you may need to have a certain level of experience and knowledge to get the most out of this book, but I think anyone who carefully reads the book, and looks up the things they may not be familiar with, will gain a great understanding of the subject. Do not expect to be an expert on the first few readings. First read it and understand the core concepts. After that using these ideas and approach on real projects, requires commitment and patience. The author says it's not easy to implement, but it is very effective and provides a solid long term approach. DDD might not be for all projects, but all software developers, and project managers should be aware of this paradigm and recognise the importance which DDD has.

This is a book on a difficult subject, in fact this book invented the subject, or perhaps more accurately synthesised and distilled and enormous amount of knowledge and experience and created a framework to make sense of it; how to think about software design. I’ve now read it once and know I will be reading it cover to cover again. For me it is the right place to start learning about DDD but as Evans admits himself it perhaps lacks some practical guidance on how to go about actually doing DDD for real, in respect to the implementation of software that is as this book is about a philosophy, not technical details. My advice is to try and read it as fluently as it is written, and it is very fluently written, and don’t worry too much that all of its detail is not going in. As I said, this is a difficult subject. Once you’ve read it, read one of the books that takes the material and treats it in a less formal way but a more practical hands on way, I’m doing that right now, then read the Evans again with the context that you’ll get from the less formal book will turbocharge your understanding, well that’s the basis I’m working on :) Becoming proficient at DDD takes time and work but I suspect the rewards are, as I suggested, game changing. Already I am looking at code and the way a business is structured to attempt to produce code with the blinkers off and a much clearer picture of the pros and cons of what I see. For me there are but a few seminal books on writing software and having read this one I’m putting it right up there with the very, very best of them. Absolutely loved every page.

This book is not something light to dip into and offers a very deep examination of modelling. I got a huge amount out of it; It went through a number of the practical problems that I've encountered before and helped me to properly understand the patterns that I used to solve them. Evans introduces concepts that are extremely useful when considering how to decompose a monolithic application into micro-services. I believe that this book will reward the effort that it takes to study it.

Anyone who has worked with me knows that, before, when i was doing coding work, I could only work in complete silence cos i had to concentrate so hard. This meant i couldn't get any work done in the office during normal hours cos there were always interuptions and disturbances. Every disturbance meant that i had to spend 15-20 mins just getting back to the mental state from which i could continue working again. Hence, i had to work weekends and do all-nighters. Hence - I spent soooo much time working and not having fun. This is all 'cos i was having to deal with really complex code. I was always spending time and energy trying to *reduce* the complexity. But, this book has really told me to STOP *trying to reduce the complexity*. It aint gonna happen - it IS complex. Instead - It tells me how to *handle* the complexity. By handling the complexity, it means that i can work better. Quickly getting back to 'where i was' mentally after an interuption. It allows me to work, during normal hours, productively. So, now I am FREEEEEEEEEEE - woo hoo! Paraphrased Quote from Page 265: from the book: Domain-driven Design, By Eric Evans "In every programming environment, a few basics are so pervasive that they are always in mind... For example,..[the concept of "numbers"] don't add to the intellectual load. Beyond that, every additional concept that has to be held in mind in order to understand [the software you are building] contributes to the mental overload... ..Low coupling (one tenet for handling complexity) is fundamental to [software] design. When you can, go all the way. Eliminate all other concepts from the picture. Then the class [a bit of code] will be completely self-contained and can be studied and understood alone. Every such self-contained class significantly eases the burden of understanding the ..[the software you are building]" Basically - if you are mildly geeky i recomend this book! Sermon over. Amen.

Simply phenomenal. Only for highly experienced and advanced software developers, with concern about high level design. People that think developing software is typing code will find it boring. Great for developing systems in an agile way. DDD requires huge team work and cooperation, courage and tremendous amount of practice. As with other outstanding books, within many decades it will still be up-to-date, relevant and ignored by many.

If you are doing architecture or want to do better when system coding then this is a must-read

Eric Evans, tal qual outros renamados autores da área já declararam sobre está obra, entrega muito conteúdo de grande relevância para quem lida com desenvolvimento de software. É um livro mandatório no assunto

If you are a practicing architect, this book is good fun. Every concept you read, you'll catch yourself cross checking if you'd done it in a similar way! You reminisce, and that's a good thing.

I know this is _the_ book about ddd. But I found it a very hard read. Endless chapters, that feel more like rambling than concrete examples and theory. Having recently seen a video with the author explains a lot, since that too became a longwinded rambling. So I guess in it time this book was ground breaking and the theory is still actual and solid. However the book is not. Trying to solve problems that long since have been solved by well designed frameworks and languages does not help conveying the message. By now there are better books handling the subject

Software development is more than just the technology used. Although this book was written almost twenty years ago it didn't run out of date. A good foundation for a DDD journey. This is a must-read for senior software developers and architects and product owners, business analysis, or even managers in tech companies. I can call it one of the most important books about software design I've ever read!

What else to say about the blue book? Only that you should read it