Dynamic tenant setup at runtime

[WillemCoudron]

We have a multi-tenant setup where tenants are created dynamically. So we don't know all the tenant ids when the application starts, while the application is running new tenants can be created and the application can be onboarded for the tenant (this is done by just activating the application for the tenant, without the need for a new container to be spun up). This application is responsible for configuration.

Next to that there is a new container that is started for the runner specific for that tenant and a service bus topic (on azure service bus) is created with a listener for this container.

So from the main application a message should be able to be send to that dynamicly created topic for that specific tenant. We can't seem to figure out, using tenant configuration (cause we don't know the tenant id's at build or first startup) or using the toDestination method how to configure this. Could you guide us to the right path please?

Our latest attempt was the following:

DeliveryOptions deliveryOptions = new();

// Add headers to the existing Headers dictionary  
deliveryOptions.Headers.Add("runnerId", "runner-" + serviceBusRequestTopic.RunnerId);

// Dynamicly configure the tenant topic
deliveryOptions.ToDestination(new Uri($"asb://topic/tenant-{serviceBusRequestTopic.TenantId}"));

// Send the message to the topic using Wolverine  
await _messageBus.SendAsync(serviceBusRequestTopic, deliveryOptions);

[jeremydmiller]

Converting this to a discussion. Try just setting the topic name on DeliveryOptions or using BroadcastToTopic.

Please don't use GitHub issues for questions though.

[WillemCoudron]

When using toTopic, we get the same results

deliveryOptions.ToTopic("tenant-" + serviceBusRequestTopic.TenantId);

The messages are created on the default topic set in the UseWolverine di method:

opts.PublishMessage<ServiceBusRequestTopic>()
    .ToAzureServiceBusTopic("tenant-xxx");

When using broadcast:

await _messageBus.BroadcastToTopicAsync("tenant-" + serviceBusRequestTopic.TenantId, serviceBusRequestTopic, deliveryOptions);

We get the following error:

Most probably because the topic isn't registered in the UseWolverine method.

[WillemCoudron]

@jeremydmiller Just wanted to kindly follow up on this thread. We’re still trying to figure out the best way to dynamically send messages to tenant specific topics when those tenants (and their topics) are not known at startup.

If there is any recommended way to approach this or if we’re maybe approaching it the wrong way, we would appreciate any further guidance.

Thanks again for your time and support!

[ArneClaerebout]

@jeremydmiller we can't seem to find a way to get this working. Can we convert this back to an issue or feature request?
Or can you give us some more guidance?

[jeremydmiller]

@ArneClaerebout @WillemCoudron Sorry, looking a little more closely at what you're trying. We support what I think you're wanting to do for Rabbit topic exchanges and Kafka for whatever reason, but this has never come up w/ ASB before. You could do it by using a Uri on DeliveryOptions instead that would point to the right Azure Service Bus topic. I think that would be azureservicebus://topic/[topic name], but I'd have to verify that.

And you can always check out a possible JasperFx engagement if you haven't already. Drop me an email at [email protected] if you're interested in that.

[WillemCoudron]

Thank you for the guidance! The following seemed to work by overriding the destination uri on the message.

public async Task<bool> SendSyncRequestToServiceBusAsync(
    ServiceBusRequestTopic serviceBusRequestTopic,
    CancellationToken cancellationToken)
{
    // Build the topic name dynamically
    var topicName = $"tenant-{serviceBusRequestTopic.TenantId}";

    // Override the destination URI for this message
    var message = serviceBusRequestTopic
        .ToDestination(new Uri($"asb://topic/{topicName}"));

    await _messageBus.SendAsync(message);

    return true;
}