Implementing Domain-Driven Design by Vernon is fantastic. Extremely practical application of the Evans book, which gets pretty abstract in places. It's great for people who actually want to see where the rubber meets the road.

Domain Driven Design by Eric Evans

Implementing Domain Driven Design by Vaughn Vernon

Clean Code by Robert Martin

I think you will find some code in all of the books but the ideas are applicable almost everywhere.

Read in order:

1. Anatomy of Domain-Driven Design, S. Millett

2. Domain Driven Design quickly, InnoQ

3. Implementing Domain Driven Design, V. Vernon

I recommend reading about Domain Driven Design. For example reading the book: Implementing Domain-Driven Design by Vaughn Vernon

The concept of Aggregates in Domain-Driven Design is based around the need for business invariants that must be maintained with transactional consistency in a system that is generally eventually consistent.

Overall, you have to learn to love eventual consistency, but small portions of the domain should absolutely be clustered together around transactional consistency needs that are absolutely necessary.

Check out "Implementing Domain Driven Design" by Vaughn Vernon; chapter 10 in particular talks about this.

In fact, the book was called "Implementing DDD, CQRS and Event Sourcing in Node.js" up until the release of its complete version. I thought about this for a longer time and decided to remove the "in Node.js" part from the title. Instead, I made it clear in the book description. In my opinion, the book can be valuable for anyone who is interested in the concepts, regardless of technology choices.

I think that it is fair to say that my book is partially also about Node.js, but not primarily. I wouldn't say though it is about JS. In fact, many of the code examples would look similar in other languages. Furthermore, the use of Node.js helps to provide concise code examples and executable code without much ceremony.

When reading "Implementing Domain-Driven Design" by Vaughn Vernon, all the code examples are in Java. The book "Enterprise Integration Patterns" has a lot of code examples and all of them are also in Java. The most recent edition of "Refactoring" by Martin Fowler uses JavaScript. Still, I wouldn't say that these books are about a particular programming language.

Technical concepts for writing code:

--------------------------------------

Clean Code (Robert Cecil Martin)

The Art of Unit Testing (Roy Osherove)

Head First Design Patterns (Elisabeth Freeman, Kathy Sierra)

Martin Fowler's blog: https://martinfowler.com/

.

How to gather requirements and write business-readable code:

--------------------------------------

Domain-driven design (Eric J. Evans)

Implementing Domain-Driven Design (Vaughn Vernon)

Patterns, Principles, and Practices of Domain-Driven Design (Scott Millett)

.

Remaining agile and managing your work according to your clients' needs:

--------------------------------------

The art of doing twice the work in half the time (Jeff Sutherland)

The Mythical Man Month (Fred Brooks)