This is the final blog of this three-part series discussing the challenges facing technology leadership of traditional businesses in their API adoption journey. In my first part we had talked about the importance of APIs and API economy. In the next part, we had explored more on the unique challenges of enterprise APIs and the importance of an enterprise SOA strategy. In this blog, we will see how API Management solutions come to the rescue, but, more importantly, we will also talk about where such solutions might fall short.
API Management solutions go a long way to address many of these concerns. They abstract out a lot of operational aspects like security, API publishing, traffic management, user onboarding and access management, usage tracking and health monitoring, so that the technology teams can focus on the actual business of the API functionality. With the big players (the likes of Intel and IBM) entering the arena the market is heating up and there are tall claims on what an API Management platform can do for the enterprise. For the enterprises it would be a slightly bigger challenge. One challenge certainly is to find the right API Management solution to suit their needs. Currently none of the products in the market seem to address all the concerns of API Management. Admittedly products are evolving fast and it would be just a matter of time when the market will see products which will cater to most of the needs in some ways or the other.
However, there are certain other aspects that need to be tackled by the business and technology leadership before they can take the leap for enterprise APIs. Most enterprise APIs need support from other processes/systems in order to complete the functionality being exposed through enterprise APIs. Some examples are audit control, transaction traceability, reconciliation reports, customer service, batch integration with partners, etc. And these may not be able to be supported in the fast forward manner that APIs can be developed and exposed.
It is important for organizations to realize that just putting an API Management platform in place will not put them in the driver's seat. They have to take a more holistic view of their particular needs and ensure that all the supporting teams are able to join them in their API journey. It is not only a matter of just riding the bandwagon. It is also important to take all your stuff along to ensure you don't have to jump off the bandwagon half-way through.