Hi Russ,
though the concept of EJBs sounds interesting and appealing there are two complaints
against it
(1) its not fully mature like other components of J2EE. Anybody who has developed
using would know the numerous small issues here and there. I have
been using EJBs from 1.1 and has been folllowing the spec to 2 and then pd2. Though it
is moving in right direction it is still not fully there.
(2) what does all these additional hue and cry finally buy?
the question which everybody raises, which Sun and others intrested in future of EJB
has to answer clearly, is what does it finally bring to the table
that is substantial to the developer??? Still looking for a convincing answer.
Thanks
Krishnan
-----Original Message-----
From: Russ White [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 1:15 PM
To: Orion-Interest
Subject: RE: EJB vs Servlets
Why do you have the idea the EJBs yield slower performance? This is false.
Your site sounds to small to worry about EJB right now. Stick with Struts. Still
as a developer you owe it to yourself to dig deeper.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin
> Sent: Monday, October 09, 2000 3:03 PM
> To: Orion-Interest
> Subject: RE: EJB vs Servlets
>
>
> You are talking about legacy support. I agree there. I haven't read the full
> spec of EJB, and I heard EJB 2.0 is even better. I would agree that overall
> its probably a better way to go, but, what does it really offer that you
> can't do in the servlet engine? If you can do fail-over/scalability,
> connection pooling, transaction management, and so on now, what benefits do
> you get from moving to EJB? Is it worth the bit slower process of developing
> them, and the slower performance? I think on our site we would be lucky to
> see 1000 users a day in 2 years from now, using our site, and we have about
> 50 or so a day now. So is there a big need for us to move to EJB in terms of
> future growth, or is the only "good" reason (for small to mediume sites) to
> move to EJB is just to separate your tiers amongst servers?
>
>
> > -----Original Message-----
> > From: Troy Echols [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, October 09, 2000 11:37 AM
> > To: Orion-Interest
> > Subject: Re: EJB vs Servlets
> >
> >
> > Might there be some benefit to using EJBs over servlets alone
> > if you want to
> > support various modes of connectivity to your business logic
> > (e.g., standalone
> > clients using JMS/CORBA/RMI in addition to web clients).
> >
> > Just my two cents worth.
> >
> > Troy
> >
> > > Hani Suleiman wrote:
> > >
> > > I've considered using EJB's a number of times for various
> > projects I'm
> > > involved in, but every time, I have to admit to myself that
> > it's more for the
> > > fun and coolness factor, than any real 'need' to use EJB's.
> > >
> > > In every case, I was able to implement a solution using
> > servlets with various
> > > caches to do whatever is needed much faster than an EJB
> > would do things (as
> > > far as I can tell, I haven't put this theory to the test
> > yet though!). Here
> > > are some examples of EJB features and ways to get the same
> > thing without
> > > EJB's..
> > >
> > > 1) Connection pooling: This is available everywhere, and
> > everyone can reap the
> > > benefits of it while being perfectly EJBless.
> > >
> > > 2) Transaction support: Stored procedures can take care of this.
> > > 3) Caching of database objects: Pretty easy to implement
> > > 4) Failover/load-balancing: As Kevin mentioned, works very
> > nicely for
> > > servlets.
> > >
> > > Having said all that though, I'm still going to try and use
> > EJB's in my
> > > current project, and port all the existing 'model' objects
> > to become full
> > > fledged EJB's. I'm hoping the advantages will become apparent then!
> > >
> > > Also, does anyone have any concrete examples of EJB's
> > performance/scalability?
> > > Has anyone deployed them in a high volume production
> > environment? Most people
> > > seem to be using them for prototyping and small scale
> > projects, that I know
> > > of...
> > >
> > > Hani Suleiman
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > > > Duffey, Kevin
> > > > Sent: Monday, October 09, 2000 1:22 PM
> > > > To: Orion-Interest
> > > > Subject: EJB vs Servlets
> > > >
> > > >
> > > > Hey all,
> > > >
> > > > I know this is a little off-topic, but seeing as how Orion is
> > > > about the only
> > > > fully compliant EJB server, I figured this would be a better
> > > > place to ask.
> > > >
> > > > Lately I have talked to a number of people that have been
> > > > moving towards EJB
> > > > and pulled back because they have found it to be more tedious
> > > > to develop, as
> > > > well as the end result was slower than just using Servlets.
> > > >
> > > > I ask this because it appears to me that the servlet engine
> > > > (at least with
> > > > 2.2) being able to be failed over, load-balanced, etc, seems
> > > > to be quite as
> > > > capable for scalability and fault-tolerance as the ejb engine
> > > > used to be. I
> > > > do realize that the EJB container offers transaction
> > management, but
> > > > connection pooling is available in the servlet engine at the
> > > > server level as
> > > > well. So, if you lose speed in development time and
> > > > performance, what is the
> > > > real benefits of moving to EJB? I should say this with
> > > > caution..I am sure
> > > > the EJB engine/container offers some things the servlet
> > > > container doesn't,
> > > > but I would think its possible to actually put those
> > abilities in the
> > > > servlet container.
> > > >
> > > > Anyways..I'll be interested in hearing any feedback on this.
> > > >
> > > > Thanks.
> > > >
> >
>
>
