All geek questions in one place

Why do all system events use an anti-pattern?

I am currently developing a new enterprise system. The purpose of the system is to track, display and notify employees about customer interactions (i.e. events) with the company. Using an event source template to store a book of all client interactions / events that are collected seems very appropriate since all of our additional domain objects are obtained from the event stream. However, I stumbled upon an article that stated that the entire system, based on the sources of events, is an anti-pattern. Why's that?

https://www.infoq.com/news/2016/04/event-sourcing-anti-pattern

+5
source share
3 answers

" DDD, CQRS, Event Sourcing" DDD Europe 2016.

, . , , .

, . , DDD, . , ().

- , DDD, , "" , Event-Sourcing. .

, , Event-Sourcing. , , / . -. , CRUD? , , - CRM, Event-Sourcing , .

, , , , , .

+8

. .

, CRUD " ", .

, , .

, , , .

, "- " , CQRS/ .

+5

I recently published a post in a blog post about this issue. This explains why the source of events is an ongoing strategy and should not be used globally.

0
source

Source: https://habr.com/ru/post/1671288/

More articles:


All Articles