In this Digital Transformation era, it is of paramount importance for organizations to adopt APIs to execute ideas quickly and acquire new business opportunities. APIs (Application Program Interface) play an essential role, as they are the building blocks of Digital Transformation, thus enabling organizations to deliver an exceptional customer experience, and thereby increasing their revenue streams and optimizing internal IT operations.
Gartner predicts that 50% of business-to-business collaboration will take place through APIs by 2017, and by 2018 75% of Fortune 1000 firms will offer public Web APIs1
That is Awesome! APIs are transformative, and the benefits are multi-fold. However, how do Organizations build an “API Economy” so that they do not fall behind in the race? Are there any challenges?
Yes, there are:
How soon can one conceptualize, develop and publish the APIs?
How do we orchestrate APIs within the suite of enterprise applications besides access to external third party developers and partners?
Consideration of best practices and industry standards to secure open/public APIs.
Ability for third party developers to discover and trial-option before using the published APIs. The ideal solution would provide a self-service portal that can enable some of these, including documentation, authorization and support.
Simplifying the development, testing and deployment aspects thereby mitigating the risks involved while reacting to changing business needs.
Provision to log and understand the API usage metrics thereby providing an opportunity to optimize the published APIs. Continuous monitoring and improvement is the key to success.
From providing various subscription models to defining usage tiers. There should be a trial option before charging the third party partners and developers.
API Centric Design is a strategy that provides an insightful approach to the design, development, and provisional aspects of API that one can apply to overcome some of these challenges.
Here are the aspects that one should consider for the design and development of APIs:
Emphasizes on the trade-offs of various architectural styles and patterns such as SOAP, RESTful and Event driven based APIs. It is essential to understand the business needs and characteristics of APIs and the consideration of various factors before deciding upon the pattern.
Key design principles to consider at the beginning of an API design and development project.
Industry specific standards and guidelines for the design and development of APIs.
It is essential to manage the APIs once published for external/internal users. Published APIs bring in revenue and hence adherence to contract definition, continuous monitoring, understanding the usage metrics, and other non-functional needs such as security, scalability, and availability. All are important factors of API management. A few platforms such as Apigee, WSO2, Amazon API Gateway, and many prominent providers offer capabilities around these, and one can make viable options in deciding to build vs. buy.
Contact Ness if you are looking for assistance with your API strategy. This is the first blog in a 3-part series on API. “Part 2: Key API Design Principles and Best Practices can be viewed here. “Part 3: Understanding the Capabilities of API Management Platforms can be viewed here.