One of the biggest pains in traditional software design is accidental complexity. Event Sourcing can help with that, as it focuses on the business process and allows for backward compatibility. With Event Sourcing, events are recorded as the results of business operations, creating a separation of concerns between business logic and read models. However, there are tradeoffs to consider. Event Sourcing wont remove the need for proper design, but it can streamline the effort. This article discusses how to keep events granular and not coupled to read model needs, using the example of managing work schedules and employee allocations.
