Hi Lakmal, But, when we take the core components of Stratos, there is no PaaS behaviour OOTB, correct? i.e. Without any cartridges, Stratos is just a PaaS framework. We provide those community cartridges to allow users to quickly build a PaaS.
So, IMV, it is not correct to say that it is a PaaS. This is my understanding. Regards, Amila. On Sat, May 17, 2014 at 3:09 PM, Lakmal Warusawithana <lak...@wso2.com>wrote: > > Hi Chris, > > > On Sat, May 17, 2014 at 11:44 AM, chris snow <chsnow...@gmail.com> wrote: > >> We describe Stratos as a "PaaS framework" on which a PaaS can be >> built. However, if an adopter of Stratos only needed to deploy PHP, >> MySQL or Java WAR based applications, then in this case can Stratos >> also be considered a PaaS? >> >> Do we need to modify our definition of Stratos? >> > > I agree, Stratos can consider as a PaaS framework and also a PaaS. > Originally Stratos building features that any one can build there own PaaS > with creating cartridges. But with the pre build community cartridges, it > also can consider as a complete PaaS. > > -- > Lakmal Warusawithana > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
