alex-lawrence

13 ms·

1.
by alex-lawrence 5y ago
This library provides selected useful features of modern UI libraries, while staying at a minimal size. Without the need for compilation and extensive tooling, it is easy and straight forward to use. Originally, this project started out as
2.
Show HN: adequate – an adequate UI library with minimal size(adequatejs.org)
2 points by alex-lawrence 5y ago|1 comments
3.
by alex-lawrence 6y ago
The Aggregate Root must track all Domain Events that occur upon executing an action and make them accessible somehow. Only after the successful persistence of the associated state change (and/or the events), they can be published via a
4.
by alex-lawrence 6y ago
Since I am asked from time to time about the technology choices for my book, I decided to write a blog post to explain my reasoning: https://www.alex-lawrence.com/posts/why-my-book-uses-nodejs-... Some of my arguments
5.
by alex-lawrence 6y ago
Without Event Sourcing, I would say there is almost no boilerplate code for aggregates themselves or their root Entities. After all, an Entity can be implemented as plain old class or object. For event-sourced aggregates, it depends on the
6.
by alex-lawrence 6y ago
I will definitely look into this. What I can already say is that it has the best name for a ES/CQRS library!
7.
by alex-lawrence 6y ago
Thank you!
8.
by alex-lawrence 6y ago
I think this is a great recommendation for any new project that is considering to use Microservices. I like the approach of an in-memory event-driven system. This helps to enforce a message-only relationship between different conceptual par
9.
by alex-lawrence 6y ago
Please note that I have limited experience with domains where Event Sourcing is without a doubt the weapon of choice. Hope my input still helps. Maybe there are other people that can give more qualified input on that. In the end, I am not t
10.
by alex-lawrence 6y ago
Could you explain which aspects specifically require a lot of boilerplate code? Judging from my experience, I think the tactical DDD patterns are straight forward to implement. I didn't mention this in my post, but the Node.js framewor
11.
by alex-lawrence 6y ago
Thanks! It is important to note that my book is not an alternative to "Domain-Driven Design" by Eric Evans. Rather, it is an introduction to DDD, an explanation of CQRS and Event Sourcing and an implementation guide. Also, it is n
12.
by alex-lawrence 6y ago
Thanks for the feedback. Happy to hear that you appreciate the UI chapter. For me, it was important to explain how to approach the User Interface. I often had the feeling that this part was a bit neglected when reading about CQRS & Even
13.
by alex-lawrence 6y ago
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 th
14.
by alex-lawrence 6y ago
I only heard of Nest.js a few weeks ago and haven't had the chance to look it. Therefore, take my reply with a grain of salt. Libraries and frameworks can help you with different things, but they can also get in your way. If the CQRS m
15.
by alex-lawrence 6y ago
In one project, where we could have done otherwise, we went consciously full Event Sourcing. In another project, the Domain Model was inherently event-based. In my book, the Sample Application first persists domain objects and is later refa
16.
by alex-lawrence 6y ago
I have to say that my recommendations on JavaScript education resources might be pretty outdated. The book that helped me a lot with the JavaScript language (in 2010) was https://www.goodreads.com/book/show/2998152
17.
by alex-lawrence 6y ago
That is a good question and, ideally, I should be able to answer it. Unfortunately, I don't know. The book started as a passion project and I never analysed the market in any useful way. However, I think that there is a certain potenti
18.
by alex-lawrence 6y ago
Sorry, there is no printed version at this point. I wanted to focus on the e-book variant first. While this is not necessarily an argument against a printed version, note that this book works best when reading on a computer. It comes with t
19.
by alex-lawrence 6y ago
The idea of this book is to provide a practical guide on how to implement DDD, CQRS and Event Sourcing. I chose to use JavaScript and Node.js as alternative to Java or C#, which are often used in comparable literature. After reading it, one
20.
Show HN: I wrote a book on implementing DDD, CQRS and Event Sourcing(leanpub.com)
169 points by alex-lawrence 6y ago|56 comments
21.
The financial cost of writing a book(alex-lawrence.com)
2 points by alex-lawrence 6y ago|0 comments