Hi Chris, Please see my comments inline,
On Thu, Jan 16, 2014 at 1:21 AM, chris snow <[email protected]> wrote: > In the Stratos Developer Guide [1], I've captured that Stratos is a > 'framework' for building a PaaS. I would like to flesh out that statement > a little more, so I have some questions: > > Who could benefit from adopting Stratos? How do they benefit? For > example: > > Could a tiny startup company benefit from using Stratos to manage scaling > of a single cloud based application? > Its depends. If the cloud application need more scalability, and when it come to scale, their devOps team need to do lot of work. Stratos mainly help devOps to monitor and manage the infrastructure and resources need for scaling. If the cloud app does not require this all, no need to adopt to Stratos. > > Or, is Stratos only really of interest to large organisations that are > building full featured PaaS applications (e.g. IT providers)? > Yes, if the large organizations want to deploy complex cloud application (may be polyglot) and require on demanding scaling, then Stratos is natural fit. And if cloud app need SLA and maintain several nines availability, Stratos will good fit. > > I'm trying to get a feel for when Stratos becomes a viable solution for a > company to manage their apps. How does a company make the decision that > Stratos is the right framework for them? > > Many thanks, > > Chris > > > [1] > https://docs.google.com/document/d/1GiEsqVbqhp0rBqf6LhpNqB57TVxIApNg9o1Sk0zI9Oo > -- Lakmal Warusawithana Software Architect; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
