From the title, I was prepared to disagree with you. Because there is nothing wrong with using Event Sourcing inside a microservice. But I do agree with your conclusion. A service's persistence details should remain private. Anything that is shared publicly should be separate, because it is used for a different purpose and may change for different reasons. This is a core Separation of Concerns.
Also, thanks for the links. I look forward to reviewing some of these I haven't seen.
From the title, I was prepared to disagree with you. Because there is nothing wrong with using Event Sourcing inside a microservice. But I do agree with your conclusion. A service's persistence details should remain private. Anything that is shared publicly should be separate, because it is used for a different purpose and may change for different reasons. This is a core Separation of Concerns.
Also, thanks for the links. I look forward to reviewing some of these I haven't seen.
Thanks for your feedback. I adjusted the title to Why Event Sourcing is a microservice communication anti-pattern.