The basic examples I have seen about Event Sourcing do not deal with out of order events, clock offsets in different systems and late events from system partitions.I am wondering if more polished Event Sourcing implementations rely on a version stamp of modified objects?For example, assuming that the system is rendering the entity Client with version id ABCD1234. If the user modifies the entity, the system will create an event with the modified fields AND the version id reference to which version it applies. Later the event responder would detect out of order events and merge them.
Version hash to solve Event Sourcing problems
cqrs;event sourcing;distributed system