I think you're mostly downvoted because: * It's only about CQRS, which in no way was mentioned in the article; * You're not properly qualifying why this featu

I think you're mostly downvoted because: * It's only about CQRS, which in no way was mentioned in the article; * You're not properly qualifying why this feature is so important for CQRS; * In the same breath, you're also claiming it's overused and complex, while in fact you're the one who's "promoting" it. I agree that in my reply, I was actually thinking about ES + CQRS rather than pure CQRS, but the gist of my comment still stands: I would expect a CQRS implementation to work with triggers (for incremental updates) or materialized views (one table insert-only, the "view" is kept in sync automatically by the database, which is what users query). Could you elaborate on why you think this new feature is better than those two approaches?