webDEVILopers comments

Results 260 comments of


                                            webDEVILopers

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Would love to hear how the @AxonFramework deals with these kind of "value object from deserialized event payload without revalidating" issue. @abuijze Could you give us some feedback on this?...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Related to an older issue: * https://github.com/webdevilopers/php-ddd/issues/35 Thanks to @ocramius for his feedback: > fromArray_v2 all the way: I avoid public function __construct in my systems, as data structures have...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

My current suggestions would be: ```php private function __construct() {} public static function fromString(string $name): FirstName { $name = NameNormalizer::withString($aName); $self = new self(); $self->validate(); $self->name = $name; return $self;...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Other options related to the library or framework you use could be versioning of events as suggested by @Mattin. Options would be: * Upcasting the event * Using a different...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

At the bottom line a totally I agree with @AntonStoeckl here: > Upcasting imho is: Adding new information where old Events will be valid with a default. Or only changing...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

> b) It's a new rule that should be enforced during the creation of _new_ events but can be ignored when _consuming_ them > => create a new VO that...

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

> But now your domain logic needs to know where your VO comes from to know whether it follows the new rules or not. That is the point! The domain...

webDEVILopers

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Applying domain events to aggregate roots when deserializing payload of old events break current value object constraint changes

Creating event-sourced aggregate roots through CQRS read models

How to handle large aggregates - defining multiple aggregate roots

How to handle large aggregates - defining multiple aggregate roots