Enterprise Integration Zone is brought to you in partnership with:

Mitch Pronschinske is the Lead Research Analyst at DZone. Researching and compiling content for DZone's research guides is his primary job. He likes to make his own ringtones, watches cartoons/anime, enjoys card and board games, and plays the accordion. Mitch is a DZone Zone Leader and has posted 2576 posts at DZone. You can read more from them at their website. View Full User Profile

WSO2 Fights Cloud Lock-in With Stratos PaaS

06.03.2010
| 10174 views |
  • submit to reddit
This week, WSO2 launched what it is calling the first 100% open source PaaS cloud platform.  The SOA and developer platform is called WSO2 Stratos, and it is offered as a self-service, multi-tenant, cloud native, elastic runtime (based on WSO2's Eclipse RT-like Carbon framework) for private and public clouds.  

WSO2 provides free and open source SOA middleware components (ESB, App Server, etc.) on a customizable, modular framework called Carbon.  Last year, WSO2 started offering its components as cloud images, but they were not cloud native.  Stratos provides these components natively in the cloud, which means when you log into Stratos and immediately provision your own domain with the services you want via the Cloud Manager.  The components are completely self-service, elastically scalable, and comprehensively metered and monitored.   

Initial Advantages
If your organization needs an ESB, for example, they can instantly provision one on the multi-tenant architecture and let the metering and monitoring tell you what resources are being used by each tenant.  Having these services be cloud native saves memory because (unlike with the images) you don't need to allocate new VMs for each service, which cost about half a GB on each server used.



WSO2 co-founder and CTO Paul Fremantle blogged about [http://pzf.fremantle.org/2010/06/wso2-stratos-platform-as-service-for.html] Stratos, saying that unlike Force.com or Google App Engine, you have the option to run applications internally.  Stratos offers an enterprise architecture with governance, business process, integration, portals, identity management and mashups.  It also supports the common Enterprise Programming Model (Java, JAX-WS, BPEL, XSLT, XPath, WSDL, etc.).  Only Tibco Silver provides similar offerings.

No Lock-in!
WSO2 believes in the open source business model, and takes it very seriously.  One problem that Fremantle is seeing in today's cloud/software platforms is lock-in:

"Software vendors love lock-in - and Cloud vendors love it even more. So if you code to Google App Engine, you are tied into Google's identity model, Google's Bigtable, etc. If you code to force.com or vmForce - you are tied to force's infrastructure services. If you code to Tibco Silver, you are tied to Tibco. WSO2 fights this in three ways:

No code lock-in: we use standards-based coding (WAR, JAX-WS, POJO) and Stratos is 100% Apache License Open Source.
No model lock-in: we use standards-based services:
  • Identity is based on OpenID, OAuth, XACML, WS-Trust
  • Registry is based on AtomPub and REST
  • Business Process is based on BPEL, etc
No hosting lock-in: you can take you apps and data from our public PaaS and re-deploy internally or on your own virtual private cloud anytime you like."

Stratos can run on the web, Amazon VPC, or private clouds based on Ubuntu Enterprise Cloud, Eucalyptus, and others.  Support for VMware's vSphere will be coming soon.  You can test-drive WSO2 Stratos on the web right now.

Comments

Ronald Miura replied on Thu, 2010/06/03 - 2:03pm

What about persistence? The main problem with PaaS today is not the runtime. The limitations in GAE (for example) don't affect the programming model in general, just specific functions like asynchronous processing, which could be abstracted with some effort.

The big problem about PaaS vendors is persistence. Each offers a different mechanism. Some offer relational databases, others offer different [single/multi]-level-key-[value/document/record]-based datastores. Not only different APIs, but different semantics or even paradigms.

How does WSO2 solves this issue? The 'just use mine' approach? Or some abstraction (that would probably perform very poorly without very platform-specific tunning)? Or the 'we don't try to solve this' non-portable approach (which kills any usefullness of the stuff)?

Kathiravelu Pra... replied on Thu, 2011/08/04 - 6:27am in response to: Ronald Miura

Nice post Mitchell. Just found this post, when going through a few articles on Java PaaS.

Hi Ronald,

Stratos is available as a cloud enabled application platform, where you can download and set up Stratos locally as your cloud middleware platform, for your organization, where the publicly hosted Stratos (named as StratosLive, since the new release of Stratos - 1.5.1) is available for anyone to register a tenant from http://stratoslive.wso2.com/carbon.

As a Platform as a Service, you are free to use/try StratosLive, and also can easily migrate your information to your locally hosted Stratos or a data center. Persistence and hence easy migration are made possible as Stratos development has followed open standards, and also it is the WSO2 Carbon open source SOA middleware platform as a service. WSO2 Stratos is highly portable and fits any infrastructure as a service (StratosLive, the Java PaaS, has been deployed on top of Amazon's IaaS), or databases.

Pls do reply, if you have any concern or thought on this, so that we can discuss further on Stratos or the PaaS as a whole.

 

Thank you.

Regards,

Pradeeban.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.