corba-J2EE-EJB-WebSphere?

java-programmer, corba-J2EE-EJB-WebSphere? Some help for a newbee?

I've been a c/C++ programmer in VMS, OS/400, and most recently, Windows
and Dot Net. However, I have recently signed on as Q/A manager at a
predominantly Java shop. We have some consultants coming in to assess our
scaleability and architecture, and I'd like to be in a position to at least
make some intelligable noises. I have gotten the sense that there is at
least some compatability between these, but I'm not picking up the extent,
if any, to which any are essentially competing technologies. Is some subset
of these an obvious choice for a medium volume site with lots of active
content, with scaleability, performance, and maintainability being our top
three criteria? Thanks.

Joe
email***@***.com
(please remove "nospam." to reply)

java-programmer >> corba-J2EE-EJB-WebSphere? IBM WebSphere provides a J2EE implementation, which includes EJB.
EJB requires CORBA interoperability, and WebSphere actually contains
a full ORB implementation to achieve that. Now, at least all the
topics in the headline have been mentioned once :-).

EJB and CORBA do not really compete but rather complement each other:

- CORBA implementations are available for just about any mainstream
language, J2EE/EJB is Java-only, so there are many scenarios where
EJB is not an option at all, and CORBA is in fact the only one.

- as pointed out above, an EJB implementation actually requires CORBA,
(mre specifically, the IIOP and CSIv2 protocols), and some products
are actually enriched ORBs.

- CORBA as such such does not provide technology and programming models
for 3-tier environments. J2EE does this with one gazillion Java APIs,
and also in its latest version offer to expose EJBs as Web Services.
"Active content" sounds like you need Web frontends that access backend
databases, and J2EE does provide APIs and patterns for that.

- scalability and performance depend on many details, in principle you
should be able to design salable and performant systems with either
technology, although CORBA will cause less overhead in many cases.
You will also be able to screw things up with either technology, of
course :-).

Hope that helps a little, Gerald.

Joe Befumo wrote:
> Some help for a newbee?
>
> I've been a c/C++ programmer in VMS, OS/400, and most recently, Windows
> and Dot Net. However, I have recently signed on as Q/A manager at a
> predominantly Java shop. We have some consultants coming in to assess our
> scaleability and architecture, and I'd like to be in a position to at least
> make some intelligable noises. I have gotten the sense that there is at
> least some compatability between these, but I'm not picking up the extent,
> if any, to which any are essentially competing technologies. Is some subset
> of these an obvious choice for a medium volume site with lots of active
> content, with scaleability, performance, and maintainability being our top
> three criteria? Thanks.
>
> Joe
> email***@***.com
> (please remove "nospam." to reply)
>
>

--
Dr. Gerald Brose mailto:email***@***.com
Xtradyne Technologies http://www.xtradyne.com
Schoenhauser Allee 6-7, Phone: +49-30-440 306-27
D-10119 Berlin, Germany Fax : +49-30-440 306-78

java-programmer >> corba-J2EE-EJB-WebSphere? Thanks so much for that comprehensive overview -- just what I needed. Oh my
God -- I'm starting to feel like Dilbert's boss!

"Gerald Brose" <email***@***.com> wrote in message
news:email***@***.com...
> IBM WebSphere provides a J2EE implementation, which includes EJB.
> EJB requires CORBA interoperability, and WebSphere actually contains
> a full ORB implementation to achieve that. Now, at least all the
> topics in the headline have been mentioned once :-).
>
> EJB and CORBA do not really compete but rather complement each other:
>
> - CORBA implementations are available for just about any mainstream
> language, J2EE/EJB is Java-only, so there are many scenarios where
> EJB is not an option at all, and CORBA is in fact the only one.
>
> - as pointed out above, an EJB implementation actually requires CORBA,
> (mre specifically, the IIOP and CSIv2 protocols), and some products
> are actually enriched ORBs.
>
> - CORBA as such such does not provide technology and programming models
> for 3-tier environments. J2EE does this with one gazillion Java APIs,
> and also in its latest version offer to expose EJBs as Web Services.
> "Active content" sounds like you need Web frontends that access backend
> databases, and J2EE does provide APIs and patterns for that.
>
> - scalability and performance depend on many details, in principle you
> should be able to design salable and performant systems with either
> technology, although CORBA will cause less overhead in many cases.
> You will also be able to screw things up with either technology, of
> course :-).
>
> Hope that helps a little, Gerald.
>
>
> Joe Befumo wrote:
> > Some help for a newbee?
> >
> > I've been a c/C++ programmer in VMS, OS/400, and most recently,
Windows
> > and Dot Net. However, I have recently signed on as Q/A manager at a
> > predominantly Java shop. We have some consultants coming in to assess
our
> > scaleability and architecture, and I'd like to be in a position to at
least
> > make some intelligable noises. I have gotten the sense that there is at
> > least some compatability between these, but I'm not picking up the
extent,
> > if any, to which any are essentially competing technologies. Is some
subset
> > of these an obvious choice for a medium volume site with lots of active
> > content, with scaleability, performance, and maintainability being our
top
> > three criteria? Thanks.
> >
> > Joe
> > email***@***.com
> > (please remove "nospam." to reply)
> >
> >
>
>
> --
> Dr. Gerald Brose mailto:email***@***.com
> Xtradyne Technologies http://www.xtradyne.com
> Schoenhauser Allee 6-7, Phone: +49-30-440 306-27
> D-10119 Berlin, Germany Fax : +49-30-440 306-78
>