For a distributed computing project starting today, with 0 legacy components, are there any good reasons to look into CORBA?
For a distributed computing project starting today, with 0 legacy components, are there any
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There are still situations where CORBA could be a good answer:
system involving multiple programming
languages and multiple platforms,
complex data structures … and SOAP
doesn’t cut it,
… and HTTP doesn’t cut it, or
existing CORBA clients and/or
services.
But having said that, there are alternatives that do what CORBA does, only better … or so they claim. For example ZeroC’s ICE
EDIT @fnieto chimes in to say (or imply) that ICE is not free, but TAO is.
This is inaccurate and misleading.
The down-side of ICE is lack of interoperability with CORBA middleware stacks, but in my experience interoperability of different CORBA implementations could also be problematic. (Things may have improved in that area … but I haven’t done any CORBA work since ~2002, so I’m a bit out of touch.)