Thanks for the feedback!

Depending on what your focus is, I’d say yes. If you’re working with microservices or a similar distributed architecture, then Domain Driven Design lays out a number of concepts and patterns that, IMHO, will make it much easier to reason about your system and to make design decisions.

That said, the book can be dry at times. What you could do is to first build up some more familiarity with some of its patterns via other sources. For example, Fowler, Chris Richardson, as well as articles like this one — and I’ll plug my article on Bounded Contexts :) . After that, maybe go back and read through Domain Driven Design. With more of a foundation up front, it might be an easier read.

Software architect, engineering leader, musician, husband, dad

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store