WSO2 Roadmap and Vision
•Download as PPTX, PDF•
2 likes•2,004 views
The document provides an overview of WSO2's roadmap and vision from the perspective of the CTO. It discusses how WSO2's original vision of being lean, platform-based, and open source has remained consistent while certain aspects have improved or expanded. The roadmap highlights major enhancements to products like the ESB, integration of Stratos innovations back into Carbon, and a focus on areas like big data, cloud computing, and mobile/social applications. It envisions WSO2 becoming an "Ecosystem PaaS" and discusses approaches to application development using a unified JavaScript model.
![Some stuff I’d like to talk about ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
What's hot
What's hot (20)
Similar to WSO2 Roadmap and Vision
Similar to WSO2 Roadmap and Vision (20)
More from WSO2
More from WSO2 (20)
Recently uploaded
Recently uploaded (20)
WSO2 Roadmap and Vision
- 1. WSO2 Roadmap and Vision by Paul Fremantle CTO and Co-Founder WSO2 paul@wso2.com #pzfreo
- 3. What remains the same?
- 5. Where we have come from:
- 6. what is new since WSO2Con2010
- 7. Themes for the future
- 10. What you see coming in your roadmaps?
- 11. Where do you go to look for inspiration for the future?
- 12. Ongoing discussion and participation
- 13. In the corridors at WSO2Cons
- 18. Encapsulated by “not J2EE / build from ground up”
- 19. Platform
- 20. Not just one product but three based on the same core runtime
- 21. Open Source and Open Standards
- 22. 100% Apache License from Day One
- 26. © WSO2 2011 Carbon Studio
- 27. Message Broker and CEP Server
- 28. Major Enhancements ESB Templates ESB Message Stores Relay Transport SCXML Governance Lifecycle HL7 and SAP support Built in Transaction Manager DSS Distributed Transactions OAuth support Registry Extensions Registry Performance Kerberos Major XACML updates Tomcat 7 Custom BAM reports cAppDeployment SAML2 within Carbon/Stratos
- 33. Billing / Metering / Throttling
- 34. Logging as a Service
- 35. Local Transport
- 39. Distributed Cache (in Carbon 3.2)
- 40. WSO2 Elastic Load Balancer (sorta alpha)
- 41. Metering and Billing as a Product / Service (future)
- 42. Centralized Logging (available as a services offering)
- 45. SLA Management with WSO2 Carbon
- 46. More Roadmap Carbon Studio 2.0 ESB Flow based Tooling Productization of API management BAM 2.0 (redesign for scale) Registry with Cassandra storage BPS support for BPMN 2.0 Looking at adding wider SCXML support Message Broker – significant work on large scale
- 50. A big appreciation of Cloud
- 51. Cloud Native
- 53. Data, Big Data and Analysis
- 56. Complexity We expect to dig into every detail We expect to correlate diverse events and data We expect to look at the world from new angles
- 58. Highly scalable / Dynamically scalable
- 59. NoSQL model
- 60. Merge of Amazon Dynamo / Google Bigtable
- 61. Infinispan
- 63. Apache HDFS (in progress)
- 64. Highly scalable / Dynamically scalable
- 65. Filesystem model
- 66. Apache Hadoop (in progress)
- 70. Canappi Invokes Stratos Data Service to store answers
- 71. Canappi DSL layout startTheSurvey { button startSurvey (44, 42,232, 205) { Bordered ; action startSurvey navigate to answerViews ; } image instructions (20, 275,280, 165) { } } main wso2 { splashscreen 'scansurvey.png' ; navigationBar ; start startSurveyView ; menu { startSurveyView , aboutUsView , twitterView , locationView } data { Response } }
- 72. Mobile App created from a single DSL file All WSO2 Office Locations stored in a data service This is HTML WSO2 Twitter Feed
- 75. Gartner Reference Model for Platform as a Service SaaS Applications PaaS Service Offerings Integrated PaaS Application Modeling, Design, Development, Maintenance, Life Cycle Management Business Process Management Platform Cloud Database Platform User Experience Platform Integrated PaaS Platform Management, Monitoring, Governance, Provisioning Application Platform Integration Platform Other WSO2 StratosAppServer WSO2 Stratos ESB Message Broker WSO2 Stratos BPS MySQL Cassandara WSO2 Stratos Gadget Server WSO2 Stratos CEP PaaS Technology Core Cloud Value Foundation (Shared Resources, Multitenancy, Self-Service, Elasticity, Real-Time Versioning, Metadata Management, Subscription/Use Billing) PaaS WSO2 Stratos Controller BAM Governance Registry WSO2 Carbon Studio WSO2 Stratos Governance Stratos Controller, OSGi/Carbon App, Governance Registry, Stratos Billing, Stratos Elastic Load Balancing Cloud Performance Foundation (In-Memory Computing, Grid/Massive Scale, Auto-Scaling, SLA Enforcement, Use Tracking, High Availability, Security, Data Integrity, Parallel Processing) WSO2 Stratos Cache, HDFS (future), Stratos Load Balancer, WSO2 Stratos Identity, Stratos Metering System Infrastructure or System Infrastructure Services (IaaS) IaaS Hardware
- 81. JSSP
- 83. Integration with existing stuff – Mashup Host Objects and XML
- 85. Deployment Synchronizer with SVN
- 86. Working on integration SVN / Github with Stratos/StratosLive for Deployment
- 87. SVN-as-a-Service
- 88. Soon
- 89. Better integration from SVN + Git into Registry
- 90. Future
- 91. Full lifecycle development in Stratos
Editor's Notes
- Platform as a service is middleware "in the sky." Although offered as a service, its functional role remains the role of the middleware — platform, integration or other middleware type. Because there are different types of middleware offerings (application servers, integration brokers [ESBs], business process management suites [BPMSs], portal products, messaging products, etc.), each can also be delivered as a service. In some cases, these middleware services are delivered stand-alone as specialized PaaS services (StormMQ is a specialist messaging service). More often, the same cloud service provider offers multiple middleware services to meet the requirements of real-world projects (force.com includes services of a DBMS, an application server and an application development tool). Over time, most PaaS providers will aim to deliver a growing set of middleware functions. To be implemented as a cloud service, a PaaS service must not only deliver its middleware functionality, but also possess the features that make it cloud-worthy (the cloud performance foundation) and cloud-enabled (cloud behavior foundation). The cloud performance foundation is responsible for scalability and availability to match the potential demand of the global cloud user base. The cloud behavior foundation delivers resource sharing, multitenancy, elasticity, self-service and other characteristics expected of a cloud service. The common, shared development and management environments complete the picture of a well-designed PaaS platform, whether it offers only a few middleware services or is a comprehensive end-to-end PaaS.