I leave an example that I hope can help you in understanding the problem. That MassTransit can manage the creation of queues and topics based on the serialization of the object, instead of managing it based on the object type (perhaps through some type of wrapping object?).While lightweight, high-speed ticketing alternatives are already in use in the private transport sector. The environmental conditions present in Rail and Mass Transit equipment and facilities require unique product properties. Remove the namespace from the endpoint of the destination address, naming it only with the name of the class. Ticketing is a pain point across mass transit.The options that have occurred to me are: The same thing happens with two classes with the same properties in the same namespace but with a different class name. RabbitMQ, NServiceBus, Azure Service Bus, Kafka, and Hangfire are the most popular alternatives and competitors to MassTransit. The automatic management of MassTransit causes queues and topics to be managed by the object type, which prevents the microservices that consume a message from receiving the messages sent by the microservice publisher. By their own definition, and to avoid generating dependencies between them, messages sent between different microservices are defined in each of them, that is, they are part of different namespaces. Its very clear that a significant portion of the increase in transit use is directly caused by people who are looking for alternatives to paying 3.50 a gallon.
I am using MassTransit with Azure Service Bus for asynchronous communication between microservices. First of all, excuse my English, it's very bad.