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.
WSO2 Roadmap and Vision
WSO2 Roadmap and Vision<br />by<br />Paul Fremantle<br />CTO and Co-Founder<br />WSO2<br />firstname.lastname@example.org <br />#pzfreo<br />
Some stuff I’d like to talk about<br /><ul><li>How our vision changes and has changed
More Roadmap<br />Carbon Studio 2.0<br />ESB Flow based Tooling<br />Productization of API management <br />BAM 2.0 (redesign for scale)<br />Registry with Cassandra storage<br />BPS support for BPMN 2.0<br />Looking at adding wider SCXML support<br />Message Broker – significant work on large scale<br />
What has changed in our vision?<br /><ul><li>Catalogue, secure, manage, monitor and govern the stuff
WSO2 and Social<br /><ul><li>Our initial Registry was designed from the start to enable Social interactions</li></ul>“SOA World session discusses how social governance brings viability to Web 2.0 for the enterprise” 2008<br /><ul><li>Carbon has OpenSocial 2.0 support built right into the heart</li></li></ul><li>“Ecosystem PaaS”<br />Tenant<br />Apps<br />Tenant<br />Apps<br />Tenant<br />Apps<br />Tenant<br />Apps<br />Industry Vertical / Ecosystem Guardian <br />Customizations / APIs<br />(e.g. Mobile, Retail, Gaming, B2B)<br />Platform As A Service<br />
Interesting ways of putting the two together</li></li></ul><li>Sugru<br />