Excellent post Ali! My thoughts exactly. Glad to see someone else thinking
clearly.
>
> 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
>
>
===========================================================================
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".
