Then I see JavaScript and Node.js.
So this isn't a book on either of DDD, CQRS or EventSourcing. It's about JS.
Then I see JavaScript and Node.js.
So this isn't a book on either of DDD, CQRS or EventSourcing. It's about JS.
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
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.
>Then I see JavaScript and Node.js
What's wrong with this? The underlying architectural patterns and abstractions you should be able to pick out and apply to your technology of choice.
I don't know where that came from but please don't make things up that look like quotes when they're not, and especially please don't use that as a snark trope.
(If someone said that and you're actually quoting them and they edited it out, that's of course different.)