azureservicebus

The Azure Event Hubs overview article states the following: The number of partitions is specified at the Event Hub creation time and must be between 8 and 32. Partitions are a data organization mechanism and are more related to the degree of downstream parallelism required in consuming applications than to Event Hubs throughput. This makes the choice of the number of partitions in an Event Hub directly related to the number of concurrent readers you expect to have. After Event Hub creation, the partition count is not changeable; you should consider this number in terms of long-term expected

I've been dealing with a spate of Timeout's from TopicClient and I think it may be related to object lifetime and disposal. I'm using the TopicClient class from Microsoft.ServiceBus.Messaging and reading this Best Practices Guide states You should not close messaging factories or queue, topic, and subscription clients after you send a message, and then re-create them when you send the next message. Closing a messaging factory deletes the connection to the Service Bus service, and a new connection is established when recreating the factory. This is confusing to me - this document doesn't

I have several services in Azure and i would like to sync changes between them using some kind of pub/sub service. I am looking into Redis and Azure Service Bus. The data to be synced is very simple - mostly strings up to 100 characters I would like to know what is the preferred choice for me - or if i am in the right direction.. My requirements are simple: Low latency - Many small operations optional - be able to install the solution on-premise and not in Azure Don't use Redis for this. Redis PubSub isn't reliable (it's fire-and-forget ). What would happen if no one is listening when Redis

I am new to Azure logic apps. I have a service bus and pass a json object message to that service bus then I set up an action in logic apps to listen to my service bus. So everytime a new message come in to that service bus my logic apps will pick it up and send it to http. My question is how can I grab the property from the message in service bus and pass it to my http action. I tried this “Id” : “@{json(triggerBody()[‘ContentData’]).id}” but it's not working Who and how is sending the message on the queue? I read a json message property (DestinationPath) in this way: @{json(base64ToString

I have implemented a long running process as a WebJob using the WebJobs SDK. The long running process is awaited because I want the result. public async Task ProcessMessage([ServiceBusTrigger("queuename")] MyMessage message) { await Run(message.SomeProperty); // takes several minutes // I want to do something with the result here later.. } What I can't figure out is why the message sometimes is abandoned which of course triggers the handler again. I've tried to debug (locally), setting breakpoints before ProcessMessage finishes and I can see that it appears to finish successfully. The Sevice

I am using azure service bus for the first time to transfer message between C# source and python client. I am creating ServiceBusService object and using it i fetch message from function receive_subscription_message . The payload i get is not as expected. My code is something like below. bus_service = ServiceBusService(service_namespace="service_namespace", shared_access_key_name="All", shared_access_key_value="password") msg = bus_service.receive_subscription_message('test', 'test', peek_lock=True) print(msg.body) msg.delete() msg.body gives a byte string like below: b'@\x06string\x083http:/