Re:Event Sourcing (2017)
by fennecfoxen on Thursday January 02, 2020 @08:29AM
(#21935159)
That's command-query responsibility segregation. The command stream gives you the nice log of everything that happened, while the read database is easy to query (and to reprogram if necessary).
[ Parent
| on HN ]
Isn't that confusing two different things, CQRS and ES? I use CQRS all the time, but have never built a system using Event Sourcing.
Regarding logs, "traditionally", I'd use an audit/change history table for objects that needed one.