I read with great interest as I encountere the same situation some time ago.
In practice (at least in my case), it worked to have the app run on separate
EOF stacks accessing different database. So , it simplified the case to
only have one instance in JavaMonitor for multi databases. However,
FWIW
We uses an setup were access is organized by groups, sub-groups and
sub-sub-groups, etc.
We have sales reps which manage channel partners, which manage clients
or schools. In the schools are more groups. These are all group
objects.
There are classes that relate to groups,
Hi Guido,
Guido Neitzer wrote:
On Sep 22, 2009, at 4:34 PM, Chuck Hill wrote:
- some increase in RAM usage due to duplicated loading of code and JVM
If you don't want to do that and are committed to doing this in one
instance, the next best way is to tag the root object with the
tenant.
Hi Lachlan,
Lachlan Deck wrote:
On 23/09/2009, at 8:46 AM, Henrique Prange wrote:
Chuck Hill wrote:
- problems / load on one tenant do not impact others
- guaranteed that one tenant will not accidently see information from
another
This last one is exactly the reason why we can't have a
Hi Cheong,
Cheong Hee (Gmail) wrote:
I read with great interest as I encountere the same situation some time
ago. In practice (at least in my case), it worked to have the app run on
separate EOF stacks accessing different database. So , it simplified
the case to only have one instance in
Hi Chuck,
Chuck Hill wrote:
Not so easy when you have more than 20 different instances (and
counting) running on JavaMonitor. :p
20 does not seem like that many to manage.
Yeah. I'm worried about the future. 100+ instances can become a problem
to manage.
Cons:
- more instances to
Hi Henrique,
This thread may be of interest:
http://lists.apple.com/archives/webobjects-dev//2007/Jul/msg00390.html
We are still using the approach described by Eugene in this thread.
On Sat, Sep 19, 2009 at 7:09 PM, Henrique Prange hpra...@gmail.com wrote:
Hi all,
Is there a way to
Hi Chuck,
Chuck Hill wrote:
The easiest, and perhaps best, way to do this is to have different
instances for each tenant. The configuration (in JavaMonitor or
elsewhere) can then specify the database.
That is our current way to deploy the application.
Pros:
- easy
Not so easy when
Hi Denis,
Thank you very much, Denis. I haven't found this thread while googling
by the subject. The Eugene e-mail has exactly what I need... Sample code. :)
Cheers,
Henrique
Denis Frolov wrote:
Hi Henrique,
This thread may be of interest:
Hi Henrique,
On Sep 22, 2009, at 3:46 PM, Henrique Prange wrote:
Hi Chuck,
Chuck Hill wrote:
The easiest, and perhaps best, way to do this is to have different
instances for each tenant. The configuration (in JavaMonitor or
elsewhere) can then specify the database.
That is our current
On Sep 22, 2009, at 4:34 PM, Chuck Hill wrote:
- some increase in RAM usage due to duplicated loading of code and
JVM
If you don't want to do that and are committed to doing this in
one instance, the next best way is to tag the root object with the
tenant. But you said separate databases,
On 23/09/2009, at 8:46 AM, Henrique Prange wrote:
Chuck Hill wrote:
- problems / load on one tenant do not impact others
- guaranteed that one tenant will not accidently see information
from another
This last one is exactly the reason why we can't have a shared
database at all.
This is
Hi; I've done two reasonably complex multi-tenant systems which are
now seven and five years in production. Both are running out of
unified models and I haven't heard of any issues around data
authorisation issues.
cheers.
I did something like this a while ago and it was actually pretty
Hi Henrique,
On Sep 19, 2009, at 8:09 AM, Henrique Prange wrote:
Hi all,
Is there a way to configure EOF to access separate databases for
each tenant in *one* application?
I'm working in an application that has a strong non-functional
requirement on multi-tenant architecture with
14 matches
Mail list logo
