Two bigs ones for me: - Don't use the read side from the write side. - Each aggr... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dmitryminkovsky on May 22, 2019 \| parent \| context \| favorite \| on: CQRS and Event Sourcing Intro for Developers Two bigs ones for me: - Don't use the read side from the write side. - Each aggregate should own its data (or more abstractly, the basics of DDD, bounded contexts[0]). [0]: https://cqrs.nu/Faq

eithed on May 22, 2019 [–]

Every state change needs to be reflected as event. Does your function need to save something to DB? Then your functionality should create event which will perform the DB save.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact