Hacker News Reader

Funny how the CQRS circle closes: it is an architectural design that overhauls some concepts of database design (the redo log, views) into the application layer (for some, to the extreme of reducing the database to a simple log.) And now this same separation is appearing in a DBMS design :)

View on HN

As per my understanding, CQRS fits here if you consider the database log as the "event source". But wouldn't it be terrible performance wise to create the "view" from the event source rather than using the storage layer.

I think there’s a parallel with how apps keep a trailing materialied view of the data instead of re-creating from the log, unless necessary.

Reply on news.ycombinator.com