Architecture for distinguishing messages from multiple devices
Let's say I have 1000-10000 sensors. I work on azure. I want to distinguish sensors sending messages. I can (all that I currently know):
Create 1 iot hub with 1 device and send messages from all the sensors. and to distinguish sensors I need to include a special field (sensor id) in the message.
After that I can read it in trigger.
Create 1 iot hub with 1000-10000 devices and send messages from all the sensors. and to distinguish the sensors in a trigger I can use something like this:
var deviceId = message.SystemProperties["iothub-connection-device-id"];
where message is of type Microsoft.ServiceBus.Messaging.EventData
If I want to distinguish message, let's say, by a 'level' field (1, 2, 3..)
I can add this field into message and then set up routing, query, read this field and redirect to an appropriate end-point
Questions:
1. which of 1st and 2nd approaches is mostly useful/better on real projects with a bunch of sensors
2. Are there other ways to implement such distinguishing on Azure?
azure iot azure-iot-hub
add a comment |
Let's say I have 1000-10000 sensors. I work on azure. I want to distinguish sensors sending messages. I can (all that I currently know):
Create 1 iot hub with 1 device and send messages from all the sensors. and to distinguish sensors I need to include a special field (sensor id) in the message.
After that I can read it in trigger.
Create 1 iot hub with 1000-10000 devices and send messages from all the sensors. and to distinguish the sensors in a trigger I can use something like this:
var deviceId = message.SystemProperties["iothub-connection-device-id"];
where message is of type Microsoft.ServiceBus.Messaging.EventData
If I want to distinguish message, let's say, by a 'level' field (1, 2, 3..)
I can add this field into message and then set up routing, query, read this field and redirect to an appropriate end-point
Questions:
1. which of 1st and 2nd approaches is mostly useful/better on real projects with a bunch of sensors
2. Are there other ways to implement such distinguishing on Azure?
azure iot azure-iot-hub
add a comment |
Let's say I have 1000-10000 sensors. I work on azure. I want to distinguish sensors sending messages. I can (all that I currently know):
Create 1 iot hub with 1 device and send messages from all the sensors. and to distinguish sensors I need to include a special field (sensor id) in the message.
After that I can read it in trigger.
Create 1 iot hub with 1000-10000 devices and send messages from all the sensors. and to distinguish the sensors in a trigger I can use something like this:
var deviceId = message.SystemProperties["iothub-connection-device-id"];
where message is of type Microsoft.ServiceBus.Messaging.EventData
If I want to distinguish message, let's say, by a 'level' field (1, 2, 3..)
I can add this field into message and then set up routing, query, read this field and redirect to an appropriate end-point
Questions:
1. which of 1st and 2nd approaches is mostly useful/better on real projects with a bunch of sensors
2. Are there other ways to implement such distinguishing on Azure?
azure iot azure-iot-hub
Let's say I have 1000-10000 sensors. I work on azure. I want to distinguish sensors sending messages. I can (all that I currently know):
Create 1 iot hub with 1 device and send messages from all the sensors. and to distinguish sensors I need to include a special field (sensor id) in the message.
After that I can read it in trigger.
Create 1 iot hub with 1000-10000 devices and send messages from all the sensors. and to distinguish the sensors in a trigger I can use something like this:
var deviceId = message.SystemProperties["iothub-connection-device-id"];
where message is of type Microsoft.ServiceBus.Messaging.EventData
If I want to distinguish message, let's say, by a 'level' field (1, 2, 3..)
I can add this field into message and then set up routing, query, read this field and redirect to an appropriate end-point
Questions:
1. which of 1st and 2nd approaches is mostly useful/better on real projects with a bunch of sensors
2. Are there other ways to implement such distinguishing on Azure?
azure iot azure-iot-hub
azure iot azure-iot-hub
asked Nov 28 '18 at 11:22
amplifieramplifier
524422
524422
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518305%2farchitecture-for-distinguishing-messages-from-multiple-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53518305%2farchitecture-for-distinguishing-messages-from-multiple-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown