Doug has hit the nail on the head. EJB is appropriate for high volume
transactional sites like an electronic trading site, but for sites that provide
read-only access to product catalogs or primarly textual material (documents,
articles, etc..) with no transactional requirements, Servlets and JSP is a
better option. You should use EJB to handle purchases and transactions on these
types of sites, but not for perusing the content.
--
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
http://www.EjbNow.com
EJB FAQ
http://www.jguru.com/faq/EJB
"Bechtold, Douglas" wrote:
> I hate to speak for Richard, but I think his point is that for read-only
> queries that are basically transaction-free that EJB is perhaps more
> overhead than is needed. I am working on exactly such a system where we are
> considering using Servlets for queries that are for read-only purposes and
> EJB for updates. If the query is for reading / writing, then the "overhead"
> that EJB comes with is not an issue because of all of the other benefits
> that come with EJB.
>
> DB
>
> -----Original Message-----
> From: Frank D. Greco [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 24, 2000 9:26 AM
> To: [EMAIL PROTECTED]
> Subject: When to Use EJB? (was: Session EJBs vs. Java Objects)
>
> >Ahi Satapathy wrote:
> >> So when EJB should be used ? what should be the factor one should
> consider
> >> before going to implement something with EJB ? If the site is not
> >> transactional, has no authorization security needs, and is read only,
> should
> >> one go for simple Java Objects and use Servlets with direct JDBC access
> ??
>
> At 05:13 PM 2/20/00 -0600, Richard Monson-Haefel wrote:
> >In a word, "maybe". You need an experienced architect (consult your
> >physician) to review your system and make a recommendation. Most
> >high volume sites (Amazon, eToys, et.) that have a lot of read only
>
> High volume as in number of concurrent visitors or number of
> transactions? Or high volume as in page throughput or http (or
> socket) throughput?
>
> >navigation and no transaction needs for the reads, should be implemented
> >with something other then EJB - I like servlets. BUT, the purchasing
>
> Theoretically EJB can be used for high-volume sites like an
> electronic
> trading system. Architecturally, as part of an App Server product,
> EJB
> should not be fundamentally slower than Servlet/JDBC/JavaClasses.
> The
> vendor app server product should be able to scale much better than a
> home-grown solution. If the home-grown solution is superior... then
> I
> want to get in on the IPO... ;)
>
> >of goods and services on these sites should be implemented with EJB via
> Servlets.
>
> Actually, are there 'rules of the road' for this stuff? What are
> the
> heuristics for choosing a AppServer/EJB(et al) over a
> WebServer/Servlets?
>
> Frank G.
> +======================================================================+
> | Crossroads Technologies Inc, 55 Broad Street, 28th Fl, NYC, NY 10004 |
> | Dot-com Engineering |
> | Email: [EMAIL PROTECTED] Web: www.CrossroadsTech.com |
> | Voice: 212-482-5280 x229 Fax: 212-482-5281 |
> +======================================================================+
>
> ===========================================================================
> 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".
>
> ===========================================================================
> 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".
===========================================================================
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".
