FxMap.Azure.ServiceBus 4.1.1

<p align="center"> <img src="https://raw.githubusercontent.com/quyvu01/FxMap/main/FxMap.png" alt="FxMap" width="96" /> </p>

<h1 align="center">FxMap.Azure.ServiceBus</h1>

<p align="center"> Azure Service Bus transport for FxMap — request/reply between services over session-enabled queues. </p>

<p align="center"> <a href="https://www.nuget.org/packages/FxMap.Azure.ServiceBus"><img alt="NuGet" src="https://img.shields.io/nuget/v/FxMap.Azure.ServiceBus.svg" /></a> <a href="https://www.nuget.org/packages/FxMap.Azure.ServiceBus"><img alt="Downloads" src="https://img.shields.io/nuget/dt/FxMap.Azure.ServiceBus.svg" /></a> <a href="https://github.com/quyvu01/FxMap/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/badge/license-Apache--2.0-blue.svg" /></a> </p>

<p align="center"> <a href="https://github.com/quyvu01/FxMap"><b>FxMap</b></a> · <a href="https://fxmapper.net"><b>Documentation</b></a> · <a href="https://github.com/quyvu01/TestFxMap-Demo"><b>Demo project</b></a> </p>

A transport carries FxMap requests between the service that needs data (the client) and the service that owns it (the server). Every service that maps data needs the core FxMap package; the owning service also needs a data provider (EntityFrameworkCore or MongoDb), and both sides use the same transport. Requests are batched per distributed key, so a hundred objects that need a UserName produce one request.

Installation

dotnet add package FxMap.Azure.ServiceBus

Usage

builder.Services.AddFxMap(cfg =>
{
    cfg.AddEntitiesFromAssemblyContaining<SomeEntityAssemblyMarker>();
    cfg.AddProfilesFromAssemblyContaining<SomeProfileAssemblyMarker>();
    cfg.AddAzureServiceBus(c =>
    {
        c.Host("Endpoint=sb://...");   // connection string
        c.TopicPrefix("staging");       // optional
        c.MaxConcurrentSessions(16);    // optional, at least 1
    });
});

Naming and sessions

For every distributed key FxMap creates session-enabled queues at startup: fxmap-request-{namespace}-{type name} for requests and fxmap-reply-{namespace}-{type name} for replies (dots replaced by hyphens, lower case). TopicPrefix prepends "{prefix}-" to both. Avoid using these names for anything else.

Related packages