Domain-Driven Design Distilled

Domain-Driven Design Distilled is about, well, Domain-Driven Design! My team has started using it (and didn't let me know...), so I needed to pick up a general idea of what DDD is, how it fits into a project, how to use it to model a project, etc., and I needed it fast.This book absolutely delivers on that. I left with a better understanding of DDD and all the weird things my team has started doing. I also got a better idea on how to approach planning and architecting from the business perspective, so it becomes easier to associate the business rules and ideas with the code. (It can be a major challenge.)You'll get a few high-level DDD activities, but if you were hoping for something that goes deep, this isn't the book for you. It's right in the title after all: *Distilled*. The same author has another book that goes way deeper. That's the one you should get. That, or the one by O'Reilly.

If you haven't read anything on DDD and don't understand the pieces and parts, don't read this first. This isn't a good book for introducing the concepts - see Domain-Driven Design by Eric Evans for the foundational information.While I like it from its simplicity, understand that this shouldn't be referred to for the first exposure to DDD topics. I feel like it gets high-level enough to paint the picture of concepts and tools, but it doesn't provide enough depth to be foundational.Once you get the foundation in, then DDD Distilled makes more sense on its purpose. This is a high-level overview - talking of strategic vs tactical design and including DDD terminology throughout those comparisons. From ubiquitous language and bounded contexts to aggregates and domain events, there are discussions of these DDD concepts with an example that a developer in a Scrum environment could relate to. In the end, he gives a list of tools that can be useful in getting started with DDD.Keep in mind that this isn't a super in-depth book. Implementing Domain-Driven Design is referred to throughout the book as a reminder of more specific implementations.If you want a high-level supplement of understanding concepts and recommendations of tools, this could be good for that.

If you're looking to gain a better understanding of DDD (Domain-Driven Design), then this book might just be the perfect fit for you. It's a concise read that can easily be completed within a week, offering valuable insights into the world of DDD. Whether you're new to the concept or seeking a refresher, this book aims to provide clear and accessible explanations.

The book explains the DDD concepts in a very good way, with good examples. It doesn’t dig too deep on implementing the concepts but for experienced engineers it’s clear how to do it.I ignored most of the last chapter though. The author doesn’t seem to understand a lot about management or processes by what i’ve read there.

- This book gives a good starting points for everyone. I believe anyone who (will) work for IT industry should this book.

It is one of the most best books that I found about software architecture.Unlike any other books, the proposed methodology covers from high level system definition with experts in your company to the implementation.It is very well written and concepts are very clear. It is easy to see that this book has written after years of experience.This book is short, and quick to read and understand, and the counterpart of it is that it makes references to other books about implementation details (specially Implementing DDD from the same author). Unfortunately, unlike this book, IDDD does not follows 100% the same methodology and exposed code is old, so it will not resolve your doubts about implementation.

Vaughn Vernon previously wrote a great book on DDD (IDDD), so I was curious what this one has to offer. I have to say that I remain slightly confused, this basically feels like a shorter and simpler version of IDDD, without code samples.First things first you will learn the most important DDD concepts such as entities, aggregates, events, and how to design model systems using event storming. The chapters on the individual concepts felt somewhat vague however it was a nice refresher. If you're new to DDD I'm not sure if has comprehensive enough explanations.Understanding rather complex things (modelling Aggregate Roots for example) without seeing the real code samples feels ... hard. Perhaps even too hard. If you're a developer, you might want to consider this book if you've heard of DDD but you know you haven't got the time to go through a much more detailed IDDD book. If you're working in a less technical position, this book is actually quite nice as it describes the high-level planning process called Event Storming and it re-visits SCRUM and its original ideas (it was supposed to be a tool for communicating/learning but it ended up being misused by many managers as a tool for controlling timelines).It's been a while since I read IDDD and to be fair I finished this book during an flight - that's quite a good time investment. On the other hand had this been my only DDD book I'd have probably ended up being pretty confused.==========================| Edit: April/2017 |==========================Vaughn reached out to me in the comments section and he was kind enough to clarify his intentions about this book that I misunderstood. I admit that I didn't fully get them at first, and I feel that my review mis-judged the book a bit. I'd like to point out that I thought of this a book as a sequel to the older (red) IDDD book, but (as its name suggests) it was meant as a more quick and condensed introductory book instead.

Experienced practitioner explains how he does DDD with lots of practical specifics. Just enough theory, and recommendations on where to find more if you need it.

L'essentiel y est exprimé clairement

The book gives a very good and short introduction on a high level into DDD. At work we made at least our tech leads read it. But the book is for sure no replacement for the blue and red book. So if you read this and hope to get away with it, if you really want to become familiar with DDD, then you should still read the blue and red book.

As a veteran developer I actually hadn't used DDD, much to the surprise of my younger colleagues. Embarking upon a rare greenfield project we identified that DDD was the approach we needed and I therfore needed to very quickly grasp the basics. With this book I was able to do this in a weekend and also become a lot more enthusiastic about DDD too!

It is a book really easy to read, it stays on the surface of all the topics related to DDD that you should at least know and understand. It gives also references to drill down into each topic if you need to. This book is a very good introduction and first step to understand DDD and to know the vocabulary and main concepts.

Um excelente livro como porta de entrada para aprender um pouco sobre DDD.Na sequência pode ler o livro mais detalhado sobre o assunto do mesmo autor, o IDDD.