Hi everyone.
Great list, i've read it all gleefully.
Sorry that my name ist rather ordinary.
We are working on a rather large scale Internet Site, every single page of
wich will be dynamically generated. I would be really thankful if someone
could just give us a hint if were on a plausible track or if were trying to
stop global warming by keeping the fridge open.
In the short description i will leave out the messy details about clustering
and load balancing for now. So the situation is the following:
We have HTTPServers that deliver the static content such as GIF/SWF etc. and
that pass on the requests for (our current approach) JSP/Servlets to a bunch
of AS. (Here we are currently thinking of Weblogic primarily and are also
evaluating Websphere) Are there any others that we should definitely look
into? Here we have our logic that defines what content will be displayed and
which template should be used for this, who the user is (session management)
and some system relevant stuff. Practically all our DB access is read access
so we will use stateless session beans to read data and not entity beans
(correct?).
On to the backend. We have an Oracle Database at hand which we can always
fall back on, but were currently evaluating ObjectStore and Versant as a
more efficient means of storage, since we have quite a bit of data that
pertains only to the current session we think an odbms would be a viable
option here. If anyone has tried using either of these in this context and
thinks it stinks - addEnragedComplaintsListener( me );
So >each< HTTP request means: we use some servlets in weblogic utilizing the
httpsession mechanism, access a few stateless session beans which read data
from, lets say, OStore , and occasionally we use an entity bean to write
some data.
Now the problem.
The current site which is horrid gets about 50000 >USERS< a day without the
company actually pointing anyone to it, so as this will change soon, this
number can be expected to rise to something like well... say 300000? worst
case half a million users a day on special events. I have no idea how many
hits this translates into... Now we cant tell the company buy a hundred and
fifty thousand sun servers, or something along the lines of "the site is so
sensational that even a response time of 45 seconds ist ok." We need some
cool response times. We will have quite a few servers to handle this but at
the price of a sun server its a difference wether we need 8 or 32.
I would really appreciate some comments on this, where could we do
something differently more efficiently, or is EJB the wrong way alltogehter
for this? Any suggestions that i cannot think of right now are of course
also welcome..... :-)
if the description was too general then I can elaborate....
Thanx in advance
Martin
[EMAIL PROTECTED]
Hamburg, Germany
===========================================================================
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".
