Very good recommendations. In our best practices work we use interfaces for
this purpose at each major architecture boundary.
-Chris.
> -----Original Message-----
> From: Ali [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 25, 2000 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Design question
>
> IMO, and in recommendations I make to clients, I suggest designing
> architectures and systems that are less dependent on a particular
> technology-base. Especially one such as EJB which is undergoing puberty.
>
> Many vendors are out there claiming that their's is the ultimate EJB
> server;
> whereas in reality the state of the EJB industry is undergoing maturation:
> experience on major projects are just beginning to come out. But remember
> that
> these experiences are based, typically, on design decisions that were made
> up
> to six months ago based on that day's technology infratsructure stability
> and
> capabilities.
>
> So the theme of the story, IMO, is that you should --as always -- design
> and
> program to interfaces that isolate the use of a given technology such as
> EJBs.
> Examples are using Proxies, Bridges, Stateless Helpers, Business
> Interface,
> etc.
>
> Make no mistake: EJBs are a strong trend that will grow in the furture in
> a
> very rapid fashion and lay the foundation for accessible destributed
> technology
> for all levels of development organizations. But we need to insulate
> ourselves,
> as architects and developers, from the strong tides of immature
> technologies by
> using them indirectly, so that they can be replaced "under the covers"
> with a
> stronger version and more mature experience as they unfold.
>
> This does not mean we should not use EJBs, but to use them indirectly.
>
> Regards,
>
> Ali Arsanjani
>
> Jes�s Vi�uales Bueno wrote:
>
> > The idea of "using always EJB for everything" is wrong.
> > The scenario you have described may be perfect for implementing remote
> > object with CORBA (or RMI, of course :-).
> > You can store your data in a different execution thread (backgroung
> work),
> > and so on.
> >
> > Maybe I don't undesrtand your needs, but my arguments are valid for many
> > other situations. EJB is not the "panacea" for everything, IMHO.
> >
> > Regards,
> > Jesus
> >
> >
> ==========================================================================
> =
> > 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".
