Version hash to solve Event Sourcing problems

Posted by SystematicFrank on Programmers See other posts from Programmers or by SystematicFrank
Published on 2014-08-20T17:48:09Z Indexed on 2014/08/20 22:32 UTC
Read the original article Hit count: 309

Filed under:

cqrs

|

event-sourcing

|

distributed-system

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.

© Programmers or respective owner

Related posts about cqrs

CQRS at Jax Code Camp 2012

as seen on ASP.net Weblogs - Search for 'ASP.net Weblogs'
Continuing my CQRS world tour...I gave my CQRS presentation at the Jax Code Camp 2012 this past Saturday. It was a great crowd with lots of representation from the wicked smart engineers at Feature[23] and others from the Jacksonville developer community. If you'd like to take a… >>> More
CQRS without using others patterns

as seen on Programmers - Search for 'Programmers'
I would like to explain CQRS to my team of developers. I just can't figure out how to explain it in the simplest way so they can implement the pattern rapidly without any others frameworks. I've read a lot of resources including video and articles but I don't find how to implement CQRS without using… >>> More
Domain queries in CQRS

as seen on Stack Overflow - Search for 'Stack Overflow'
We are trying out CQRS. We have a validation situation where a CustomerService (domain service) needs to know whether or not a Customer exists. Customers are unique by their email address. Our Customer repository (a generic repository) only has Get(id) and Add(customer). How should the CustomerService… >>> More
CQRS - The query side

as seen on Stack Overflow - Search for 'Stack Overflow'
A lot of the blogsphere articles related to CQRS (command query repsonsibility) seperation seem to imply that all screens/viewmodels are flat. e.g. Name, Age, Location Of Birth etc.. and thus the suggestion that implementation wise we stick them into fast read source etc.. single table per view mySQL… >>> More
CQRS event versioning

as seen on Stack Overflow - Search for 'Stack Overflow'
Versioning If your events changes you would create a new version of that event, and keep the old ones. To keep your domain code form being bloated with handling of all versions of events you would basically introduce a component that converts your events from previous to newer versions, and then… >>> More

Related posts about event-sourcing

Event sourcing and persistence

as seen on Programmers - Search for 'Programmers'
I'm reading up on event sourcing and have a question regarding persistence. I can still have a DB with all entities, right? Or should the events be replayed every time the application is started to get the latest version of each entity in the memory? Seems like a waste on larger systems (as in large… >>> More
Backward compatibility with event-sourcing

as seen on Programmers - Search for 'Programmers'
How do you stay backward compatible with event-sourcing? Let say you release a version that has one kind of event, let call it X. You know how to handle that event in all the systems that extracts the events from the event source. In a later release you make a change to event X or delete it, how do… >>> More
Inheritance, commands and event sourcing

as seen on Programmers - Search for 'Programmers'
In order not to redo things several times I wanted to factorize common stuff. For Instance, let's say we have a cow and a horse. The cow produces milk, the horse runs fast, but both eat grass. public class Herbivorous { public void EatGrass(int quantity) { var evt= Build.GrassEaten … >>> More
Is event sourcing ready for prime time?

as seen on Programmers - Search for 'Programmers'
Event Sourcing was popularized by LMAX as a means to provide speed, performance scalability, transparent persistence and transparent live mirroring. Before being rebranded as Event Sourcing, this type of architectural pattern was known as System Prevalence but yet I was never familiar with this pattern… >>> More
How do you end up with event-sourcing if you use a xDD approach?

as seen on Programmers - Search for 'Programmers'
When working in a TDD or BDD manner your unit tests are supposed to drive your design. But how do you end up with event-sourcing using a xDD techniques? As I see it event sourcing is something you need to adopt early on to take full advantage of it. Lets say that you start without event-sourcing… >>> More