I agree, multi-tenant databases are easy to implement with a qualifier in the
model. Here is a previous similar conversation.
http://cayenne.195.n3.nabble.com/Multi-tenancy-Implementation-td4024468.html
Ari
On 21/04/13 1:32am, Bob Harner wrote:
A quick and possibly unwelcome answer: *don't* have a different database
for each project. That is almost always a bad idea, IMHO -- completely
unscalable and ten times more work over the life of the app. Have only a
single database, possibly with sharding if needed..
Think of it this way: Google doesn't have a different database for each
Gmail user.
On Apr 20, 2013 4:40 AM, "Daniel Scheibe" <[email protected]> wrote:
All,
what would a possible scenario of running multiple isolated Cayenne
instances, actually quite the opposite of grouping multiple nodes under a
domain. Let's say i have multiple datasources all pointing to different
databases on different servers where every 'project' is completely isolated
from all others, there is no shared data between those. At first sight i
was asking myself if i should just setup and run multiple ServerRuntimes,
would this even be possible? Would this be a valid approach?
The configuration of 0..n projects should possibly be changeable at
runtime too with a higher level 'ProjectManager' that i would have to
implement to steer the runtimes.
Thanks for your thoughts!
Cheers,
Daniel
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
