How is the number of connections counted for licences?

General Discussions
2

Hi there @beautwaves_solace , welcome to the Community…! ?

So, just off the bat, the number of “connections” a broker is limited to is the number of TCP connections. Each app typically has just one TCP connection to the broker, on which they can send receive messages to lots of topics or lots of queues. So it should just be 10 if you have 10 apps.

But some points on Solace terminology… I can tell you’re new to Solace:

  • Queue’s don’t “connect” or “bind” to a topic object (there are no “topic objects” in Solace)… queues can have topic subscriptions to attract messages published on matching topics (topics are just metadata within each message… each could be unique). For example, my queue q1 could have a subscription for payments/*/new/> , and this would match messages published to topics: payments/bankA/new/cust123 payments/bankB/new/custxyz But not: payments/bankA/cancel/cust123 hr/bankB/new/cust123/policy
  • To publish to a queue, an application doesn’t have to “connect” to it… queues are the guaranteed storage for an associated consumer, to ensure messages don’t get lost/dropped when they’re slow or offline. Publishers just publish to whatever they want (topics or queues). That said: it’s our best practice to always publish to topics (and have the required topic subscriptions on the queues) vs. publishing directly to queues… this is required for more complext routing rules and broker topolgies (e.g. event mesh). So the “common queue” would have some subscription on it notice/> and any of the applications could publish to a topic that starts with notice/… and it would land in that queue.

Hope that helps! For more details on topics + subs in Soalce check out this video: https://www.youtube.com/watch?v=PP1nNlgERQI