question

KatareAshish-1107 avatar image
0 Votes"
KatareAshish-1107 asked PramodValavala-MSFT edited

APIM Premium with multiple gateway deployments

In a recent call with Microsoft it came to my notice the way APIM premium is being priced -

Use case - one APIM Premium instance with multiple gateways based on regions/location - i would charged for number of gateways multiplied by the amount for one APIM instance.
so if i have 3 gateways in different regions under one APIM instance then i would be charged close to 3*$2,795.17/month (which is a lot I believe)

https://azure.microsoft.com/en-us/pricing/details/api-management/

Trying to see the options to reduce the cost or if can use APIM Basic along with Multi region support for our API Management program..

Appreciate all the inputs around reducing the cost in Azure APIM

azure-api-management
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@KatareAshish-1107 Just following up here to see if my response helps

0 Votes 0 ·

still working on it but doesnt look like it can be done with simple traffic manager setup..

so now what we have is --

client <--> traffic manager --> APIM Premium instance --> Routing to private cluster (with the help of virtual network feature) --> Backend services

Now what we are thinking --

Client <--> traffic manager --> APIM Basic or standard instance --> Application gateway --> Backend services.

==========
Introducing application gateway so we can use the virtual network feature and route to private cluster..

=======

still not sure and exploring if the above approach should not add any other additional complexity which we may not be thinking .

==============

what basically we want reduce the cost by not using APIM Premium and fulfill our use case using the hybrid solution.. i am not sure if someone else would have used or having the same issue where premium cost is little too much for some basic kind of usage.


0 Votes 0 ·

@KatareAshish-1107 That seems to be right. Since other tiers of APIM don't support deployment into a VNET, you could leverage either Application Gateway along with IP Restrictions setup to ensure requests only come through APIM instances. This would increase the cost across the board since you would require instances in each region and more resources to manage.

0 Votes 0 ·

1 Answer

PramodValavala-MSFT avatar image
0 Votes"
PramodValavala-MSFT answered PramodValavala-MSFT edited

@KatareAshish-1107 Since multi region deployments are supported only the Premium Tier, you could try and mimic the same deployment strategy but with basic/standard instances and without a single control instance.

And the best way to achieve this would be to
1. Setup CI/CD with ARM Templates to ensure the same configuration is deployed to each region
2. Setup Traffic Manager for routing

But do note that the Premium Tier instances can support many more requests compared to basic/standard tiers. So, depending on your load, you might need multiple smaller instances to handle the same amount of load, which may come up to the same cost with extra work to synchronize all instances.


Another option you could consider would be to leverage Self Hosted Gateways that you could host in your VNET directly. If the services in the VNET are hosted as containers in AKS for example, the self-hosted gateway could be hosted there as well. Otherwise, you could leverage Azure Container Instances to run the gateway as well.

Note that this still requires APIM Premium Tier would with just one fully managed instance and depending on your projected load, you would allocate compute resources accordingly for the self-hosted gateway containers wherever they are hosted.




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.