Should we introduce specific annotations for Event Sourcing? about jmolecules HOT 3 OPEN

It's more meaningful to have events which are used in a module locally and those which are published to the outside world. You can model the visibility by putting the event definition into the API oder implementation layer.

So in my opinion it's not necessary to have special semantics for domain events and event sourcing events.

from jmolecules.

@OLibutzki this is very close to the discussion with @smcvb in Axon Discuss regarding the Local Event Store Support(https://discuss.axoniq.io/t/local-event-store-support/2980/19)... Marking event visibility seems to be a good thing... The only problem is, that you already introduced the DomainEvent concept here... And a pivotal event is probably not a domain event...

Do you have an idea how to resolve this?

from jmolecules.

@zambrovski the linked issue is in a protected forum section, so the others cannot access it I fear.

Anyway, I don't think you necessarily need t mark them explicitly...

You can derive their scope from the actual usage.

If you want to introduce certain architectural constraints like It's not allowed to use a EventSourcingEvent/LocalEvent (you name it) outside of a module you need to have some assistence.

You can have a explicit annotation or interface, but you can also derive the information from the event's package, if you split up the api and the impl part.

There are a lot of options.

from jmolecules.