With the current implementation, value entities only store the last update. With no snapshot history, consumers of value entity changes may not see every entity change event. This makes it more complex and difficult for developers to understand how changes are passed to change event consumers.
Changing from an update in place to a snapshot journal approach would reduce complexity from a developer perspective.
This change would also likely eliminate production support issues. Imagine a customer scenario where things work most of the time, but in some situations, numerous expected consumer messages are not sent. This has the potential for unexpected catastrophic application failures from the customer’s perspective.