How can we improve Azure API Management?

Self-hosted API Management gateway

To expand support for hybrid use cases and enable more efficient on-premises-to-on-premises call patterns for internal-only and internal/external APIs, we will provide an option for customers to self-host a containerized version of the API Management gateway component (fully equivalent to the gateway in the cloud, not a “micro-gateway”) on-premises or other environment e.g. other public clouds. Self-hosted gateway will require and will be managed from a cloud-based Azure API Management instance.

761 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
AdminAzure API Management Team (none of your business, Microsoft Azure) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

23 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Jørgen Michelsen commented  ·   ·  Flag as inappropriate

    Are there any plans regarding the licensing model for self-hosted gateways? Will they be free of charge as long as the management instance is paid for?

  • Andrej Medic commented  ·   ·  Flag as inappropriate

    Wondering how this wold integrate with Service Fabric and Service Fabric Mesh clusters in Azure and also on-prem? For example will we be able to Self-host the API Management gateway in an Azure SF cluster?

  • Alessandro Moura commented  ·   ·  Flag as inappropriate

    Yes, this will be very much appreciated by companies that just have API communication in the internal network and it does not make sense to go to the cloud to route back to the internal network.

  • Eurico Borges commented  ·   ·  Flag as inappropriate

    This is a step in the right direction and I think it will certainly benefict many companies that want to have an API led architecture also on-premise only.
    What I would strongly request is the possibility to aggreagate centraly the analytics and management of several of these on-premises gateways.

  • Daniel Hoenig commented  ·   ·  Flag as inappropriate

    This has been set to planned for 2 years...is it really planned? We would choose Azure APIM over the other api management tools if this feature existed. Since it does not, Azure APIM is off the list.

  • Nikolai Blackie commented  ·   ·  Flag as inappropriate

    Please split API gateway from API Management and allow gateways to be deployed anywhere. 2 years in planning, hope we see an awesome result. Getting slated in industry analysis and makes it very hard to sell solution into organisations with on prem gateway support. Also latency is a massive issue.

    https://www.gartner.com/doc/reprints?id=1-4Y21K37&ct=180501&st=sb
    "As the offering became generally available as long ago as 2014, Gartner has concerns about Microsoft's commitment of resources to it, and about the offering's long-term viability in a rapidly evolving API management market.", "Azure API Management supports virtual network connectivity for access to on-premises resources, but does not have a customer-managed deployment option that could be hosted on-premises or outside Azure"

  • Michael O'Brien commented  ·   ·  Flag as inappropriate

    Azure Stack is a new on premise offering that currently does not have Azure API Management, but would be a good service offering for the on premise Azure Stack option.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Is there any update on when this feature will be developed and released? While we look to cloud host our services by default, there are situations where government regulations require on premise installation and we would like to use the same framework.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a critical issue for us (for performance, security and compliance reasons), and is the main reason why we're considering other other API Platforms than Azure - like Akana (the proxy and api mgmnt package may be installed on-prem).

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a critical issue for us (for performance, security and compliance reasons), and is the main reason why we're considering other other API Platforms than Azure - like Akana (the proxy may be installed on-prem).

  • Marshall Brown commented  ·   ·  Flag as inappropriate

    Part of my company's interest on having on-premise deployment is similar to Mat's: we also see a lot of internal use for it and want to avoid the overhead of sending traffic to the cloud and back, especially since the options for ExpressRoute are rather limited for our particular data center.

  • Mat commented  ·   ·  Flag as inappropriate

    For my organization we currently keep all traffic internal and would like to utilize the API management capabilities without having to send internal traffic out to the cloud then back to the internal network. Adding the API Management capabilities to the Azure Pack would be a home run for us.

  • Stephen Curry commented  ·   ·  Flag as inappropriate

    A local endpoint that received config from the cloud and passes usage back to the cloud would allow internal devs to use the service for local apps

  • Aldis Vilums commented  ·   ·  Flag as inappropriate

    Miao,

    although I believe the primary scenario you are targeting is exposing APIs to partners over the internet, in my experience there is still a large set of customers running community clouds (specifically government customers that need data exchange and cooperation between agencies). And especially in cases when we are not talking US customers, many still would require on-prem version of the whole API management solution.

    Thanks for looking into this!

← Previous 1

Feedback and Knowledge Base