-
Notifications
You must be signed in to change notification settings - Fork 74
Open
Labels
type: documentationA documentation updateA documentation update
Description
Hello there,
I'm working on a project where I want to connect to multiple Pulsar instances and based on what I have found Spring Pulsar "strictly" supports connecting to one Pulsar instance at a time.
I've managed to overwrite the PulsarAutoConfiguration class related beans, but it is a pain to handle them properly, as there are a few inconviniences during the setup like using @Primary and @Fallback beans in case of integration tests.
My "dream" setup would be the following:
spring:
pulsar:
tenant-a:
service-url: pulsar://localhost:6650
tenant-b:
service-url: pulsar://localhost:6651
tenant-c:
service-url: pulsar://localhost:6652
Right now I create 3 new configuration properties which will create 3 PulsarClient instances, and all the needed dependencies like the:
- DefaultPulsarConsumerFactory
- DefaultPulsarProducerFactory
- ConcurrentPulsarListenerContainerFactory
- PulsarTemplate
Where the PulsarClients are using the newly created one with the right service Url and authentication if needed.
Is there any better/already provided solution to my problem that would be cool.
Metadata
Metadata
Assignees
Labels
type: documentationA documentation updateA documentation update