azure-servicebus-topics

Azure service bus - how to add metadata to the message

こ雲淡風輕ζ 提交于 2020-05-24 03:29:25
问题 I am using .net core web app as the publisher and .net core console app as subscriber. I am able to successfully pass messages between these two systems using Managed Identities - set up in Azure portal. My question is I need to add metadata to the the message that is being sent. How do I do that ? Below is my publisher code : string data = JsonConvert.SerializeObject(payloadEvents); Message message = new Message(Encoding.UTF8.GetBytes(data)); var tokenProvider = TokenProvider

Azure service bus - how to add metadata to the message

穿精又带淫゛_ 提交于 2020-05-24 03:28:07
问题 I am using .net core web app as the publisher and .net core console app as subscriber. I am able to successfully pass messages between these two systems using Managed Identities - set up in Azure portal. My question is I need to add metadata to the the message that is being sent. How do I do that ? Below is my publisher code : string data = JsonConvert.SerializeObject(payloadEvents); Message message = new Message(Encoding.UTF8.GetBytes(data)); var tokenProvider = TokenProvider

Managing multiple queue/topic clients?

久未见 提交于 2020-05-16 03:42:46
问题 The challenge here is that I'm trying to create a single facade for dealing with queues and topics while maintaining semantics of Send vs. Publish For example: public interface IServiceBus { Task Send<T>(T message, string destination, SendOptions options = null); Task Publish<T>(T message, string topic, SendOptions options = null); } Send() would send a message to a queue and Publish() would publish a message to a topic. So I would need to have an instance of IQueueClient and ITopicClient to

Azure Service Bus Entity Throughput

跟風遠走 提交于 2020-05-13 04:21:12
问题 As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per queue/topic. This article: https://azure.microsoft.com/en... says 'This means that the overall throughput of a partitioned queue or topic is no longer limited by the performance of a single message broker or messaging store.' If we create a partitioned queue/topic, I believe it creates 16 partitions internally. My question is: Does the throughput of a partitioned queue/topic rise

Azure Service Bus Entity Throughput

試著忘記壹切 提交于 2020-05-13 04:21:07
问题 As per this article: https://azure.microsoft.com/en..., Service Bus can process upto 2000 messages per second per queue/topic. This article: https://azure.microsoft.com/en... says 'This means that the overall throughput of a partitioned queue or topic is no longer limited by the performance of a single message broker or messaging store.' If we create a partitioned queue/topic, I believe it creates 16 partitions internally. My question is: Does the throughput of a partitioned queue/topic rise

Azure Service Bus topics partitioning

こ雲淡風輕ζ 提交于 2020-01-04 05:49:27
问题 I'm trying to send a message to a topic which was created with both Enable duplicate detection and Enable partitioning options checked. I do not set SessionId and PartitionKey properties on my BrokeredMessage instance. According to this: If the queue or topic has the QueueDescription.RequiresDuplicateDetection property set to true and the BrokeredMessage.SessionId or BrokeredMessage.PartitionKey properties are not set, then the BrokeredMessage.MessageId property serves as the partition key.

Designing your Azure Service Bus topics - should you favor the use of more topics, or more filters?

断了今生、忘了曾经 提交于 2019-12-25 01:42:17
问题 I am in the early stages of designing the high-level structure of how two of our enterprise applications will broadcast to topics in the Azure Service Bus. I am a novice user of this technology, and after my preliminary reading of the documentation, I am tempted to use a simple solution: use a separate topic for each different event type that we want to broadcast. I favor this solution (over using filters) since it provides the most granular control over shared access keys, the least amount

What happens when you try to cancel a scheduled Azure service bus message that has already been enqueued?

☆樱花仙子☆ 提交于 2019-12-20 07:33:21
问题 I'm trying to come up with the best way to schedule a message for an Azure service bus queue or topic while leaving the option open for immediately sending a message instead of the scheduled message. I want to make sure I can protect myself against creating a duplicate message if I try to send the replacement message right at or after the scheduled time of the first message. What will happen if I try to cancel a scheduled message with CancelScheduledMessageAsync (for both QueueClient and

Azure topic and sending message over MQTT

早过忘川 提交于 2019-12-13 20:17:42
问题 Is it possible to send messages to azure to any custom topic via mqtt. All example that I've found so far work with standard topics 'devices/' + hubName + '/messages/events/' 'devices/' + hubName + '/messages/devicebound/#' Btw, I tried to send/subscribe on the topic/subscription above with MQTT.fx application and never received messages, although the connection was successful. 回答1: Did you have a look on these ?? Azure IoT Hub - Send message (C2D) to one device on 2 topics instead of

Where is the Log for Azure Service Bus Topic Subscriptions Messages Sent/Delivered?

隐身守侯 提交于 2019-12-12 11:19:01
问题 After searching in vain... where can I see a log/list of which Azure Service Bus Messages (content?) have been sent to a given Topic+Subscription and which ones have been delivered? Do I have to activate a special feature? If so, which? New or "classic" Azure Management Portal? Thanks! 回答1: You can't do that in either portal to my knowledge. You can use something like Service Bus Explorer http://blogs.msdn.com/b/paolos/archive/2015/03/02/service-bus-explorer-2-6-now-available.aspx to see