In my previous blog post, I wrote about how an API Management solution can help your business create mobile apps more quickly by leveraging external development communities. In this blog post, I will discuss the stakeholders of an API Management solution and describe how the newly-released IBM API Management product can meet their requirements.
API Management stakeholders
- Business users such as the chief marketing officer, chief social officer, product manager or strategy manager
- IT (Information Technology) operations
- App developers, both internal and external
A complete API Management solution should address all of these stakeholder requirements. IBM API Management does this through the four elements summarized in the next section: creating, securing, socializing and managing.
API Management elements
- Proxy existing Representational State Transfer (REST) services in the business
- Assemble data from other systems such as databases, Salesforce.com, SOAP-based services or HTTP data sources
- Access to APIs can be managed using a combination of an API key and secret.
- App users can be authenticated using HTTP basic authentication or OAuth 2.0.
- The solution provides built-in caching, quota management and flood control.
- Ability to publish API documentation
- Ability to add links to social media communities
- A self-service developer registration process
- A sandbox test environment
- Top traffic by API
- Top traffic by app
- Geolocation of traffic
- Optimize infrastructure using operational metrics
- Manage development accounts and access
- Bill for API consumption by developers
- Establish entitlements to meter API usage
If you’re interested in the IBM API Management product, please read more details in the product announcement, sign up for a free trial of the cloud offering, leave a comment below or connect with me on Twitter.