lean . enterprise . middleware


APIs and Beyond

       Chris Haddad
VP, Technology Evangelism

    Paul Fremantle,
  CTO and Co-Founder

   © WSO2 2011. Not for redistribution. Commercial in Confidence.
Business APIs



“APIs provide a way to make resources
  available for internal and external
  partners to access information and
               services.”
API Architecture

An API is a business capability delivered over the Internet
  to internal or external consumers
   • Network accessible function
   • Available using standard web protocols
   • With well-defined interfaces
   • Designed for access by third-parties
A Managed API is:
   • Actively advertised and subscribe-able
   • Exhibits high Quality of Service (QoS)
   • Available with Service Level Agreements (SLAs)
   • Secured, authenticated, authorized and protected
   • Monitored and monetized with analytics
APIs All the Way…
APIs and Business Consumers
                                 Mobile Apps


           Legal or
         government                                       Employees
         authorities




                               Core
                             Business
      Corporate              Services
                                                               Suppliers
      Websites




                                               External
                  Distributors
                                               Partners
Don’t ignore API Proliferation




Source: http://blog.programmableweb.com/2011/10/03/4000-web-apis-whats-hot-and-whats-next/
Some Statistics
    • Twitter : More than 15 billion calls per day 75% through APIs

              • Netflix : More than 1 billion calls per day

            • Facebook : More than 5 billion calls per day

         • Amazon : More than 260 billion objects store in S3

• eBay : More than 2 billion transactions per day (using the WSO2 ESB)
The New Web

Create an Architecture of Participation




Source: http://blog.programmableweb.com/2011/01/03/api-growth-doubles-in-2010-social-and-mobile-are-trends/
API Opportunities




              “APIs create a new relationship opportunity –
                B2D; Business to Developer, that creates
                              direct B2C, B2B
                       and indirect B2C relations”
Source: http://asanka.abeysinghe.org/2012/02/apis-create-new-relationship-b2d.html
API Opportunity
WSO2’s API Management Vision
• Create APIs
 • WSO2 Application Server, Data Services Server and ESB
• Find and subscribe/buy APIs
 • API Store and Governance                   WSO2 API
• Manage, secure and protect APIs             Management
                                              Platform
 • API Management and Gateway
• Monitor and Monetize APIs
 • API Monitoring and Analytics
• Develop, host and run API-based applications in a
 Platform-as-a-Service
 • WSO2 Stratos and Cloud Development Platform
 • API Cloud
The API Platform Architecture


                            Self-service Access
 API Store Front API Explorer                        API Back Office     Key Management     Monetization Engine    API Governance




                                API Gateway
                                                                            Load Balancer      Mediation Broker
                                                     Authorization and
                                                      Authentication                                                   API Cloud




Mobile and Web
 Applications                                                                                  API Analytics Data Store
                                 Consumer Identity              Traffic Control
                                     Provider                       Policies                                      Monetization Repository
                                                                                  API Repository
Business Design of the APIs
• Know the consumer
   • Who will use the APIs (both developers and final end-user)?
   • What type of applications will use the APIs?
   • What business assets will be delivered?

• Maintain Operational Control
   • What Quality of Service is expected?
   • Who can access the assets?

• Remember Usability and Monetization
   • How will the API expose business assets?
   • How will you demonstrate business value via direct revenue, chargeback, or
     showback?
API Ecosystem Model
•From   SOA lessons learned, best practices roles

•API Publisher
  • Builds, publishes, manages, and versions API
  • Understand business and technical requirements
  • Cares about usage and scaling
  • Seeks feedback, ratings, usage

•API Manager
  •Promotes and encourages consumers to adopt API
  •Determines usage patterns and how to best monetize asset
  •Monitors and secures

•API Consumer
  •Understands the interface definition
  •Subscribes and connects application to API
  •Monitors own usage and cost basis
  •Provides feedback and ratings
Architect’s View of API Objectives

API Publisher
•Publish easily consumable APIs
•Increase API accessibility, availability, reliability, and security
•Drive API adoption by building communities and promoting APIs

API Consumer
•Identify API matching project requirements
•Evaluate API and rapidly compose solution
•Assess service level agreement and cost
•Socialize project requirements with API Publisher
 API Manager
 •Meter, rate limit, and monetize investment
 •Promote and enforce API lifecycle best practices
 •Optimize API portfolio and reduce custom development
 •Identify usage patterns, successful providers, and business opportunity
Developer’s View of API Objectives

 API Publisher
 •Quickly develop and publish secure RESTful APIs
 •Associate service level policies and monetization rates
 •Promote samples, how-to-guides, and roadmaps
 •Evolve and version service

 API Consumer
 •Register as an API consumer
 •Review API documentation and match project requirements
 •Obtain API key, integrate with API, test API
 •Subscribe to API at a specific service level and pricing rate

 API Manager
 •Follow best practice API lifecycle workflow
 •Version API
 •Request API features and file issue
 •Automated migration across lifecycle environments (e.g. Dev/QA/Prod)
Built on Proven Components

• API
    Management Platform leverages WSO2 proven
 components:
  o   WSO2 ESB
         used as API Gateway by eBay, AAA, and others. eBay
          handles > 1 billion API calls/day
  o   WSO2 Governance Registry
         used by British Airways, Intermountain Healthcare, and
          many others
  o   WSO2 Identity Server
         used by Citigroup, Federal Home Loan Bank of SF, US
          Navy and others
Scalable Deployment Architecture
API Store Features
API Publisher Features
Adding an API




                See more
