Hi all,

Thank you for submitting links to documents related to the subject.

Of course, for each the criteria might vary and weigh differently, and the
options available in current feature set of OFBiz are limited.

But in whole, the cost of operations are key. These cost of operations not
only include the hardware and software cost, but also the effort of
maintaining the environment. While setting up a new tenant is easy, and
maintaining the happy flow (uptime and backup), the crucial factors in this
are the performance of the persistence engine and recovery cost in case of
unexpected data loss.
As many (on the internet) seem to be agreeing on the recovery cost in the
case of a shared database-shared schema approach can be expected to be high
due to the intricacies of the beast as opposed to a 'separate
database-separate schema' setup.

Yes, multiple databases might lead to a performance overhead and higher
maintenance cost, but a side-by-side comparison of the various aspects of
each approach (separate db-separate schema vs shared db-separate schema vs
shared db-shared schema) is something that would surely help in assessing
what would be the best approach in various scenarios.

If that would be available, then a sound roadmap could be devised for this
subject.

Regards,


Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

Reply via email to