MyServiceBuspreview

Asynchronous messaging for .NET and the JVM

One messaging model for distributed services.

Model commands, events, requests, and consumers consistently across C#, Java, and Kotlin. RabbitMQ is the verified broker baseline; Azure Service Bus and Amazon SQS/SNS are preview transports. A local mediator covers deliberately in-process dispatch without requiring a broker.

Pre-1.0 · RabbitMQ verified · Azure and AWS preview transports
01 — QUICK START
Loading code…
Loading code…
Continue the C# guide

Where it fits

Three ways to adopt MyServiceBus.

01

Extend a .NET estate

Connect Java services to MassTransit through the documented common interoperability subset.

02

Replace MediatR

Handle local commands, queries, and notifications through dedicated APIs and generated dispatch.

03

Start cross-platform

Choose C#, Java, or Kotlin per service while keeping one permissively licensed messaging core.

Before you adopt

Know the current boundaries.

01

Pre-1.0 APIs

Preview releases can change configuration and public APIs before a stable compatibility policy is published.

02

Focused scope

The portable subset is smaller than MassTransit and does not replace its feature breadth, maturity, or commercial support.

03

Transport evidence

Ordering, settlement, topology, quotas, and operational behavior still need validation against the broker you will run.

Technical documentation

Evaluate the model, then implement it.

Start with fit and compatibility boundaries, then move into concepts, transport behavior, reliability, and testing.