Solace consumers and producers connecting with diferent protocol

subhoatg
Thu, 28 Apr 2022 09:40:17 +0000
Solace Event Broker

We have multiple microservices connecting to Solace for different message publish and subscribe requirements. There are some java runtime-based microservices connecting using JMS APIs (using sol-jms library or apache qpid JMS 2.0 library), whereas there are golang and nodejs based runtimes connecting to solace based on runtime specific native Solace libraries.
While technically we tried that a non-java client using native solace APIs connect to solace and publishes the message in the topic and the subscribers use JMS durable subscriber to receive the message from the same topic or vice versa, Are there any difficulties or anomalies that can be expected or can we assume that Solace would do the protocol conversion and there are no issues with such usecases?

5 posts - 1 participant