API Economy - Cuomo
•Download as PPTX, PDF•
5 likes•2,098 views
Exploring the API economy and API management
Recommended
More Related Content
What's hot
What's hot (20)
Similar to API Economy - Cuomo
Similar to API Economy - Cuomo (20)
More from Prolifics
More from Prolifics (20)
API Economy - Cuomo
- 1. APIs Exploring the API Economy & API Management @JerryCuomo IBM Fellow, VP WebSphere Strategy & CTO
- 14. API Management
- 15. © 2014 IBM Corporation IBM API Management Fully on-premise, multi-tenant solution, for API providers IBM DataPower API Gateway for security, control, integration & optimized access to a full range of Mobile, Web, API, SOA, B2B & Cloud workloads Over a decade of innovation, 10,000+ units sold, 2000+ customer installations worldwide A single, comprehensive solution to design, secure, control, publish, monitor & manage APIs
- 16. © 2014 IBM Corporation IBM API Management Manage and Share with developer communitie s 3 Create, assemble and version an API 1 Analyze & Monitor API usage 4 Secure, control & scale the API 2
- 17. © 2014 IBM Corporation Easily manage your APIs design, secure, control, publish, monitor & manage Explore API documentation Provision application keys Developer Portal API Manager Management Console Define and manage APIs Explore API usage with analytics Manage API user communities Provision system resources Monitor runtime health Scale the environment
- 18. © 2014 IBM Corporation Join the API Economy IBM API Management V3 – on-premise* & SaaS** Assemble business APIs easily Provide Secure or Open APIs on-prem or Cloud Control APIs at a fine-grained level Analyze API usage Manage private, partner, public app developers Provide self-service app developer onboarding What’s new in IBM API Management V3 Single console to manage REST & SOAP services and publish to various app developer communities with role-based access control Simple on-premise deployment architecture & elastic scalable cloud solution Enhanced OAuth 2.0 support for secure APIs Web service discovery from WSRR Policy-driven API control & visibility across various environments * on-prem GA date May 9 ** SaaS Statement of Direction
- 19. © 2014 IBM Corporation API Management v3 platform solution Management layer Gateway layer The management layer enables organizations to define, manage, expose and control APIs. Provides API Manager, Developer Portal and Management Console API configurations are deployed to the gateway, which provides the enforcement point for runtime policies to control API traffic. Gateway is DataPower physical or virtual
- 20. © 2014 IBM Corporation API Developer • How do I assemble APIs? • How do I manage security? • Will the infrastructure scale? • How do I measure performance? App Developer • Where do I access APIs? • How do I understand the APIs? • How do I measure success? API Product Manager • How can I rapidly release & update my APIs? • How do I publicize my API? • How do I measure success? Operations Lead • How do I manage all the API Environments that are being requested? • How can I scale each environment? • How can I easily find and fix issues? API Success Requires Addressing Needs of Multiple Stakeholders
- 21. © 2014 IBM Corporation Intuitively and iteratively define APIs and associated policies Rapidly assemble APIs via configuration, not coding Minimize risk with industry leading security & scalability Define API Developer Assemble Meter SecureDeploy, Test & Debug Monitor Scale Version 21 Create, Secure & Version APIs Simple interface accelerates iterative API development & deployment
- 22. © 2014 IBM Corporation Easily create, find REST and SOAP APIs Define the REST or SOAP API you wish to expose Import from a registry Search for, add custom tags to, and mark favorite APIs for easier discovery
- 23. © 2014 IBM Corporation Assemble New APIs Through Configuration Assemble a new API by combining multiple REST or SOAP services into a composite API Provide examples of the request and response messages, headers and parameters Drag and connect linking the request and response messages Transform the message elements with a click
- 24. © 2014 IBM Corporation Secure the API Identify application with Client ID & Secret Authenticate using LDAP or Authentication URL Authorize using OAuth 2.0 support with implicit grant type, authorization code, resource owner
- 25. © 2014 IBM Corporation Version the API for iterative development Version the API configuration in just one click Revert prior version
- 26. © 2014 IBM Corporation API Developer • How do I assemble APIs? • How do I manage security? • Will the infrastructure scale? • How do I measure performance? App Developer • Where do I access APIs? • How do I understand the APIs? • How do I measure success? API Product Manager • How can I rapidly release & update my APIs? • How do I publicize my API? • How do I measure success? Operations Lead • How do I manage all the API Environments that are being requested? • How can I scale each environment? • How can I easily find and fix issues? API Success Requires Addressing Needs of Multiple Stakeholders
- 27. © 2014 IBM Corporation “Productize” APIs using Plans Include multiple APIs and Resources per Plan Version your Plans Apply Entitlement by Plan or Resource Fine grained control over plan deployment Enforce Hard or Soft limits
- 28. © 2014 IBM Corporation Gain Business Insights Pinpoint key market fluctuations and find correlations related to your business • Business Analytics for both API provider and application developer: • Top traffic producing API , • Top application producing traffic • Structured Filtered Search across analytics for example • country:USA, color:red • Saved Searches and Filters for easy and consistent retrieval • Enables chargeback/billing for API consumption by developers
- 29. © 2014 IBM Corporation API Developer • How do I assemble APIs? • How do I manage security? • Will the infrastructure scale? • How do I measure performance? App Developer • Where do I access APIs? • How do I understand the APIs? • How do I measure success? API Product Manager • How can I rapidly release & update my APIs? • How do I publicize my API? • How do I measure success? Operations Lead • How do I manage all the API Environments that are being requested? • How can I scale each environment? • How can I easily find and fix issues? API Success Requires Addressing Needs of Multiple Stakeholders
- 30. © 2014 IBM Corporation Developer portal for API consumers Self service developer portal to explore APIs Browse API documentation Role-based access for viewing APIs Browse available plans with limits and choose from available plans
- 31. © 2014 IBM Corporation Register application Register new application Request security keys
- 32. © 2014 IBM Corporation Monitor API consumption Monitor most active applications and APIs
- 33. © 2014 IBM Corporation API Developer • How do I assemble APIs? • How do I manage security? • Will the infrastructure scale? • How do I measure performance? App Developer • Where do I access APIs? • How do I understand the APIs? • How do I measure success? API Product Manager • How can I rapidly release & update my APIs? • How do I publicize my API? • How do I measure success? Operations Lead • How do I manage all the API Environments that are being requested? • How can I scale each environment? • How can I easily find and fix issues? API Success Requires Addressing Needs of Multiple Stakeholders
- 34. © 2014 IBM Corporation Support many organizations with one solution Multi-tenant support for multi-provider organizations Provider and Consumer organization Visibility Alerts & notifications Send email directly through tool
- 35. © 2014 IBM Corporation Single Dashboard health monitoring Consolidated super admin view View system health DataPower load balancing SSL certificate Management Server scaling
- 36. © 2014 IBM Corporation Setup in minutes Easy out of the box setup LDAP or internal identity provider support
- 37. © 2014 IBM Corporation Where does API Management fit?
- 38. © 2014 IBM Corporation Customer success stories
- 39. Business Challenge Difficult for internal partners and developers to discover & access key financial services Lacked a standard ecosystem to manage internal partners including global credit card companies and merchants No visibility on Service consumption or ability to chargeback for LoB use of Services Example Apps Solution IBM API Management v2.0 & DataPower Gateway Leading Global Commercial Bank provides easy & secure access to key financial services Business Value Offers 3rd party merchants secure standards-based access to key business services as APIs, with a self-service experience Provides an internal ecosystem for partners and a central repository with usage analytics Drives innovation for Mobile application development $
- 40. Business ChallengeBusiness Challenge External business partners retrieve flight information by scraping the company’s website Unauthorized access to full flight information , with no usage analytics Delays in updating website – difficult for authorized partner to test changes REST-based API had just been built but security was not in place Solution IBM API Management v2.0 & DataPower Gateway Business Value Easily and securely connect company Website to new APIs, saving cost of building OAuth based secure access Enable secure exposure of APIs to External Business Partners, saving the implementation cost of building a developer support infrastructure with access management Ability to leverage existing investment in IBM DataPower gateway and internal team skillset Enable secure Mobile app integration with Enterprise APIs Large Airline in North America provides authorized access to flight services
- 41. Leading European Auto Manufacturer provides innovative vehicle connectivity with IBM API Management Business Challenge Offer innovative connectivity services to customers, improve the driver experience, improve safety, and create new revenue sources Improve driving conditions with driver profiling, eco- driving, fleet management, reduce accident risk Collect data to monetize them for partners Solution IBM API Management v2.0 & IBM MessageSight Business Value “Always connected” low-latency reliable communications with the car systems/apps and customer mobile apps Vehicle data APIs published on secure developer portal Internal & external developers use vehicle data to develop mobile applications Drives innovation for Mobile application development
- 42. Business ChallengeBusiness Challenge Difficult for internal partners and developers to discover & access key retail services Leverage mobility as a revenue stream and manage internal and external business partners No visibility on Service consumption or ability to chargeback for LoB use of Services Solution IBM API Management v2.0 & DataPower Gateway Business Value Offers 3rd party merchants secure standards-based access to key business services as APIs, with a self-service experience Provides an internal ecosystem for partners and a central repository with usage analytics Drives innovation for Mobile application development Leading Retailer in North America provides easy & secure access to retail services
- 43. Pitney Bowes, a global leader in software innovations, and mailing and shipping solutions, powers billions of transactions in modern commerce “Pitney Bowes location-based services on IBM BlueMix will allow innovators and developers to seamlessly extend their products and services to the cloud and mobile devices.” -Roger Pilc, Chief Innovation Officer, Pitney Bowes ..
Editor's Notes
- The "API economy” has changed how developers think about building apps, and how organizations deploy software in the cloud. Everywhere you look on the Web these days, it seems as if somebody’s launching new APIs. There are over 10,000 API documented on programmable web today… and is significantly increasing as we speak.
- Let’s look at the Cars.com mobile app as an example. Cars.com is a consumer of APIs, and has assembled several 3rd party apis together to form the base function of their cars app. For example, they use a Map Provider API to provide a “store locator function” APIs from a car dealer data aggregator for availability of certain makes and models. They use APIs from a Bank to offer Loan calculators and origination Auto insurance from an Insurance companies APIs And can imagine them using the new Xtify API from IBM to provide notifications, that a car they were looking for was now found.
- By consuming APIs to assemble their App, Cars.com… Can focus on their core competence and value add, rather then reinventing common capabilties Sees Quicker time to market, decreases cost and speeds up their cars.com app development and delivery Drives innovation, from others, into their app (like, perhaps the notifications from Xtify) Perhaps the insurance company offers value to their affiliates (which cars.com is now part of) by marketing the cars.com app to their insurance customers
- Now, let’s look at the API Economy from the Providers perspective The Bank can extend it’s reach beyond customers doing on-line banking. By offering an API, that includes Mortgage Calculators, Lon Origination, On-line Payment, and Account Query the bank can reach new mobile app providers link Cars.com (automotive sales), Zillow (on line real-estate), and Mint (financial data aggregator) Which…
- Expands into new customer bases and niches that the bank would normally not reach on their own Expands their brand and brand loyalty – you think about google when you see their maps appear in apps, perhaps you will think of “the bank” when you see their signature mortgage calculator And now you have third parties innovating with your content in ways you haven’t imagined and you are now monetizing those sources – across a wide array of app, running on a wide array of platforms
- As the definition explains, the Web Economy is where companies [providers], expose their internal digital assets or service in the form of Web APIs to third party [consumers] with the goal of unlocking additional business value through the creation of new assets. <MAXX> Emphasize definition… Also… Re-sub-title – The API Economy lifecycle
- The assets can be data, functionality, or computing resources. API Providers see three types of benefits when they liberate these assets externally, beyond their cooperate firewalls… They are: Wider reach Facilitation open innovation with external parties (usually developers) New or extended sources of revenue For example. Expedia launched their Expedia Affiliate Network developer program to allow access to their digital travel services and by doing so created many new revenue sources. Today they have about 5,000 developers whose apps and services account for over half of Expedia’s revenue.
- As I mentioned, The number of private and public APIs has been growing exponentially: (Source: Craig Burton) As of 24 March 2013, ProgrammableWeb documents 8,826 public APIs – This is expected to reach 30,000 by 2016 The commercial sector is quickly catching up, while APIs not publicly exposed (sometimes called “dark apis”) are thought to have a 5X growth rate of open APIs.
- Developers COMPOSE apps from existing services and the APIs fronting those services to create new business value The Millennial developers had no problem “renting” their code versus writing it… speed and iteration are paramount to the lean startup mentality Tools that help them assemble and manage their APIs usage across vendors rates highly on the list of demands
- It’s my estimation that Enterprise Mobile apps use between 5 and 12 APIs, which all the developer to quickly embed new functionality, that developers value to their end user
- The modern user expects to work in context and not jump between apps and systems… this is driving the need for more APIs integration.
- The API Economy lifecycle in completed, when the business uses API Analytics to gain insights from new customers, and optimize their business as a results – perhaps provide new api – that drive more revenue and customer satisfaction.
- On-Prem: V3 on-premise Announce Apr 22, 2014 in RFA58985. GA of v3 on-premise is May 9, 2014. SaaS: Same on-prem RFA also contains Statement of Direction for API Mgmt SaaS. Announce date for v3 SaaS is June 17, 2014, subject to change. GA date for v3 SaaS is June 20, 2014, subject to change Summary IBM API Management V3.0 delivers these key capabilities: Application programming interface (API) developer can create, secure, control, deploy, analyze, and manage SOAP and REST APIs and services for internal or external consumption quickly through a single console. API business owner can advertise, market, socialize and sell APIs as a product in developer communities (private, partner, and public) worldwide. Application developers can easily find, understand, and have tools to help them consume the API, and are able to manage their application and understand its consumption. IT operations can easily manage and upgrade the API environment to use existing investments in DataPower with the ability to monitor and scale without disruption to service. Technical Details: API Management V3.0 delivers the following sets of capabilities: 1. API developer can create, secure, control, deploy, analyze, and manage SOAP and REST APIs and services for internal or external consumption quickly through a single console. Policy-driven assembly that enables custom rate-limiting scenarios, enforced by the API Gateway (DataPower) Fine-grained ability to set API quotas and rate limits Visibility and control with ability to deploy across runtime environments Ability to easily create different versions of an API and understand where those versions are deployed, such as in test, staging, or production Ability to search for, add custom labels to, and mark favorite APIs and services for easier discovery in API Manager to work with APIs Ability to notify within API Manager to understand who is working on the APIs and any issues the APIs might be having Support for SOAP-based web services Discovery of web services from WSRR Ability to create an API by assembling REST-based and SOAP-based services Role-based access for viewing and working with the APIs Support for OAuth 2.0, an open standard for authorization 2. API business owner can advertise, market, socialize, and sell APIs as a product in developer communities worldwide: Ability to have more than one developer portal in order to support more than one developer community (private, partner, and public), with controlled visibility. Ability to create API plans which treat the APIs as product offerings, allows several APIs and resources per plan. Improved application developer management, with the ability to send an email to all application developers in a particular community. 3. Application developer (also API consumer) can explore API documentation and provision application keys: Developers can register their application, select API entitlement levels, and monitor their API usage. A single ID allows a developer to be a member of multiple API Management communities. Allows role-based access for viewing APIs. 4. IT Operations can easily manage and upgrade the API Environment using existing investments in DataPower with the ability to monitor and scale without disruption to service: Simplified operations environment for API assembly using DataPower Gateway Improved environment console experience Improved tenant management with the introduction of organization and owners Integration with enterprise authentication systems by using Lightweight Directory Access Protocol (LDAP) that enables administrators to streamline the user login process Simplification of deployment architecture to only two tiers: Gateway tier. DataPower appliance (virtual or physical appliance) Management tier - API Management virtual appliance
- Multi tenant - Provider Organizations Provider and Consumer Organization Visibility Alerts / Notifications Send email directly through tool.
- Consolidated super admin view. View system health. DataPower load balancing. SSL Certificate Management Server Scaling (not this dashboard)
- Easy out of the box setup. LDAP or internal identity provider support.
- Citi This is a use case that covers banks, payment processors, wireless telecommunications, merchants and their supply chain partners. Electronic wallets are getting significant airplay that falls in line with the growth of smart phones. Particularly with customers under 35, they rarely leave any location without taking their phone. Using it for financial transactions using Near Field Communication (NFC) is growing and the pace will quicken in 2014. API Management provides a secure environment for transactions to take place and includes near real time analytics to understand what is going on with the transactions. To help generate new applications from internal, partner or independent developers, a branded, easy to use developer portal is included.
- WestJet Airlines
- PSA Peugeot Citroen: https://w3-connections.ibm.com/blogs/WSSuccessStories/entry/websphere_and_big_data_technology_help_peugeot_charge_into_car2car_and_mobile_to_offer_innovative_connected_car_services?lang=en
- Neiman Marcus Electronic wallets are getting significant airplay that falls in line with the growth of smart phones. Particularly with customers under 35, they rarely leave any location without taking their phone. Using it for financial transactions using Near Field Communication (NFC) is growing and the pace will quicken in 2014. API Management provides a secure environment for transactions to take place and includes near real time analytics to understand what is going on with the transactions. To help generate new applications from internal, partner or independent developers, a branded, easy to use developer portal is included.