From on-premise to cloud computing – WSO2 Carbon, Stratos and StratosLive

WSO2 Carbon is the world renowned middleware platform. It is an open source project with a complete and comprehensive set of features that can address all the expectations of the enterprise, from data to screen.

Here is the source code: https://svn.wso2.org/repos/wso2/trunk/carbon/

WSO2 Stratos is the open source software project, that adds cloud native attributes and features into the WSO2 Carbon middleware platform.

Here is the source code for Stratos components: https://svn.wso2.org/repos/wso2/trunk/carbon/components/stratos/

If you happen to notice, it is the same source tree. In fact, the WSO2 Carbon products and WSO2 Stratos services are built using the same pom, based on the same set of components.

For e.g. WSO2 Application Server product and service are both built using the maven pom: https://svn.wso2.org/repos/wso2/trunk/carbon/products/as/pom.xml

WSO2 StratosLive is the public cloud operated by WSO2, and provides a platform as a service (PaaS), based on WSO2 Stratos.

carbon-stratos-platofrm

WSO2 Carbon middleware products can be deployed on-premise on native hardware or on a cloud environment on virtual machines.

The same WSO2 Carbon products are made available as cloud services, quipped with the cloud native capabilities, with WSO2 Stratos. WSO2 Stratos cloud middleware services can be deployed either on a private cloud operate by an your won organization or on a public cloud operated by a cloud service provider, such as Amazon EC2. With WSO2 StratosLive, you can enjoy the luxury of using all the WSO2 Carbon middleware products on the public cloud as a PaaS, deployed and operated by WSO2.

One of the key values of the use of WSO2 platform for your enterprise solutions is the ease with which you can transition and operate in a hybrid mode. This is where the real value of the same code base comes. The benefit to the user is the fact that the same artifact can be delayed on premise, on the private cloud as well as on public cloud. Zero code changes on the part of the user when going from on premise to cloud or from cloud to on premise. Because it is the same battle tested product, that is available on the cloud as a service, not something new or alien.  This is one of the fundamental barriers to adopt cloud computing, namely transition, that WSO2 has addressed and solved,  with its unique design of the platform.

And if you relate this to the lifecycle and governance aspects, now you can leverage the capabilities of the platform to manage develop, test, staging and production states of your solution artifacts with ease and with less management and administration costs with a hybrid setup. For example,

  • Developers can try out and PoC stuff on the public cloud, using a tenant on StratosLive
  • Developers can develop and test the artifacts on the WSO2 Carbon product instance, say WSO2 ESB, running in their laptops or desktops
  • Then deploy the same artifact, to a private cloud, running the WSO2 Stratos service, WSO2 ESB as a service, where the test environment is setup
  • Testers can test the artifact on the test setup running on the private cloud setup
  • Once QA passes, the same artifact can be deployed to the staging environment, running on a public cloud, operated by the same organization
  • Once acceptance tests pass, the same artifact can be deployed to the production environment, running on the public cloud, operated by the same organization on StratosLive
Technorati Tags: ,
BuzzNet Tags:

Comments