I'm new to eventsourced apps and since the beginning I'm facing an issue that I'm unsure how to resolve.
I work in ecommerce and I always try to convey meaningful events to my aggregates like PriceIncreasedEvent
, ProductDeactivatedEvent
, OutOfStockEvent
etc
But many times I just want to do a simple "CRUD" style with my aggregate. For instance, the user can change the product image, but I don't want to mess with my aggregate with ImageUploadedEvent
event, since it isn't part of the domain its supposed to handle.
All I want to do is simply set the new image path in the database. But since "projections" are supposed to be disposable, I can't do that, because I would loose information.
This often happens with other types of editorial data, like the title/name of something. I don't want to create a event TitleChanged
, I know that's a code smell, it doesn't matter for the domain that the TitleChanged
. I just want to change it.
Maybe eventsourcing was a bad idea? How do you guys handle these kind of scenarios?
TitleChanged
not an event in your domain? – RubberDuck May 29 '18 at 9:27