Listing APIs
API Store
Scalable Analytics Deployment
Questions?




             http://www.flickr.com/photos/oberazzi/



                                                      25
Resources
Follow us:
                           http://twitter.com/#!/wso2

                                                        Follow us:
Contact us:
                                                        http://twitter.com/#!/wso2
http://wso2.com/contact/

APIs and Beyond

  • 1.
    lean . enterprise. middleware APIs and Beyond Chris Haddad VP, Technology Evangelism Paul Fremantle, CTO and Co-Founder © WSO2 2011. Not for redistribution. Commercial in Confidence.
  • 2.
    Business APIs “APIs providea way to make resources available for internal and external partners to access information and services.”
  • 3.
    API Architecture An APIis a business capability delivered over the Internet to internal or external consumers • Network accessible function • Available using standard web protocols • With well-defined interfaces • Designed for access by third-parties A Managed API is: • Actively advertised and subscribe-able • Exhibits high Quality of Service (QoS) • Available with Service Level Agreements (SLAs) • Secured, authenticated, authorized and protected • Monitored and monetized with analytics
  • 4.
  • 5.
    APIs and BusinessConsumers Mobile Apps Legal or government Employees authorities Core Business Corporate Services Suppliers Websites External Distributors Partners
  • 6.
    Don’t ignore APIProliferation Source: http://blog.programmableweb.com/2011/10/03/4000-web-apis-whats-hot-and-whats-next/
  • 7.
    Some Statistics • Twitter : More than 15 billion calls per day 75% through APIs • Netflix : More than 1 billion calls per day • Facebook : More than 5 billion calls per day • Amazon : More than 260 billion objects store in S3 • eBay : More than 2 billion transactions per day (using the WSO2 ESB)
  • 8.
    The New Web Createan Architecture of Participation Source: http://blog.programmableweb.com/2011/01/03/api-growth-doubles-in-2010-social-and-mobile-are-trends/
  • 9.
    API Opportunities “APIs create a new relationship opportunity – B2D; Business to Developer, that creates direct B2C, B2B and indirect B2C relations” Source: http://asanka.abeysinghe.org/2012/02/apis-create-new-relationship-b2d.html
  • 10.
  • 11.
    WSO2’s API ManagementVision • Create APIs • WSO2 Application Server, Data Services Server and ESB • Find and subscribe/buy APIs • API Store and Governance WSO2 API • Manage, secure and protect APIs Management Platform • API Management and Gateway • Monitor and Monetize APIs • API Monitoring and Analytics • Develop, host and run API-based applications in a Platform-as-a-Service • WSO2 Stratos and Cloud Development Platform • API Cloud
  • 12.
    The API PlatformArchitecture Self-service Access API Store Front API Explorer API Back Office Key Management Monetization Engine API Governance API Gateway Load Balancer Mediation Broker Authorization and Authentication API Cloud Mobile and Web Applications API Analytics Data Store Consumer Identity Traffic Control Provider Policies Monetization Repository API Repository
  • 13.
    Business Design ofthe APIs • Know the consumer • Who will use the APIs (both developers and final end-user)? • What type of applications will use the APIs? • What business assets will be delivered? • Maintain Operational Control • What Quality of Service is expected? • Who can access the assets? • Remember Usability and Monetization • How will the API expose business assets? • How will you demonstrate business value via direct revenue, chargeback, or showback?
  • 14.
    API Ecosystem Model •From SOA lessons learned, best practices roles •API Publisher • Builds, publishes, manages, and versions API • Understand business and technical requirements • Cares about usage and scaling • Seeks feedback, ratings, usage •API Manager •Promotes and encourages consumers to adopt API •Determines usage patterns and how to best monetize asset •Monitors and secures •API Consumer •Understands the interface definition •Subscribes and connects application to API •Monitors own usage and cost basis •Provides feedback and ratings
  • 15.
    Architect’s View ofAPI Objectives API Publisher •Publish easily consumable APIs •Increase API accessibility, availability, reliability, and security •Drive API adoption by building communities and promoting APIs API Consumer •Identify API matching project requirements •Evaluate API and rapidly compose solution •Assess service level agreement and cost •Socialize project requirements with API Publisher API Manager •Meter, rate limit, and monetize investment •Promote and enforce API lifecycle best practices •Optimize API portfolio and reduce custom development •Identify usage patterns, successful providers, and business opportunity
  • 16.
    Developer’s View ofAPI Objectives API Publisher •Quickly develop and publish secure RESTful APIs •Associate service level policies and monetization rates •Promote samples, how-to-guides, and roadmaps •Evolve and version service API Consumer •Register as an API consumer •Review API documentation and match project requirements •Obtain API key, integrate with API, test API •Subscribe to API at a specific service level and pricing rate API Manager •Follow best practice API lifecycle workflow •Version API •Request API features and file issue •Automated migration across lifecycle environments (e.g. Dev/QA/Prod)
  • 17.
    Built on ProvenComponents • API Management Platform leverages WSO2 proven components: o WSO2 ESB  used as API Gateway by eBay, AAA, and others. eBay handles > 1 billion API calls/day o WSO2 Governance Registry  used by British Airways, Intermountain Healthcare, and many others o WSO2 Identity Server  used by Citigroup, Federal Home Loan Bank of SF, US Navy and others
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
  • 23.
  • 24.
  • 25.
    Questions? http://www.flickr.com/photos/oberazzi/ 25
  • 26.
  • 27.
    Follow us: http://twitter.com/#!/wso2 Follow us: Contact us: http://twitter.com/#!/wso2 http://wso2.com/contact/