4 ms·
Probably because event-sourcing is beginning to trend. The article is not that interesting in itself, but the conclusion is a good starting point for a convers
by djfm 10y ago
Probably because event-sourcing is beginning to trend.
The article is not that interesting in itself, but the conclusion is a good starting point for a conversation that may be.
> Systems are largely not functional. But they can be.
So, how?
- yrashk 10y agoMy research into this topic has led me to lazy event sourcing so far https://blog.eventsourcing.com/lazy-event-sourcing-ed7e59007e17#.v3yqh7ukh https://blog.eventsourcing.com/lazy-event-sourcing-ed7e59007... My current view is that by eliminating or reducing the need to serialize domain objects, we're creating a system which is easier to argue about and provides an easy way to adjust domain models as the understanding or circumstances evolve.
- djfm 10y agoYeah, now this is a nice continuation to the conversation :) I too have been mildly obsessed with the kind of thinking you're developing in your post - very nice article! I've been very attracted to event-sourcing since I realized that now that React and redux have mostly solved the UI problem what remains to be solved is the problem of how to store our beautiful event-driven data. EDIT: re-read your comment, felt the need to say that your "current view" is exactly mine too
- yrashk 10y agoI am happy to continue this conversation off-HN, perhaps Gitter? http://gitter.im/eventsourcing/eventsourcing http://gitter.im/eventsourcing/eventsourcing