In the mid-90's, I got to become experienced in CORBA distributed programming environments. While it's considered a dead technology with a lot of flaws, I would like to look at it specifically at it from a boundaries point of view.
With the advantage of hindsight, we can look at which characteristics of a distributed programming environment:
With the advantage of hindsight, we can look at which characteristics of a distributed programming environment:
- Interface Definition Language (IDL) - is not a deal breaker. If you look at current environments like gRPC, the use of a language independent definition language allows wide adoption. The ability to do code generation for your interfaces ensure that you can implement clients and servers with static type checking (if your language supports that).
At the same time, JSON is also widely used is REST implementations. So, another successful alternative is an interpretive on the wire format. - Leaking language details into other implementations is not good. Anyone who implemented a CORBA system would have to learn and understand a fairly complicated memory management scheme that had _ptr and _var in C++ and Java affecting your client and server code because the vendors also wanted to support C. This means that even if you are just implementing business logic, you were exposed to the complexity.
- Assuming a flat network design. While there were proprietary work around (Visibroker GateKeeper) with long polling HTTP gateways, one of the fundamental assumptions in CORBA is that all network endpoints are equally available and connected. That's just not true. In the real world you have firewalls, proxy servers, reverse proxy servers, etc. and CORBA generally just didn't play well with them.
- A greedy set of vendors with a committee based set of standards. I know this isn't a technical issue, but it affected how software was developed.
For example, when the CORBA standard moved from a BOA (Binary Object Adapter - which is not standardized - each vendor did their own) to a POA (Portal Object Adapter - each vendor was supposed to generate standard code) Visibroker, for example, would charge you for any named POA's and not for unnamed POA's. This would allow you to establish callback objects - think of a push notification - but would not allow you to debug which clients were having problems because they were not named.
To add insult to injury, that didn't stop them from insisting on audit's that use different license terms than the version deployed.
Part of the problem is that open source was not as available then. Getting management buy in to use an open source implementation (like ICE) that was moving faster than the standard was difficult.
Comments
Post a Comment