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 navigation and no transaction
needs for the reads, should be implemented with something other then EJB - I
like servlets. BUT, the purchasing of goods and services on these sites should
be implemented with EJB via Servlets.
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 ??
>
> -- Ahimanikya
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Richard Monson-Haefel
> > Sent: Thursday, February 17, 2000 6:09 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Session EJBs vs. Java Objects
> >
> >
> > Assaf Arkin wrote:
> >
> > > EJB is pretty much your Java objects + RMI/IIOP + some EJB logic. That
> > > means you can expect it to be slower that plain Java objects.
> > >
> > > Even if you do not perform the a remote method invocation, still EJB
> > > needs to deal with method parameters and return type through
> > > marshalling, which is dead slow on some JVMs. (On my machine everything
> > > slows down to 25%).
> > >
> > > The Servlet 2.3 API supports the same transactions and JDBC connection
> > > pooling that is available for EJB, so if that's all you're looking for,
> > > consider running your database access from the Servlet itself.
> > >
> > > arkin
> > >
> >
> > Before EJB was officially announced, back in the fall of 1997, I
> > developed a site for
> > a major cruise line that used Servlets 1.0 and direct JDBC access
> > through a facade of
> > Java Business Objects. It is quite fast because data access is
> > direct, and flexible
> > because the business object allowed me to assemble solutions
> > easily. This site is not
> > transactional, has no authorization security needs, and is read
> > only. It has been
> > running for three years with little or no modification and its
> > still going strong. A
> > clear case for using Servlets with direct JDBC access instead of EJB.
> >
> > --
> > Author of Enterprise JavaBeans
> > Published by O'Reilly & Associates
> >
> > EJB FAQ
> > http://www.jguru.com/faq/EJB
> >
> > EJBNow.com
> > http://www.ejbnow.com
> >
> > ==================================================================
> > =========
> > 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".
--
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
EJB FAQ
http://www.jguru.com/faq/EJB
EJBNow.com
http://www.ejbnow.com
===========================================================================
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".
