Aggregates: Persist and return stored object

[ahoiroman]

Hello everybody,

I'm quite new to the concept of event sourcing and at the moment I'm playing around in a pretty large app to move to event sourcing on smaller features.

Now I was on my way to implement the aggregates on a small controller like this:

public function store(Request $request): ItemData
    {
        $newUuid = Str::uuid()->toString();

        ItemAggregateRoot::retrieve($newUuid)
                                       ->createItem($request->input('item.name'))
                                       ->persist();

        $item = Item::uuid($newUuid);         // This feels a bit fishy

        return ItemData::from($item);
    }

As you can see, I need to return a DTO called ItemData, which contains the item I just saved. But the way I am doing this, it kinda looks "fishy" as I am searching for the Item I just saved using the UUID.

[etahamer]

@ahoiroman As far as I understood, your Item is projection, then I would suggest generating ItemData from ItemAggregateRoot rather than from projection, which may or may not exist during runtime (Happens when projections are being queued).

[ahoiroman]

I ended up returning the UUID and broadcast the projection‘s data after it has been created.

[chrisloftus]

@ahoiroman I'm broadcasting at the moment but it is slow.

[ahoiroman]

It may be - but you could make this process visible to your users by reflecting the loading-state in the frontend in a nice way.

[chrisloftus]

Maybe but it's still not ideal.

I'm creating a relationship model, not the parent model that has UUID already. So the UUID is on the parent model. So I need to think of a way to return the child model that is created. Maybe use UUIDs on the child model too but ugh...

[ahoiroman]

So you asked me for my solution - I gave you the answer that worked for me.

you are not forced to queue the events - you can always return the full model as shown in my initial post.