Critical path--
one website URL and least amount of Customization is multi-tenant.
Manual setup of each client by you,
so no setup by client;
no individual themes (look and feel) or logos; and
Adding to the Help Doc system would be the same for both.
this is also assuming you have sufficient resources to provide the
individual DB for Multi-tenant.
Note there may still be coding based on usage to complete features.
frank sent the following on 9/13/2010 9:54 PM:
Hi BJ,
Thanks for fronting some alternatives. Closing the loop then on your initial
suggestion (i.e. “One website, many stores - is it possible”). Assuming I
take a critical path approach (in context of the features that I am after)
to my implementation which could be limited to tenant level data separation
only (i.e. excludes any cosmetic type areas such as logos and only involves
tenants wanting to act, generate and report on their respective data aka
invoicing appreciating ‘some’ tenant level configuration in context of
taxation etc.) then would the “One website, many stores - is it possible?”
approach provide the least impact to my particular problem? Or based on the
additional info that I provided can I assume a multi DB approach would be
the only way to go?
Thanks again guys; much appreciated
frank
