Event sourcing was always interesting to me, having read Martin Fowler's article about it years ago, I always thought it was perfect for some domains that I worked with (Inventory Management, Healthcare). But I never got the chance to fully delve into it. For those who don't know what Event Sourcing is, in a few words, it is a pattern that asks, what if, instead of storing the current state of an entity, you store all the events that have occurred over time, and use those events to reconstruct the state at any given point in time. This allows a system to be replayable, auditable, and (hopefully) scalable. These characteristics make Event Sourcing a great candidate for domains like financial systems, logistics, and healthcare. Fast-forward to today, I thought it would be interesting to really put my effort on understanding and applying it, but I got stuck on a practical problem: Even if I understood the concepts, I wan't sure how to actually structure the application around it.…