The commoditization of technology has reached its pinnacle with the advent of the recent paradigm of Cloud Computing. Infosys Cloud Computing blog is a platform to exchange thoughts, ideas and opinions with Infosys experts on Cloud Computing

« Take your business where your digital consumers are - on the cloud! Part2 | Main | Take your business where your digital consumers are - on the cloud! Part3 »

Riding the Band Wagon for Enterprise APIs - the Technology Leadership Dilemma (Part 2)

In the previous blog we had looked at the importance of APIs and the API economy and had outlined the challenge that the technology leadership of traditional businesses face.  In this part we talk about the nuances of Enterprise APIs and what makes them more challenging to be exposed by traditional businesses.

Traditional businesses are a mix of different technology platforms and legacy systems are still a reality for most financial, health and travel industries. While most distributed teams can easily adopt agile or rapid development methodologies, it is a bit more difficult for legacy systems to take that leap. Additionally enterprise APIs presents unique challenges in itself, challenges that are very different from those of consumer APIs. Most enterprise APIs deal with Personally Identifiable Information (PII) or company confidential data. Consequently, there are higher security, compliance and regulatory needs. Many of the enterprise APIs are also transactional in nature requiring heavy integration with multiple back-end systems. Hence delivering such APIs comes with the additional baggage of being able to ensure transactional handling capabilities, complete audit, traceability and non-repudiation characteristics.

The dilemma of the technology leadership for such traditional businesses is formidable. On one hand they have to deliver to continue to remain relevant and competitive while on the other hand they have to take care of the various facets of the enterprise APIs that they are exposing.

Enterprise SOA readiness plays a key role in the ability for the enterprise to deliver such APIs. Organizations which have got their act together in gaining SOA maturity will definitely find themselves a few steps ahead in their API journey. Trying to fix a broken SOA strategy with a new API strategy might not be a promising idea.

In the last part of this three-part series, we will discuss how API Management solutions can help address some of the concerns for these businesses and where such solutions fall short. 

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.