just for sharing here is an about multi-tenant architecture on force.com / salesforce.com
https://wiki.developerforce.com/page/Multi_Tenant_Architecture We are currently customizing ofbiz to cater multi-tenant using shared DB which resulting to below process flow Use Case 1. Tenant A as the master Tenant 2. Tenant B, Tenant C as the child Tenant that has parties relationship to Tenant A Tenant A can view all data from Tenant B and Tenant C Tenant B can view its own data. Tenant C can view its own data. e.x. Product Feature (existing) Product Feature Role (new entity) and then create a view-entity joining the two tables in the screen/form, we changes all the entity calls to this new view-entity. And then we create an intermediate screen, forcing end-user to choose its "organization/tenant". And thus this partyId will pass into the view-entity. Thus, we are using the ProductFeatureRole to control the data is belong to which tenant. And, we use the party relationship to define which tenant can view whom tenant data. Thus, we heading to the direction of One ofbiz instance, one tenant(Master tenant), multiple organization (child tenant) But, having said that, IMHO, i still favor the multi instance(application and database) approach to cater multi tenant. IMHO, Because i think thats the way to go for cloud. But of course, the costing on the cloud service provider are a factor. On Thu, Feb 27, 2014 at 9:08 AM, Carlos Cruz <[email protected]>wrote: > From a business perspective, if wanting to resell OFBiz hosting, wont > the perspective of maintaining individual DB's for each client quickly > become a mega-complex undertaking with accompanying high maintenance > expences? I can only imagine trying to maintain 1,000 DB's for a small > client pool of 1,000 clients wouldn't be the easiest thing to do, so I > don't think the ecomics supports the business model of large pool of > individual DB tenants easily. > > Just my humble thoughts..... > > CC > > -----Original Message----- > From: Mike [mailto:[email protected]] > Sent: Wednesday, February 26, 2014 2:12 PM > To: user > Subject: Re: OFBiz Multi-tenancy > > Shared Database and Shared Schema initially sounds great, until you > realize what a pain it will be to do backups/restores of individual tenants. > Eventually, a tenant will mess up it's data and will ask you to restore > back to date/time. Now you are in a real pickle, unless each tenant has > it's own DB and you have a solid point-in-time DB recovery process. > Something to think about. > > > On Wed, Feb 26, 2014 at 4:45 AM, Prashant Sankhla <[email protected] > >wrote: > > > Hello OFBizers, > > > > I am evaluating a proposal for development of a SaaS application using > > OFBiz framework. As I understood from wiki page< > > https://cwiki.apache.org/confluence/display/OFBIZ/Multitenancy+support > > > > > for > > every tenant a separate data instance is created. > > The requirement for us is to be able to scale up to ten thousand > > tenants and more. Typically each tenant will have 1 to 10 users. > > > > This gives me all indication that Shared Database and Shared Schema is > > the way to go in our use case. > > > > My question to OFBiz experts is: > > > > 1. Is there any other better design to achieve the use case as stated > > above? > > 2. Is there any implementation or guideline available for such a use > > case anywhere? > > > > > > Best Regards > > Prashant > > > > -- Disclaimer : This E-mail is intended only for the use of the individual or entity named above and may contain information that is confidential. If you are not the intended recipients, please immediately notify us by return email and delete it from your system. Any unauthorised dissemination, distribution or copying of this email is strictly prohibited. Thank You.
