in this post i write about and show how to merge #aggregates in #eventSourced systems (particularly with the #dolittle #sdk)

https://www.eke.li/2023/05/merging-aggregates/

#ddd #dev #code #systemDesign

No surprise that implementing such a feature is really straight forward in an #eventsourced system. Everything feels natural.

Iterate through the event stream, count the number of finishes cards (tasks), memorize which achievements were already granted, check the specs and produce a new event if a new achievement (or level) was reached.

Should we want to introduce temporal achievements like „finished tasks per week“ - easy peasy, the time is in the events.

3/x

Turns out, I have not really declared my huge 💛 for #eventsourcing since I‘m on Mastodon. 😺

We‘re building a company-internal social card game @MaibornWolff with #golang - and it’s #eventsourced

If you want to learn about the #domainlogic of the game, I described it here:

https://medium.com/@TonyBologni/domain-driven-design-vs-functional-core-imperative-shell-4a38c6c86733

After many busy months I was finally able to work on the game again, mostly while spending ~10 hours in the 🚆

1/x

Wrote an article on how to improve your Spreadsheets with Event Sourced architecture.

With demo spreadsheet and background on #eventsourced architecture.

"Event Source your Spreadsheets for Flexibility and Maintainability"

https://berk.es/2022/08/16/event-source-your-spreadsheets-for-flexibility-and-maintainability/

Once I learned #eventsourced architecture, I realized that several systems which I wrote in the past, suffered because they weren't event sourced.

It's one of those "if only I knew back then" architectures.