Open2024/04/21にコメント追加3

Event Driven Architecture in ODC

outsystems

odc

Junji Watanabe

Some articles I wrote on Qiita:

https://qiita.com/jyunji_watanabe/items/d867db0723e5584039ff
https://qiita.com/jyunji_watanabe/items/3a7e264b3b49fdcb3066

Junji Watanabe

I found a Chapter titled "Event-Driven Architecture" in the book Learning Domain-Driven Design (English Edition).

Some notes on the Chapter here.
The terms "Producer" and "Consumer" are used in this book, and they are used in the same way as those used in OutSystems.

building blocks of EDA
common causes for failed EDA projects
DDD tool to design asynchronous system

Junji Watanabe

Since an event describes something that has already happened, an event’s name should be formulated in the past tense: for example, DeliveryScheduled, ShipmentCompleted, or DeliveryConfirmed.
Khononov, Vlad. Learning Domain-Driven Design (English Edition) (p.369). O'Reilly Media. Kindle 版.

A naming rule convention for Events in ODC: the past tense