I'm somewhat mixed on this book. The authors are very clear about one particular design pattern, using Domain Driven Design to create aggregates which push events to a message bus, and layers of abstraction between the changeable facts of any specific database or infrastructure on one end, and the confusion of business logic which has to represent the messiness of the real world in a way that computers can understand on the other.

I'm somewhat pleased that I stumbled into their preferred pattern on my own before reading this book. But the meat of what I was interested in, test-driven development in the real world with legacy code, is left underexplained. I should spend more time with the accompanying Github, and in many ways this book is closer to my day to day than Designing Data-Intensive Applications, but as other reviews have mentioned, it's one architecture pattern.