we are having multiple mobile users sending data to an Azure Event Hub but we’re encountering the limitation of having only 5 concurrent connections per consumer group, how can we address this issue?

Question

we are having multiple mobile users sending data to an Azure Event Hub but we’re encountering the limitation of having only 5 concurrent connections per consumer group, how can we address this issue?

Answer 1

Hello Keerthana, Welcome to MS Q&A

To address the limitation of having only 5 concurrent connections per consumer group in Azure Event Hub, you can consider the following approaches:

Create Separate Consumer Groups: By creating additional consumer groups, you can distribute the load and avoid hitting the connection limit. This involves creating separate inputs with different consumer groups for the same event hub.

Use the WITH Clause: For queries involving multiple inputs connected to the same Event Hubs consumer group, you can split your query into multiple steps using a WITH clause. This helps in managing the connections more efficiently.

These best practices can help mitigate scenarios where the number of readers per partition exceeds the Event Hubs limit of five.

References:

• Troubleshoot input connections
• Azure Event Hubs quotas and limits
• Azure subscription and service limits, quotas, and constraints

Please let me know if you have further questions

Kindly accept answer if it helps

Thanks
Deepanshu

Answer 2

Hello @Keerthana Merugu ,

welcome to this moderated Azure community forum.

Yes, as @Deepanshukatara-6769 mentioned it's highly recommended to use separate consumergroups for separate users so each gets a copy of the same incoming message, without 'collisions'.

It's even recommended to not use the $default consumergroup to prevent accidental information loss when a service or tool is added as a consumer that uses $default by default (as most services do).

Notice there are limitations to the number of consumergroups per eventhub:

If you need more users to consume messages, another architecture could be needed.

So, I post a separate message to propose an alternative.

Perhaps using Azure PubSub services (Websockets) or Azure SignalR services (Websockets but smarter and more .Net friendly) is a better solution to distribute messages to many users.

These push technology services are built for scale and lightweight so are commonly used for distributing messages. Two way communication is also offered, also popular in mobile solutions.

---

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.