Azure Service Bus, Event Hubs and Notification Hubs on the Classic Azure Portal Announcement

Important announcement for Azure Service Bus, Event Hubs, and Notification Hubs customers using the classic Azure Portal We want to notify our customers that on October 2, 2017 August 15, 2017, the Service Bus extension on the classic Azure Portal will be retired. This means you will no longer be able to create (example below),…

3

Azure Relay Namespace Separation

We wanted to provide an update on this blog post about separating our namespaces. You may have noticed we didn’t include specific dates for Azure Relay namespace separation. This was done so we could focus first on Service Bus queues and topics and Event Hubs. Now we are ready to follow a similar process for…


Namespace Auto-convert from Messaging type to EventHub type

Following our announcements about namespace separation, we are now offering the chance for customers to auto-convert their ‘Messaging’ type namespaces that contain eventhub entities into ‘EventHub’ type only namespaces in the Azure portal. As a pre-requisite in doing this, your ‘Messaging’ type namespace can only contain eventhub entities. If the namespace also contains queues, topics,…


ARM Templates: Deprecating the “kind” field

Since we started supporting ARM functionality in April, we have had some great feedback. If you haven’t had a chance to check it out, take it for a spin! As a result of moving to the New Portal, we have had a little bit of technical debt to clean up (click here to read more about…


Advanced Service Bus with AMQP

This post was written by my team member Clemens Vasters. The Advanced Message Queueing Protocol 1.0 is a standardized framing and transfer protocol for asynchronously, securely, and reliably transferring messages between two parties. AMQP 1.0 is the result of broad industry collaboration that brought together middleware vendors with many messaging middleware users. The technical standardization…


EventProcessorHost for Java Released

Any Java fans out there? We just added the EventProcessorHost to the master branch of our Event Hubs Java client. Now you can consume messages from an Event Hub with the same simplicity as our .NET client. No need to worry about partitions or check-pointing, we do all that work for you. And since its…


Service Bus client 3.2.2 is now live

Check out our newest release for the Service Bus client library! This release was primarily focused on Event Hubs, but there are still a couple of fixes in there for Messaging and Relay customers. The NuGet package can be found at https://www.nuget.org/packages/WindowsAzure.ServiceBus/3.2.2. Below are the release notes: EventHub/Messaging: Improve information in exception tracking in NamespaceManager…


How exactly does Event Hubs Throttling Work?

This is a good question and it comes up fairly often. Event Hubs provides capacity through a concept called a Throughput Unit (TU). A TU entitles you to a maximum of 1000 events per second or 1 MB per second of ingress (traffic to Event Hubs) and double that amount in egress – traffic out…


Service Bus, Event Hubs, and Web Sockets

We make some good stuff in the Azure Service Bus team and we tend to make it fairly quickly (both as it operates and as we iterate). For both Messaging (Queues & Topics) and Event Hubs we favor the AMQP protocol because the performance it gives us – including things like flow control and a…