Martin Friedel wrote:
> We are working on a rather large scale Internet Site, every single page of
> which will be dynamically generated.
> ...
> 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 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.
> ...
> 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.
<Vendor>
You might go at this a couple of ways with GemStone/J. Certainly the Oracle
backend could be used directly, as with any other application server. In
the GS/J case, however, you could use the built-in persistent cache
mechanisms to make read-only data access and dynamic content generation
very efficient. By constructing a cache of backend data in GS/J, your
servlets, JSP, and/or session beans could access the data directly as Java
objects (enabled by our shared memory cache infrastructure), run their
methods to generate your per-request results, and translate those results
into HTML in your servlet, JSP, or JSP bean. All of this runtime work would
be done in Java, without communications to external servers, SQL coding, or
O/R mapping. Because frequently accessed objects would be present in shared
memory, you'd find quite good performance.
It wouldn't matter whether you perform your work from servlets, JSP beans,
or EJBs - all have access to the cache.
</vendor>
Marc San Soucie
GemStone Systems, Inc.
Beaverton, Oregon
[EMAIL PROTECTED]
===========================================================================
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".
