title: Is event sourcing an enhanced pattern of choreography-based SAGA pattern?
body: <p>These days I am researching the Microservice inter-service communication patterns. So during my research, I found that there are two patterns called SAGA and event sourcing. But I couldn't find a resource on the internet to learn the difference between the two patterns. I mean I know event sourcing will capture the history of the event with the aid of an event store. So as per my understandings, I feel that event sourcing is like an extended version of choreography-based SAGA pattern. So I need to clarify is my argument acceptable or not. I will attach sample diagrams of the two patterns which I found on the internet below. Please use those diagrams during any of your explanations.</p>
  <p><a href="https://i.stack.imgur.com/0hRZH.png" rel="noreferrer"><img src="https://i.stack.imgur.com/0hRZH.png" alt="Choreography based SAGA Implementation" /></a></p>
  <p><a href="https://i.stack.imgur.com/WO2jD.png" rel="noreferrer"><img src="https://i.stack.imgur.com/WO2jD.png" alt="Event Sourcing" /></a></p>
  <p><a href="https://www.confluent.io/resources/kafka-summit-2020/redis-and-kafka-simplifying-advanced-design-patterns-within-microservices-architectures/" rel="noreferrer">References</a></p>