The Wikipedia page says the most recent version of the standard is 3.4, published in 2021: https://en.wikipedia.org/wiki/Common_Object_Request_Broker_A... In my 25+ year career I haven't seen it in use anywhere. I only ever encountered it while getting my CS degree.
The Rise and Fall of CORBA (2006)
71–80 of 156 posts
Re: The Rise and Fall of CORBA (2006)
#72I remember how CORBA was all going to be the future. I wrote dozens of programs in C++ and Python using IDL. Funny, though, that we now find ourselves doing the exact same thing but it is "an API", has no type-checking, no error handling, requires more work, is limited to particular languages and is slower. Distributed objects were ahead of their time by maybe 15 years. Now we're stuck in async API-over-JSON hell for…
What is telling because it's a badly defined beast that mostly doesn't work. But it did the type checking, automatic (client) endpoint creation, self-documentation, reflection-based (server) endpoints, support for lots and lots of languages (as long as you don't use something like an array)...
People keep promising new protocols that do one or two of those things on the modern world, but they always fail to deliver. AFAIK, the last promise was grpc, but doesn't even use a widely supported subset of HTTP so it has no chance of ever going anywhere.
Re: The Rise and Fall of CORBA (2006)
#73Re: The Rise and Fall of CORBA (2006)
#74For what it's worth, CORBA is hard to use from languages without a proper reflection. But with something like Java or .NET - it's a breeze.
And before you start asking questions why - no, REST or gRPC do not cut it. They are too primitive and come with poorly defined semantics. Their HTTP/1.1 transport is rudimental, though HTTP/2.0 made it better by allowing multiplex streams with an elusive possibility of a proper bidirectional communication. But CORBA already had all that, and more, since 2005! And I use it to the fullest extent in the distributed systems my company designs.
Re: The Rise and Fall of CORBA (2006)
#75In reality, what is probably most missing is consistent effort toward better organization and complexity management of problems (leading to effective solutions).
Without naming current 2-letter hype trains, we're doing it again after the blockchain stuff finally fizzled. Blockchain didn't magically solve our organizational and complexity problems, and so we need a new great hope.
New tech and patterns are exciting (probably mostly because of the promise of making our lives easier), but eventually one stops accepting them with big expectations. Ultimately it seems like instead of addressing the real difficulty in our technical solution development we create new distractions and use them to hide ourselves from the bigger problem that we can't seem to deal with.
Re: The Rise and Fall of CORBA (2006)
#76Re: The Rise and Fall of CORBA (2006)
#77I still use CORBA with huge success. For example, it is a backbone of several commercial systems that connect vending units in different regions and even countries. For what it's worth, CORBA is hard to use from languages without a proper reflection. But with something like Java or .NET - it's a breeze. And before you start asking questions why - no, REST or gRPC do not cut it. They are too primitive and come with po…
Re: The Rise and Fall of CORBA (2006)
#78I remember how CORBA was all going to be the future. I wrote dozens of programs in C++ and Python using IDL. Funny, though, that we now find ourselves doing the exact same thing but it is "an API", has no type-checking, no error handling, requires more work, is limited to particular languages and is slower. Distributed objects were ahead of their time by maybe 15 years. Now we're stuck in async API-over-JSON hell for…
We've finally come full circle with gRPC, which is basically a simplified CORBA. I went through the whole cycle, and while I don't exactly miss CORBA, I do wonder why it took us so long to get back to that baseline of functionality.
Scaling networks provided more value, and HTTP over networks was always going to work so protocols over HTTP just had to catch up, feature-wise.
Re: The Rise and Fall of CORBA (2006)
#79I still use CORBA with huge success. For example, it is a backbone of several commercial systems that connect vending units in different regions and even countries. For what it's worth, CORBA is hard to use from languages without a proper reflection. But with something like Java or .NET - it's a breeze. And before you start asking questions why - no, REST or gRPC do not cut it. They are too primitive and come with po…
gRPC is tightly coupled with HTTP/2 so the way you’re grouping it with REST doesn’t really make sense.