Event Sourcing has always been an interesting subject to me. I used to work at a manufacturing company, specifically on a product that handled inventory management, so event sourcing felt like a natural fit for that domain. However, the concept was never easy to grasp as a junior developer. To make things worse, we were constantly under pressure from deadlines and new feature requests, which meant we never really had the time to properly learn and understand how to apply it. Fast-forward to today, now working in a healthcare company, I decided it would be worth revisiting Event Sourcing—if only to have it in my toolbox in case the right use case comes along. But while learning, I realized something: even though I could understand the concepts, I still had no idea how to actually structure an application around them. Even though I like to think I have a decent understanding of clean architecture and separation of concerns (or at least I want to believe that I do 😄), I was having a really hard time.…