Next values are estimations and all of them depend on the final production needs.
||Azure API Management
|New API effort
|Distribute in other location effort
|Min dev. environment costs
||1 machine = 587 euros yearly
||486 euros yearly
|Min pro. environment costs
||12 machines + 8,500 euros (yearly) for production support = 15,544
||28,288 euros yearly + 1,404 euros for VPN connection to private endpoints = 29,692
||– It is more flexible thinking about configuration and deployment options
||– Its management is easier and faster.
||– Hard maintenance
||– Its more expensive
– At this moment you can only use this over Azure infrastructure.
It can be installed on premise or it can be used in its cloud version. The cloud is a beta version. We will only consider the on premise versio. Thinking about an on premise solution you are responsible of deploy an environment that provides availability, scale capabilities, and low latency for all subscribers.
In order to create a preproduction environment all the components can be installed, configured and run in the same machine.
In order to create a production environment the different components (API Publisher, Gateway, Store, Key Manager, and 3 MySQL Databases) should be installed in separate servers. Multiple instances of these components should be set up behind a load balancer in order to provide high availability.
Additionally, a monitoring component could be included. Different configurations must be applied to each component.
A publisher can publish an API manually, using a WSDL in a SOAP Endpoint or other API definition file for another type of service.
A subscriber can discover and subscribe to an API throw Store component. After that she can invoke the API using SOAP or REST clients.