On Tue, Jul 16, 2013 at 6:34 PM, Shiroshica Kulatilake <[email protected]>wrote:
> Hi, > > Apparently having to find a way to make non multi-tenanted products to > work in a multi-tenanted environment is a situation that has been come > across before. > > IBM has had to do this and there are multi-tenanting > patterns<http://www.ibm.com/developerworks/cloud/library/cl-tenantconversion/>that > can be followed. > > Some of these methods are having a shared user store and operational > database thus achieving the shared database model; having tenant specific > reports and logs etc.. > > What we are doing in appfactory for each of the ecosystems may already > fall into one of these patterns. For those cases where we are still looking > for a solution, viewing the problem from this aspect might shed some light. > The different models of multi-tenancy and through that seeing which level > can be shared within a given non MT'd tool is also a point to consider. > Through this we may have a label to how we multi-tenanted products X, Y and > Z. > GitBlit - Shared Application Jenkins - Shred Middleware(according to the article) - But I would call it multi-tenancy coming from the PaaS thanks, dimuthu > WDYT ? > > Thank you, > Shiro > nkins slaves [4][5]. We need to figure out a scheme on how to do this. > > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
