I’m looking to find the name of a software development (pattern/architecture/etc)

Essentially, I'm trying to consume some events about incoming calls – call created, call answered, that sort of thing.

Currently, we add a date to database object for each incoming event, but this could easily result in data corruption due to race conditions or out of order event processing if multiple events happen nearly simultaneously.

The solution I'm looking at is to store each event as it's own event in a database collection (mongo, we have it in the system already), and then generate a synthetic object at the end by loading all the events and applying them to the synthetic object.

What I want to know is what is this pattern called, so I can google it and learn more about the upsides and downsides of this approach. Also, any thoughts on the advantages and disadvantages, but mostly a googlable name so I can learn about it/point the boss at it.