[omniORB] CORBA benefits over EJB model

[Brenneis, Steve]

One note on EJB and CORBA that is neither a pro or a con, but should be
considered in a designer's thinking for database-centric applications. EJB
is very rigidly tied to the database structure. This has good points and bad
points. CORBA, particularly through the Persistent Object Service, can be
much more flexible. As with the rest of CORBA, this flexibility has a cost
of some extra complexity, but it is nothing that should actually require
advanced experts to code.

Steve Brenneis
ProServe Lead Developer
AT&T Wireless Services
Desk (336) 286-1783
Cell (336) 456-3290
FAX (336) 286-1880
"I am opposed to millionaires, but it would be dangerous to offer me the
position." -- Mark Twain


-----Original Message-----
From: Ben Miller [mailto:Ben.Miller@Mercia.Com]
Sent: Wednesday, June 06, 2001 1:02 PM
To: 'omniorb'
Subject: [omniORB] CORBA benefits over EJB model


I know it is a generic CORBA question rather than specifically
omniORB, but I know you lot have experience of using CORBA....

Can anyone think of any practical advantages to starting a new product
from scratch using CORBA rather than EJBs.  The reason is that we are
about to embark on a 3-tier application and I have a gut feeling that
CORBA will be more performant in the long run.  I need to convince the
rest of the team that CORBA is the way to go, but I'm coming up
against "CORBA is old technology now" arguments.

We have no need to link to legacy systems, so there's no _physical_
reason that we couldn't write everything using Java rather than C++.
My benchmark tests have shown that mathematical calulation performance
is better using C++ than Java, but need more ammunition!  Please
help...


Best regards,
Ben.
Mercia Software Ltd.
Mercia House 
Ashted Lock
Aston Science Park
Birmingham B7 4AZ, UK 
Registered Number: 1868855 (Cardiff) 
Tel: 44 (0)121 359 5096 
Fax: 44 (0)121 359 0375 
Web Site: http://www.mercia.com