hi,
I am using weblogic as my app and I came to the point where I have to
make my system redundant, scalable and so on.
So what do I do?
My thinking is that if I use EJB I should cluster a few servers, but
other people around here don't like the idea and propose the following :
1-to have a few servers running, that don't know about each
other.
2-front en those servers with a cisco local director to
provide load balancing
3-have two identical setups in case one fails
4-Any kind of data the app handles goes to the database,
(everything), so that the other servers can pick it up.
A - it seems to me that 1 is too simplistic, 2 and 3 I don't have a
problem with, and 4 stinks. I would think that if there is a lot of traffic,
the app would crawl to a halt since everything goes to the database and
nothing is cached. What do you think????
B - Now what I think is that since I use EJBs I should definetly use
clustering and not using it ,to me would mean that then the use of EJBs is
worthless and would slow the system even more since I could implement the
same solution with servlets in a more efficient way. What do you think???.
So what I would do is use EJBs with clustering
questions:
1- would you use EJBs at all if you are not planning to cluster as the
system grows ??
2- Is it realistic to say that everything goes into the database?? what
about performance??
3- would you say that I will fail if use the first setup at the top of the
email??
4- Would you say that clustering is the solution if I use EJB, in order to
provide availability, failover and the other?
Thanks
Gustavo E Tenrreiro
[EMAIL PROTECTED]
work: (650) 413-5565
cell : (408) 373-8595
home: (408) 225-7097
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
