DomainEvents and CommandEvents not persistent

[Ron Smith]

I'm porting an older Sculptor app to the latest and greatest Sculptor version, and am getting errors on the 'not persistent' modifier on any CommandEvent or DomainEvent objects.  The event-driven tutorial (http://sculptorgenerator.org/documentation/event-driven-tutorial#domain-events) indicates these are never persistent now.  So I'm removing the qualifier which is no longer needed nor legal.

I recall there was some discussion as to whether command events or domain events would be persisted in an EDA/CQRS approach, but don't we need to support the persistence of some types of events?

Ron

[Torsten Juergeleit]

I recall there was some discussion as to whether command events or domain events would be persisted in an EDA/CQRS approach, but don't we need to support the persistence of some types of events?

The chapter Persistence mentions that using the keyword "persistent" in an event type will add the persistence support.

IMHO are Sculptors non-persistent events sufficient for implementing "simple" EDA (pub/sub). But for implementing full-blown event sourcing or CQRS something like a generic event store seems to be more appropriate. For the latter one I would consider using a fully-fledged framework like Axon2 with its repository and event store implementations.

/Torsten