In time for the Build 2018 conference, the Relay learned a brand-new trick that you may have missed leaning about amidst the torrent of other Azure news, so we’re telling you about it again today: The Relay now also supports relayed HTTP requests over its
With the introduction of Event Grid, Microsoft Azure now offers an even greater choice of messaging infrastructure options.
We are announcing today that we will not provide an immediate successor for the standalone, on-premises Service Bus for Windows Server 1.1 product. The product, available as a free download, will go out of mainstream support on January 9, 2018, as announced at product release.
The Azure Relay service was amongst the initial core set of services available on Azure, and is a fundamental hybrid cloud integration tool for many current solutions running on Azure.
On May 31, 2006, Microsoft announced the “Live Labs Relay” as a technology preview.
After May 1, 2016, Service Bus will introduce separate namespace types for Event Hubs, Relay, and the Broker (Queues and Topics). This change will affect only newly created namespaces. Any existing namespaces will work as they do today.
Today, we’re happy to announce a brand new, open source Azure Event Hubs client for Oracle’s Java® programming language, and for all other JVM-based languages leveraging Java libraries. The client library is made available under the MIT license.
For this year’s State of the Union address by President Obama, television networks CNN, MSNBC and Telemundo, along with their web and mobile properties took the people’s pulse with Microsoft Pulse, powered by Azure Event Hubs.
With Service Bus Premium Messaging, you benefit from the economics and operational flexibility of a multi-tenant public cloud system, while getting single-tenant reliability and predictability.
As announced at BUILD this week, the Service Bus September 2011 Release is now available. This is the biggest feature update in the production environment since the service launched in January 2010.
