Integration

As more and more serverless applications are developed, events are now the glue connecting all aspects of modern applications.

With the increased adoption of cloud and the need to innovate at a faster pace, we find customers embracing hybrid architectures in increasing numbers and demanding high productivity integration services.

I’m excited to announce today a preview of the Open Service Broker for Azure (OSBA), an implementation of the Open Service Broker API for Azure services.

Five highlights from last week in Azure for the week of October 16, 2017: Translating AWS to Azure with the Cloud Service Map, Azure Red Shirt Dev Tour ’17, New Azure Government capabilities, New previews on Azure, and weekly Azure shows to catch.

The set body policy is used for changing the request or response body.

When talking to developers building HTTP APIs the subject of versioning comes up regularly. A quick web search will reveal hundreds of articles promoting guidance on the subject.

With the introduction of Event Grid, Microsoft Azure now offers an even greater choice of messaging infrastructure options.

Azure Service Bus .NET Standard client is generally available. With it comes support for .NET Core and the .NET framework. And as mentioned in an earlier post it also supports Mono/Xamarin for cross-platform application development. This is only the start of greater things to come.

Azure Relay Hybrid Connections is generally available.

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.

Today marks the release of Microsoft BizTalk Server 2016.