This is probably one of the most useful “cloud” patterns out there and it is fairly easy to implement. There are great articles and implementations, like Polly, already on the internet about this pattern so why another one? Κρείττον οψιμαθή είναι ή αμαθή. Socrates 469-399 BC., Philosopher Which translates to: Better too have learned lately than never, as he tried to explain why he learned to play guitar in his old age. ...
Yes, i know not this again. Is this not the one millionth time that someone blogs about that? Yes, yes and yes but… It is always good to repeat things and we all know that “Repetition is the mother of learning, the father of action, which makes it the architect of accomplishment.” ― Zig Ziglar There are still implementations out there that might benefit from this… So let’s start with some definitions. ...
Event sourcing is capturing all changes of an application state as a sequence of events. Since we only store events we only have to add events to a store, in contrast to updates for keeping the application state. A much simpler model that scales very well. When needing the application state we just aggregate the events into More on this can be read all over the internet but two excellent links are available below: ...