Akana API Management

What do you like best?

All we need is to share .yaml document with the client who wants to access our published APIs on Akana. Publishing API is all configurable with easy to use interface. Best thing about Akana is its monitoring capability, due to which it is very easy to troubleshoot or check transaction logs even by business users without involvement of developers. Akana provides easily understandable dashboard view for all of its transactions to showcase the processing of message at each step.

What do you dislike?

The version that we have is very old. Now, the product has new features that we are going to implement in the next few months, such as API management and analytic reporting.

There are certain improvements can be made in graphical orchestration services.

Recommendations to others considering the product:

If you are looking to implement and publish your API, go for it.

What problems are you solving with the product? What benefits have you realized?

Being in healthcare Industry, we are using Akana to integrate with FDA (Food and Drug Administration of USA). Medical Devices company are supposed to register every single products at FDA for approval before launch. That FDA integration of our company systems through EAI is implemented at Akana. Every transaction coming inside or going out of our company network passes through Akana , be it any agency or vendor.

This way we are able to implement security and monitoring for these critical transactions in one place, with a uniformity in terms of control and policies.