APIs & Integration Strategy
min of reading
October 21, 2018

Does your company consume APIs? Reduce costs and gain agility with Monitoring and Caching

Nicholas Gimenes
Leader of Growth & Product Marketing
Passionate about using technology and data to leverage digital strategies
More about the author
Computador e gráficos

Many external services are consumed through APIs by different departments (Marketing, Financial, R&D, Distribution, etc.), and this consumption is often not monitored or optimized, which leads to unnecessary expenses and loss of efficiency.

Through an API Management platform, it is possible not only to expose services via APIs, but also to monitor the consumption of external APIs, as well as creating a catalog of available APIs, apply security mechanisms, caching, call composition, and data transformation, among other resources.

The monitoring of consumption of APIs with dashboards and full tracing of calls facilitates the monitoring of unavailability and errors, double checking of collections, service quality evaluation by observing latency, perceiving rapid changes in the APIs (new versions, retirement, etc.), and performing a centralized management of expenses and the relative importance of different API providers (which can be used to negotiate better prices and diversify supplies).

Additionally, the use of caching enables the performance improvement with a lower latency and protection of against unavailability, as well as drastically reducing the costs of consuming APIs, when they do not have very frequent changes in the information they bring.

In turn, the creation of a catalog of APIs centralizes a variety of services and increases agility in the use, avoids duplicate contracting and lack of control of the IT team. This lack of control by the personnel in charge of the technology can lead to consumption of APIs with inadequate security, exposing sensitive information of the company.

Another useful feature is the creation of a mediation API layer, which favors the composition of calls, data processing, and application of security mechanisms.

In case of changes in the APIs, with the use of a mediation API layer, the interface for the API consumer remains the same. It is necessary to simply change the mediation API to another API or change the parameters to adapt to changes, without the need to change the different applications that consume the APIs.

Do you want to know more? Talk to one of our specialists, just fill the form below and soon we will get in touch ;)

Click and join the Sensedia News!

Click and join the Sensedia News!

Click and join the Sensedia News!

Thanks for reading!