Interoperability
Specific promises, backed by specific tests.
MyServiceBus compatibility is deliberately scoped by transport. The verified RabbitMQ and Azure Service Bus preview baselines cover portable messaging across the C# client, Java client, and MassTransit.
Verified scenarios
- Envelope publication and directed queue sends
- Correlated request, response, and fault flows
- Retry exhaustion and preservation in
_error - Unknown-message preservation in
_skipped - C# ↔ Java delivery in both directions
What is not implied
This is not source compatibility, full MassTransit API coverage, or a promise for every MassTransit 8.x or broker release. Compatibility is tied to the documented versions and transport profiles.
Contract for every supported transport
Both MyServiceBus clients must follow the supported MassTransit peer’s addressing, entity naming, topology, native-property, and settlement conventions. A transport is not promoted from experimental to supported until C#, Java, and MassTransit can communicate in both directions through that profile’s documented conformance matrix.
Live Azure verifies cloud topology, default message and consumer endpoint naming, bidirectional publish, directed queue sends, correlated responses and faults, lock renewal, and terminal failure settlement between MassTransit and both MyServiceBus clients.
Before 1.0, only the newest published preview is actively supported. Fixes are delivered in a newer preview.