File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Java in General and the fly likes Event Processing in Action: relationship with DDD Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "Event Processing in Action: relationship with DDD" Watch "Event Processing in Action: relationship with DDD" New topic

Event Processing in Action: relationship with DDD

Gian Franco
Ranch Hand

Joined: Dec 16, 2003
Posts: 977
Hi Opher, Peter,

In Chapter 1 of your book you have the following definition:

EVENT An event is an occurrence within a particular system or domain; it is
something that has happened, or is contemplated as having happened in that domain.
The word event is also used to mean a programming entity that represents such an
occurrence in a computing system.

One of the meanings of the word event seems strongly related to domain driven design
(DDD) is this what it is, does DDD make Event Processing easier?



"Eppur si muove!"
David Newton

Joined: Sep 29, 2008
Posts: 12617

It depends on the domain--just because the word appears in multiple places doesn't mean it's synonymous.

In some domains (systems, use cases) event processing makes sense, in some, it doesn't.
Opher Etzion

Joined: Aug 04, 2010
Posts: 14
Hi Gian. As you noted one of the meanings of the word "event" is the event that happened in the "real-world domain" and not in the computerized domain (which is a proxy of the former). An approach of DDD can be helpful for many type of event-driven application; One of the common types of application is the one whose goal is to find some events or event patterns that we wish to react to, DDD approach can focus us to the real-world situations to which we wish to react, and then we can map the relationships between them and events, and define the patterns that will be used at run-time to detect that these situations occur. This can evolve based on the business environment evolution, which means that connecting it to the domain knowledge might be very important for such application, and this follows the DDD paradigm.
I agree. Here's the link:
subject: Event Processing in Action: relationship with DDD
It's not a secret anymore!