Closed jeremydmiller closed 3 months ago
I.e., be able to connect one single application to multiple Rabbit MQ brokers, multiple Azure Service Bus connections, multiple AWS SQS connections
Definitely making this part of Wolverine 3.0.
Strongly consider making this dependent on the Aspire integration -- which is really depending on the DI integration of the connection information
Splitting the issues for this for different transports
I.e., be able to connect one single application to multiple Rabbit MQ brokers, multiple Azure Service Bus connections, multiple AWS SQS connections
Definitely making this part of Wolverine 3.0.
Strongly consider making this dependent on the Aspire integration -- which is really depending on the DI integration of the connection information