WSO2Con US 2013 - Creating the API Centric Enterprise Towards a Connected Business


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • A = APISS = social AppsM = Mobile AppsW = Web AppsE = EmailI iPaaS, BPMaaS, DaaSP PaaS for APIs or SaaS
  • PaaSAmazon Beanstalk, Google App Engine, CloudBeesRUN@Cloud, WSO2 StratosA dedicated Tomcat einstance running on EC2 virtual server each web applicationGAE – Supports Java platform as a development platformStratos – Multi-tenant environment . Private jetmode is availableAs the load goes up, the platform will auto scale to support it.
  • WSO2Con US 2013 - Creating the API Centric Enterprise Towards a Connected Business

    1. 1. Creating the API Centric Enterprise: Towards a Connected Business John Mathon WSO2 VP, Product Strategy
    2. 2. BigData iPaaS / PaaS / BPMaaS / aPaaS / … SaaS applications Social Mobile Enterprise IT is exciting again Ecosystem PaaS The Cloud API EconomyBigData
    3. 3. What’s a connected business? • It’s about connecting: – – – – Internal Systems Internal People Customers Potential Customers – Partners – systems and people – Potential Partners – systems and people
    4. 4. What is a “Connected Business – How?” The way the participant prefers SaaS Application Social Apps E-mail Mobile API iPaaS / BPMaaS / PaaS
    5. 5. What Kind of Connectivity should you have? What/Who? Internal Systems Employee Partners Potential Partners Internal Systems Employees Partners Potential Partners Customers Potential Customers A=APIs S=Social M = Mobile Apps W=Web Apps E=Email I=iPaaS Customers Potential Customers
    6. 6. Imagine • You know how every asset is used, who is using it and how much they are using it, when • You know the reliability, performance, cost and benefit of every asset • You can assess the security of assets and who is allowed to see and use it, possibly when, how much, revoke it instantly when needed and remove data from devices even if the devices are turned off
    7. 7. Imagine • You can safely and smoothly retire or replace assets that aren’t being used, cost too much or represent security or other risks • You can understand dependencies both system and people involved for any asset • That you can create a virtuous cycle of innovation, benefit that increases people’s incentive to be collaborative, innovative and transparent?
    8. 8. API “Centric” starts with an “Enterprise Store” • • • • • • • A Governance Registry not just a store, scalable, secure An Asset store not just APIs Track the lifecycle of assets, subscribers, stakeholders Drag and drop directly in your development environments Re-use Internal and External assets Publish Internally or Externally – even to other stores Completely secure, Mobile enabled - revoke access even when the device is off
    9. 9. Enterprise Store A Social platform for Enterprise Assets • A social platform to enable collaboration – (Today) Comments, ratings, related assets, events and eventing, permissions and visibility by role (Future) A searchable wall for each asset put video, issues, solutions, pictures, tips, tools, best practices, statistics, performance, set up circles for selected users • Understand who can see, who uses assets, what their role is, what they do with the asset, when • Account for costs, manage, end-life unused assets, replace assets, KPI’s for assets, bill, set SLA’s, set tiers of service for all assets
    10. 10. Publish and Socialize
    11. 11. CXO Dashboard
    12. 12. Business Benefits of API Centric • Higher Re-Use – Lower Costs • Easy Ability to Re-Use and Change – Faster time to market • BigData on all assets – understand new opportunities from users of your web, mobile, APIs, PaaS, SaaS, … • Transparency – better manageability and quality • Share resources – lowers costs
    13. 13. How do you succeed with API Centric • Need a culture of transparency • Need a collaborative mindset or at least a way to segment collaborative effort from silo effort Move assets into the Store, socialize • Learn from the usage • Testing regime that will test changes in central assets against dependencies (user orientation)
    14. 14. Transparency
    15. 15. Do you believe Transparency will: • • • • Create higher trust Increase Morale Increase innovation Improve your organization • Result in bad press • Be misunderstood • Oh boy - when people find out how bad it is • Good people will suffer
    16. 16. Why be transparent? • Observation: Transparency leads to higher trust contrary to what might be supposed – transparent organizations are characterized by high loyalty and high morale • Logic: Improvement is harder if the knowledgeable and dependent people capable of fixing the problems are not aware of the problems • Fact: Nobody will re-use if they don’t know what the real problems, roadmap, objective measures of performance and usage are • Fact: Nobody will stake their career on using something if they don’t think they are getting the “real info”
    17. 17. We don’t preach … but • We think it’s going to be hard to succeed with re-use and innovative technology without transparency
    18. 18. Becoming a Connected Business – Refactor • Take a systemic approach and decompose your existing business processes, data and capabilities into services • Make all services accessible via APIs, externally and internally • Separate the API life cycle from service life cycle
    19. 19. Monitor And Analyze • • • Monitor millions of events, leveraging highly scalable and performantNoSQL database Take decisions in real time through Complex Event Processing Create dashboards for both technical and business monitoring
    20. 20. Don’t Loose Control
    21. 21. Becoming a Connected Business Part2 • • • • • • Create new services Compose new products and services Do not lose control! Build an ecosystem - socialize Learn from the usage of your products quickly Improve incrementally
    22. 22. Connected Business • You know we make it easy to do Mobile, APIs, Email, Web Apps • But what about
    23. 23. Data As a Service / DataMart • Expose Data Sources (database, files, Google Docs) as APIs using Data Services Server. • APIs are created declaratively (no coding) • Supports SOAP / REST
    24. 24. App Factory Ecosystem PaaS • • Simplest way to create, build, test, stage, deploy and operate applications External Use Cases – – – – – • Ecosystem PaaS aPaaS (Building SaaS applications) Extend API Management with a PaaS for mobile or other application development Extend SaaS Applications with a PaaS iPaaS, bpmPaaS, DaaS, … Internal Use Cases – – DevOps Internal Open Source Collaborative Development
    25. 25. PaaS is to Applications as IaaS is to Infrastructure • • • • • • • • • Low initial cost to deploy Incremental cost as your usage grows Automated deployment Management built in Self service Best Practices embedded Lifecycle built in Re-use Resource sharing 11/17/2013 26
    26. 26. App Factory is unified • API’s – Build and use APIs in the Enterprise Store – Define who can see what APIs, who can create and use what APIs at what tiers of service – Drag and Drop APIs into development • Applications – Build and Deploy multi-tenant Applications • Mobile Applications – Build Mobile Applications, deploy to employees or customers or partners favorite devices. Revoke and delete them and their data as needed, upgrade them remotely
    27. 27. Provide new ways to interact and benefit customers • • • • • • If you have a partner ecosystem you wish to improve If you have a successful SaaS application If you have a successful API or APIs If you have a mobile strategy If you want to build a SaaS application If you want to control the APIs, applications or mobile application created by customers or partners on your APIs, applications or mobile applications
    28. 28. Extend API Management with a PaaS Extend SaaS Applications with a PaaS • If you have a successful API you will want to manage the development of applications using your API with a PaaS. – Twitter probably wishes it had done so • iTunes manages their devices with a store and regulates look, feel, money generation, security • If you have a successful SaaS application like Salesforce, SAP, Workday, … you will want to have a PaaS
    29. 29. Proven Model • Numerous companies today provide custom built PaaS environments for their customers and partners today – – – – – • Salesforce Netflix Google Ebay … For companies with more regulated environments or where they want more control this is essential to do. – Twitter probably wishes they had done it – Financial companies, governments, regulated enterprises all need a controlled environment
    30. 30. Benefits You and Them • Partner Benefits – Lower cost to use your AAM’s – Easier to develop and faster to market with your AAMs or their AAMs – Built in collaborative environment to learn from others what’s best and what others can do, what they’ve learnt or done • For YOU – – – – More partners, more innovation, stickiness Control of how they use your AAM’s Control the quality of AAMs produced by your partners Understand partners usage, learn opportunities and difficulties first hand
    31. 31. Summary
    32. 32. Key Benefits of API Centric • • • • Reduce Costs and Risks Manage Assets better Make it easier to innovate, increase transparency Re-use assets to build new products and services faster
    33. 33. API Centric / Connected Business
    34. 34. Key Benefits of Connected Business • Higher integration makes it easier to offer new products and services • Providing connectivity as needed for each participant in your value chain whether internal or external means – More leverage – Stickiness / More Usage – Ability to increase interaction from existing participants and gain new partners
    35. 35. What do you need to go down this path? • WSO2 Carbon – the platform for integration and connectivity • WSO2 Private PaaS – the platform for devOps and Cloud • WSO2 Enterprise Store – the social governance platform for next generation Enterprise Application level Asset Management • WSO2 App Factory – the complete platform for building an agile development environment using API Centric and the Connected Business