Mike Budzynski posts

The IT industry is experiencing a shift from monolithic applications to microservices-based architectures.

La version 3 de la spécification OpenAPI, dernière version de la norme open source largement utilisée pour décrire les API, est désormais prise en charge, en préversion, par le service Gestion des API Azure.

Azure Integration Services will be hosting a joint Twitter Ask Me Anything (AMA), or actually “Ask Us Anything”, session for API Management, Logic Apps, Service Bus, and Event Grid on Thursday, December 6, 2018 from 8:30 AM to 10:00 AM Pacific Time.

The new Versions and Revisions feature was designed to fit as seamlessly as possible into our existing management API. From a high level perspective, working with a current Revision is identical to the way working with an API has always been.

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

Today we are excited to announce the public preview of support for Versions and Revisions in Azure API Management! This new feature gives you flexibility and control in how you manage change and the lifecycle of your API.

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.

A few months ago we added SOAP pass-through support to Azure API Management – thank you to all of you using and giving us feedback on this feature.

Over the past few years, an API description format called Swagger has quickly gained momentum. In order to reach it’s full potential the specification was recently donated by its owner Smartbear, to the OpenAPI Initiative group.

Many of our customers have requested the ability to use Azure API Management to create a proxy for their SOAP APIs in the same way that we allow them to for REST/HTTP APIs, enabling developer portal integration, analytics, policies etc