Azure / Azure/azure-iot-hub-node

Opening multiple connections with IOT Hub as a publisher

Open
#51 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
3
Forks
18
PR merge metrics
No merged PRs in 30d

Description

I need advantages and disadvantages of opening multiple connections with IOT Hub as a publisher.

Basically I have multiple services (node applications) each opening a connection with IOT Hub to send messages (C2D) to IOT devices. Right now I am able to open the connection and also send (C2D) messages.

For reference (The devices use mqtt to connect to IOT Hub)

Is this the right approach of opening multiple connections with IOT Hub? Can I get advantages and disadvantages of taking this approach or if I could get a better approach for handling this scenario it will be helpful.

I have tested this scenario by creating multiple node processes and opening multiple connections to IOT Hub as a publisher in each node process and it lets me connect.

The only issue is any one of the node process gets the feedback. Apart from that all the node process are able to connect and send messages.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is identified. Start by reviewing the Node SDK's publisher connection and feedback behavior described in the issue, then determine what supported multi-service approach and feedback semantics should be documented or changed; done requires a decided recommendation.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, nodejs, typescript
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.