Event definition duplication

e.g. OrderStatusChangedToPaidIntegrationEvent 1, 2

How come these aren’t in some shared place e.g. ...Services.Orders.API.Events?

[CESARDELATORRE]

We believe that is not a good practice. Microservices should be autonomous and not depend on shared libraries except for serious building blocks. This shared library wouldn’t be a building block but a domain-type library. That is almost like if you share a domain entity library across microservices. If you change the event in one microservice will break the consumers in the same way than you break consumers if you change a REST API. But in that case, you are not sharing types with Http consumers, neither. So, changing events should be done carefully, with versions, in the same way than you change REST or HTTP services. You might also have similar types when using DTOs or ViewModels in services and HTTP consumer apps. I think this is a very similar case, but using integration-events.

So, initially, we don’t want to share a class library for the events across a microservice application. It is arguable, but the reasons are what I just said. We’re open to discuss this topic further, though. We could find additional improvements, in any case. 😃

[CESARDELATORRE]

We have a Slack channel for the project, but due to many other projects we’re working on, we cannot focus on Slack, so we end up using email… You can send me emails to cesardl at microsoft.com