In this new eventsourcing blog post we will considered several ways to implement state to be used in decision-making. We're equipped with a varied range of tools suitable for different sizes and maturity of problems, from deriving the state with kotlin stream extension functions to employing finite state machines. Enjoy the read! https://dev.to/jakub_zalas/deriving-state-from-events-1plj

I am always intrigued by event sourcing. Have you used it in production somewhere? My experience with it, where we have it in production, is that it tends to 'fragmentise' domain logic somehow. And onboarding new team members is harder because most people have no experience with event sourcing. Besides that... excellent set of articles.

Unfortunately, I can’t usually discuss client projects so I had to use a game example. I didn’t experience logic fragmentation as you say. I didn’t try to onboard anyone yet, but od approach it like tdd and pair extensively. Thanks for feedback!