Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

WSO2 Integration Platform: Vision and Roadmap

To view recording of the webinar please use below URL:

http://wso2.com/library/webinars/2015/08/wso2-integration-platform-vision-and-roadmap/


In this webinar, John Mathon, vice president of enterprise evangelism at WSO2, and Senaka Fernando, solutions architect at WSO2, will talk to you about

WSO2’s vision in becoming the world’s #1 middleware platform provider
Its roadmap - introducing some of the exciting new products that are lined up for release in the next few months
Our experiences with some of the world’s leading enterprises that are adopting the WSO2 platform and why they chose WSO2 over any other vendor

WSO2 Integration Platform: Vision and Roadmap

  1. 1. Envisioning the Future Enterprise Platform for Mobile, Social, Big Data, Cloud, APIs, I(I)oT, Open Source By John Mathon WSO2, VP Enterprise Evangelism and Product Strategy
  2. 2. About the Author —  10 patents, publish / subscribe, multipath low latency high reliability messaging, Content management in file systems, peer to peer messaging over WAN… others —  founder and CTO of TIBCO —  Twitter: @john_mathon —  Blog: CloudRamblings johnmathon.wordpress.com
  3. 3. Existing Products —  API Management – leading full featured open source —  Orchestration for Enterprise, Cloud, IIoT or IoT – ESB, MB, BPS, Rules —  Integration with old and new – ESB, Adapters, DSS, AS —  Data – DSS, BAM, CEP —  Security – IM – OPEN_ID, OAUTH2, … —  And more
  4. 4. New Products —  PaaS = DevOps Automation and Operations Scalability —  Ecosystem PaaS = Multi-tenant full lifecycle Development environment in a box to provide PaaS to YOUR customers —  Enterprise Store = Combined API, App, IoT, Web App that is social and enables widescale reuse of all Enterprise Assets —  App Management = Manage Applications in a Virtual / Cloud Hybrid Environment —  Device Management = Manage Mobile, IIoT and IoT devices, including their APIs, services, security, maintenance, data in one place —  Machine Learning = Apply state of the art technology to leverage BigData —  CEP and BAM = Bigdata KPIs, analytics, real-time and batch as well as high scalability
  5. 5. Unprecedented Change
  6. 6. Cloud Companies changed the model —  Twitter, Google, Yahoo, Facebook, Netflix, —  Continuous frequent deployment —  open source development —  Map/reduce, hadoop, Kafka, Clojure, Ruby, Chaos Monkey, API Management —  Chef, Puppet, Cassandra, Mongodb, OpenStack, Wso2, Cloud Foundry, Scala, Spring, Rails, Docker, KVS, Phonegap, html5, firefox, chrome —  Unprecedented scale : The billion user club —  Google 3+ billion users, Facebook 1+Billion users, Yahoo 2+billion users, Twitter – billion messages/day, Ebay 5 billion transactions/day, Amazon cloud division growing at 136% annually
  7. 7. Open Source Black Duck Survey —  2014 80% of respondents say code quality vs proprietary why they chose open source software —  In 2007 80% rank cost as primary driver —  2014 80% said access to source code important —  2014 OSS Attracts and retains talent —  Open Source projects doubling every 15 months —  Companies are realizing Proprietary Enterprise License companies are not necessarily aligned with your interests —  Product Lifecycle tied to License Fees —  Not amenable to open source projects (many of which are critical) —  big upfront commitments not consistent with ‘aaS’ models —  Not on the leading edge anymore
  8. 8. Platform 3 is About: —  Much higher Productivity —  Faster code writing / Polyglot model —  Reuse APIs, Open Source and Containers —  Standardized tools and Continuous Integration, testing and deployment —  PaaS / DevOps automation —  Intimacy / Connectivity to Customers —  APIs, Mobile Apps, IoT, Web Apps, PaaS —  BigData to learn and act —  Increased Innovation Capability —  Open Source, Cloud economics, Cloud Services and reuse of APIs, Containers —  Continuous Deployment —  High Scalability —  Scale when demand hits to billions
  9. 9. Key Elements of Platform 3 —  Cloud native multi-tenancy —  Open Source —  APIs —  Mobile —  Social API, App, Web Store —  Bigdata —  Event Driven Architecture publish/subscribe IoT —  PaaS/Devops Containers, PaaS —  Continuous testing, integration, deployment —  Automated scalability —  New security protocols —  Internet of Things Gartner defines: social interaction, mobility, cloud, and information IDC: 3rd Platform for IT growth and innovation, built on mobile devices, cloud services, social technologies, and big data Wikipedia:  mobile computing, social media,cloud computing, and big data. The Internet of Things is sometimes included.
  10. 10. Reuse pandemic —  100 billion API calls/minute in the cloud says it all —  APIs (microServices) are the new center of reuse —  Apps use dozens of external services for —  Payment, social, storage, AI, GPS, Locations, —  Things, financial, logistics, lookups, —  No interesting app without APIs —  Open Source —  Containers – Docker —  Devices – IIoT and IoT
  11. 11. Network Effect APIs Exponentially Increasing Intelligence and Value Route Planning Voice and SMS Services Ratings Social Services Game Engines Relationship Services Payment Services Geo-GPS Services Location Services Deep Learning AI Services Data and BigData Services iPaaS , PaaS Calendar Services IoT Integratio n Financial Services Security Services Logging Services Analytic Services Content Services Government Svcs News ServicesSensors
  12. 12. Enterprise Store – Socialize for Reuse
  13. 13. First Step to Platform 3 API Management —  Scalable API Delivery —  API socialization and reuse —  Lifecycle management —  Usage Monitoring and Throttling —  Security —  External and/or internal services managed —  Microservices
  14. 14. Enterprise Refactoring Step 1 —  Take existing applications and services and break them into APIs that can be consumed easily Partners Apps and Services Customer Apps and Services
  15. 15. IoT  Markets  -­‐  Truly  Enormous  
  16. 16. Network Effect – Increasing Devices, Services Exponentially Increasing Value Smartphone1 In a car Smartphone2 In a restaurant Waze Uber Yelp Medical Monitor Service Smartphone4 On the street Smartphone3 In a taxi Tesla Glucose Monitor Drone GPS Emergency Vehicle Searc h
  17. 17. BigData A big part of the new Platform —  Information is knowledge (Google proves that) —  You can create automation after the fact —  Put automation in later instead of burdening real- time processing —  More agile —  Learn about usage —  Learn about your customers —  Big Data Makes you look smart —  Big Data gives you agility
  18. 18. BigData  Lambda  Architecture   Best  Prac>ce  /  Best  of  both  worlds   http://srinathsview.blogspot.co.uk/2014/03/ implementing-bigdata-lambda.html
  19. 19. PaaS is “aaS” for Services and Applications Development (see blog below) —  Low Initial Cost to Deploy —  Incremental Cost as you use or develop more —  Automated Deployment —  Management Built-In —  Best Practices baked in —  Self-Service —  Lifecycle Managed —  Reuse —  Resource Sharing johnmathon.wordpress.com CloudRamblings – A simple guide to Cloud Computing
  20. 20. © WSO2 2014 PaaS : A critical part of P3.0 Bottom Line: Faster Time to Market Before - software development is costly, risky and slow process —  Do tests on early versions of software to determine loads from customers —  Plan demand expectation and hardware required —  Acquire hardware and networking equipment for a time period including additional hardware for failures and expected peak periods —  Find space for hardware, plan network integration plan, rule changes in switches, routers, update configuration management, outages for upgrades and changes —  Test hardware and network with software to insure it works —  Understand failure modes, when to scale, runbooks for different scenarios, train people in operation and what to do in different scenarios. Write scripts to detect scenarios and provide needed information in failures. —  Write or acquire management tools, put in instrumentation in hardware. —  Plan for upgrade strategies, outages and SLA measurements, backup policies. —  Beta customers —  Go Live Now – cheaper, faster, less risky —  Choose IaaS vendor —  Choose PaaS platform —  Write some runbooks for different scenarios, train people in PaaS operation —  Deploy software —  Beta customers —  Go live 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Time Cost Time Cost Development Test/Deployment Operations $$$$$$$$$$$$$$$$$$$$$$$ SAVED SAVED!
  21. 21. Hybrid Capability is important —  Change cloud vendors based on: —  Security —  Cost —  Zone Coverage —  Performance Problems —  Vendor instability —  Or any reason that may occur —  Use Multiple Clouds —  Have on premise hardware as well as public —  Burst on demand —  Run certain services in some clouds that perform better —  Run some tenants in some regions on different clouds —  Run production, test, demo, staging … in different clouds Some Vendors claim Hybrid meaning: not different types of clouds. Seriously restricts choices
  22. 22. Polyglot – pluggable componentized
  23. 23. Con>nuous  Integra>on,  Test,  Deployment   http://wso2.com/whitepapers/the-path-to-responsive-it/
  24. 24. “Cloud native” —  Ability to develop and deploy in the cloud —  The Development Platform itself runs in the cloud or on a cloud infrastructure —  Integrated with other Cloud Native Components —  components that work in the cloud as services —  Continuous integration, test, deployment – high iterations dramatically improves productivity —  Multi-tenancy throughout —  Cloud Scalability
  25. 25.
  26. 26. IoT
  27. 27. Mobile / IIoT Evolution – 3 Use Cases! —  For the Factory / Enterprise —  Cost Reduction / Improved Efficiency / Automation —  For the Employees —  Productivity of Employees —  For the Customer —  Connected Business —  New Interaction Paradigms —  Increase Stickiness
  28. 28. UI IOT Reference Architecture Device API MgtDev Mgt Service Bus BPMBigData Long Term Analysis Activity Mgt Cloud CEP Cloud Orchestration/Integration Commu nication Prov ider OS Application ESB, Security OS ESB, IM, PEP Data Infrastructure Hub Orchestration Integration Rules Engine Data Dev Mgt Rules Engine User Dashboard IoT Mgt Dashboard
  29. 29. Mobility /Device Management —  Security —  Authentication, Entitlement, Device Wipe, Tamper Detection, GeoFences —  Data Management —  Data at Rest and in Motion – security, allocation, backup —  API Management —  Device Class and Grouping to manage groups - scale —  Connected Device Management Framework —  Standards in IIoT and IoT don’t dominate yet (OMA LWM2M) —  Legacy devices exist in abundance
  30. 30. Ecosystem PaaS – Taking Platform3 to the next level
  31. 31. Boeing  Digital  Airline  
  32. 32. This is the way you build modern disruptive solutions
  33. 33. Connected Car API Mgt Dev MgtCust Svc Service Bus Design BPM BigDat a Long Term Analysis Activity Mgt Service Bus Polling LoggingEvents Brake sBrakes BrakesBrakes Console Phone Watch 3rd Party App / Device 3rd Party App / Device 3rd Party App / Device Brakes Hi Priority Planning Lo Priority Apps Cell Ven Cloud CEP - Service
  34. 34. ConnectedConstruction API MgtDev Mgt Cust Svc Service Bus Design BPM BigDat a Long Term Analysis Activity Mgt Phone Vehicles Tools Hi Priority Planning Lo Priority Cloud CEP Building Sites Vehicles Vehicles Phone Phone Tools Tools Tools Data Gather Device Data Gather Devices Wharehouse Wharehouses Tools Data Gather Device Contractors Design Contractor Planning Tool Connected Construction
  35. 35. 
 
 Connected-Health Reference Architecture
  36. 36. Health Enrollment –Insurance State or HMO Mediation /ESB DSS to RDB Patient Data Patient Web Application Patient Data Sources Message Broker Queues Activity Monitor Activity Logs Complex Event Processor Patient Mobile Application Busine ss Proces s App Serve r API Management Patient Medical Records Patient Data Sources Patient Data Sources
  37. 37. Online Sales Mediation /ESB DSS to RDB Inventory SKU / UPCs Pricing Consumer Web App Partner / OEM Message Broker Queues Activity Monitor Activity Logs Complex Event Processor Consumer Mobile App Busine ss Proces s App Serve r Shipping API Management
  38. 38. EDA Architecture: Ufer Taxis Uber User App Uber Driver App Meetup Mobile App United Airline Mobile App Mediation /ESB Business Processe s DSS to RDB Message Broker Payments Square / Zuora …Activity Monitor DSS Big Data Activity Log API and App Store Analytics Peak Demand Pricing Dispute Handling City Configuration Reserve Service Monitor Service Driver Onboard Driver Rating Customer Onboard Driver Interaction Driver Selection Driver Payments Customer Payments Avail Query
  39. 39. Quick WSO2 Commercial —  8 years Apache and Open Source Contributor —  … from the past – Axis2, Synapse and contributors on 20 other Apache Projects —  All wso2 software is 100% open source not enterprise licensed in any way (Apache licensed) —  Contributed Stratos as Cloud PaaS layer —  True polyglot, hybrid PaaS —  Contributors WSO2, Indiana University, Citrix, EngineYard, Cisco, NASA, SunGaurd, Georgia Tech, … —  Also have an open source cloud Ecosystem PaaS —  App Factory —  WSO2 will also offer Cloud Services based on all our open source tools in 2014/2015
  40. 40. Glue for NEW and OLD technology Cassandra/ Hbase/ Mongo Social API/ App Store API Management IoT
  41. 41. Forrester Systems of Systems We do all this 

  42. 42. One Stop Shop for Platform 3 API Management Integration Open Source Mobile Enterprise Store Big Data PaaS / DevOps I(I)oT Ecosystem PaaS Security WSO2 RedHat Mule Pivotal
  43. 43. What’s different about WSO2? WSO2 Carbon consists of 190+ individual OSGi bundles (components) 20+ individual products (ESB, CEP, BAM, Bigdata, API Mgt, PaaS, Security, User Experience, Dev and App Mgt for Mobile and IoT, Integration, Bus Process, Enterprise Store, Governance, PaaS and more) Use as little or as much
  44. 44. All Components designed to the same: 1.  Multi-tenancy throughout 2.  Scalable distributed Cloud Native 3.  Admin, Logging, Governance 4.  HA/DR, APIs, Configuration, 5.  Run time management, Runbooks 6.  Deployment across all components 7.  Everything uses everything else
  45. 45. More Information —  John Mathon john@wso2.com —  Twitter Feed: @john_mathon —  Blog: johnmathon.wordpress.com —  Cloud: wso2.com/cloud —  Download: wso2.com —  App Factory Signon: https:// cloudpreview.wso2.com/
  46. 46. WSO2 Integration Platform: Vision and Roadmap
  Case-Studies   Senaka Fernando Solutions Architect, WSO2 UK
  47. 47. CASE  STUDIES  -­‐  AAA   Scalable  message  gateway  for  mobile  buying  app   @senaka  #wso2  
  48. 48. Products Case  Studies  -­‐  AAA   Challenge - Necessity to aggregate services to minimize iPhone interactions with backend services. - Expose multiple AAA internal data stores as services. - Ability to present REST/JSON APIs for a variety of backend services using different message formats and transports. - Ability to monitor gateway transactions and generate statistical data. Solution - Created APIs and composite services to homogenize the access to AAA services and data. - Very solid/scalable architecture: backend services have evolved without affecting the UI. Customer Scalable integration platform connecting geographically dispersed multiple data centers. @senaka  #wso2  
  49. 49. CASE  STUDIES  -­‐  BARCLAYCARD   Performance  and  Backend  Service  Op>miza>on   @senaka  #wso2  
  50. 50. Case  Studies  -­‐  Barclaycard   Challenge - The company has to accommodate applications and services relying on SOAP, REST, Android and Apple iOS mobile operating systems, Voice XML, and OFX, along with many different APIs. - Core Domain Services are hosted in many locations and pull data from data sources and different vendors. - The solution must integrate systems across 10 distinctive environments. Solution - A mobile app connects via REST to the ESB, and behind the scenes they orchestrate to many different systems. - With the WSO2 ESB, BarclaycardUS can have its aggregators support the OFX standard used by banks and boost performance. - BarclaycardUS plans to integrate the WSO2 Identity Server into its system to implement OAuth for RESTful services, which will be important for mobile applications. - Other platforms (3 commercial and 4 open source) they looked at didn’t have all of this, and WSO2 was very complete and robust and supported all the modern protocols, which was a big advantage. Products Customer With partnerships that include over 60 best-in-class companies and brands, BarclaycardUS is dedicated to making the purchasing experience simple and rewarding. @senaka  #wso2  
  51. 51. CASE  STUDIES  -­‐  BOEING   A  PaaS  solu>on  to  reshape  the  way  in  client  engagement   @senaka  #wso2  
  52. 52. Products Case  Studies  -­‐  Boeing   Challenge - Help airlines convert all the silo, non-standard data into common data formats that can be shared in a variety of ways - Ability to interface with a wide set of Legacy, stove-pipe data and applications. - A platform that can scale under high volumes of data whilst supporting real time performance optimizations. Solution - A platform that can create supporting profitability through integration between airline and OEM data - A solution based on Open architecture and modular design - Reusable app services and a platform to leverage analytics to improve operations - Unified user experience across distinct functional modules (i.e. Fleet, Material services. ) - Highly extensible architecture capable of driving strategy, people, process and tools. Customer The Boeing Edge ; a PaaS solution to reshape the way Boeing connects with its customers @senaka  #wso2  
  53. 53. CASE  STUDIES  -­‐  CONCUR   Corporate  Repor>ng  PlaMorm  for  smarter  use  of  employee  >me  and  resources   @senaka  #wso2  
  54. 54. Products Case  Studies  -­‐  Concur   Challenge - Concur provides employee expense management solutions to 1000s of companies worldwide. - Consolidating all of this information and developing reports out of massive amounts of data was a painfully manual process for Concur employees. - Large amounts of server resources were required to combine data from multiple data sources. - This resulted in a great deal of costs for Concur as a business. Solution - WSO2 ESB made service integration straightforward. 3 weeks of work was now covered in less than 3 hours. - WSO2 Application Server and WSO2 Data Services Server combines information across multiple enterprise systems and data bases into a set of very well organized SOA services. - The Governance Registry helps streamline development and provides governance for the whole deployment. - With WSO2, Concur automated many tedious tasks and improved efficiency of their overall processes. The success of Concur is strongly reliant on the WSO2 platform. Customer Corporate Reporting Platform for smarter use of employee time and resources. @senaka  #wso2  
  55. 55. CASE  STUDIES  –  SPECTRUM  HEALTH   Security  and  policy  gateway  for  enterprise  applica>ons   @senaka  #wso2  
  56. 56. Products Case  Studies  -­‐  Spectrum  Health   Challenge - Application of HIPAA security policy enforcements defined for the US healthcare sector. - A scalable security model with the ability to govern enterprise trust between participating entities. - Ability to provide enterprise level authorization for heterogeneous components. Solution - Provisioning Service Provider (PSP) to provision user attributes across multiple, heterogeneous user stores - XACML Policy Administration Point / Policy Decision Point leveraged by a variety of enterprise applications and platform entities (i.e. IIS/WCF services, JBoss EAP) - Platform agnostic single sign on through OpenID/SAML2 Customer Standards driven Security and Policy gateway for enterprise applications @senaka  #wso2  

×