Thread by @oskar_at_net

If you’d like to know why you may not need snapshots and learn modelling patterns to do #EventSourcing efficiently, read my latest article on @eventstore blog 👇
It may sound blatant, but I think that there are not many resources like that on this topic 1/
eventstore.com/blog/keep-your…

It’s a looking article, much longer than the length of the streams you should keep in the event store 🙂 I tried to keep it shorter or split it, but my main goal was to provide a thorough, nuanced and complete explanation. So grab a glass of preferred drink and have a read 2/

This is the third part and (hopefully) the last one of the triad about temporal modelling patterns. I started with a general introduction, explaining closing the books as to why you should reconsider your decision about snapshots. 3/
eventstore.com/blog/snapshots…

Then I explained snapshotting strategies. All patterns may be useful in a specific context. I don’t recommend snapshots as a first design decision, but if you have to do it, then do it right. I explained what options you have 4/

eventstore.com/blog/snapshott…

And now I’m coming with a grand finale, to give you tools to keep your stress short. It’s essential to use event stores efficiently. It might not be evident if you’re coming from the streaming world. They can keep streams long, as you’re not reading from them, but... 5/

...just receiving notifications. In Event Sourcing, you treat your events as the source of truth, and you should read stream events to make decisions on the latest state. Read more on that in: event-driven.io/en/event_strea….
It’s important to not copy/paste patterns /6

If you model your streams correctly and keep them short, you’ll have a much easier life. It’ll spare you a lot of troubles around versioning, performance, operation etc. I’m not saying that’s easy, but that’s the reason why I wrote this lengthy article and Twitter thread 😅 7/

This article is extremely important for me. I put huge effort and been probably too long in this rabbit hole for too long not seeing the light. So I’m happy that’s out, and we’ll be even more pleased if you read it and send me a feedback! 😀 8/

Last but not least, I thank the draft readers for their precious feedback. Not all suggestions I could apply, but it helped me a lot.
Thanks go especially to @rbartelink @mat_mcloughlin @alchemist_ubi @wastaz @aludwikowski, but also to the others! You rock! 🤘😀🤘 9/9

Of course, I had to forget about someone, but at least you have a personal thank you tweet @RadekMaziarka 😅 Thanks for the precious feedback! 10/10