Interoperability
Verified interoperability boundaries.
MyServiceBus compatibility is deliberately scoped by peer and transport. The broad portable profile targets MassTransit, while NServiceBus support is a separate RabbitMQ directed-send profile.
Verification is transport-specific
| Transport | Verified | Not yet verified |
|---|---|---|
| RabbitMQ | Full C# / Java / MassTransit 8.5.1 matrix | Features outside the documented portable profile |
| Azure Service Bus | Emulator send/publish matrix plus periodic live topology, request, fault, naming, lock, and settlement checks | Sessions, managed identity, transactions, and native scheduling |
| Amazon SQS/SNS | Standard-queue send and raw SNS publication in both directions for C#, Java, and MassTransit 8.5.1 | FIFO queues and FIFO-specific ordering, grouping, and deduplication |
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.
The emulator is the routine gate for bidirectional directed sends and publications between MassTransit 8.5.1 and both MyServiceBus clients. Periodic live Azure runs verify cloud topology, default naming, correlated responses and faults, lock renewal, native temporary queues, and terminal failure settlement.
LocalStack verifies bidirectional directed sends and raw SNS-to-SQS publication between MassTransit 8.5.1 and both MyServiceBus clients. It is the default acceptance environment; the narrow real-AWS gate is reserved for emulator differences and AWS-only concerns. FIFO behavior is not part of this preview.
Live RabbitMQ tests verify C# and Java directed sends in both directions against real NServiceBus endpoints. Raw JSON remains neutral and does not imply NServiceBus compatibility. Review the exact profile →
Before 1.0, only the newest published preview is actively supported. Fixes are delivered in a newer preview.
The concise runtime and tooling policy is on the supported versions page.