CORBA

CORBA
Name	CORBA
Developer	Object Management Group
Released	1991
Operating system	Cross-platform
Genre	Middleware

CORBA CORBA is a cross-platform middleware specification for enabling communication among distributed objects, developed to allow Sun Microsystems, IBM, Microsoft, Oracle Corporation, and other vendors to interoperate in heterogeneous environments. It was standardized by the Object Management Group to provide language- and platform-neutral remote method invocation, supporting enterprise systems used by organizations such as NASA, European Space Agency, AT&T, Siemens, and General Electric. The specification influenced and was influenced by contemporaneous technologies like Distributed Computing Environment, Remote Procedure Call, Java RMI, and later Web Services and gRPC.

Overview

CORBA emerged in the early 1990s amid efforts by vendors including Sun Microsystems, IBM, HP, Oracle Corporation, and Siemens to create portable component-based architectures for distributed applications. The Object Management Group shepherded successive versions and specifications, producing standards such as the CORBA 2.x family and the CORBA 3.0 enhancements. Deployments spanned industries including aerospace (NASA), telecommunications (AT&T), finance (Deutsche Bank), manufacturing (General Motors), and defense (Lockheed Martin), integrating systems built with languages from C++ and Java to Ada and Python.

Architecture and Components

CORBA defines a set of architecture elements: the Object Request Broker, object adapters, object implementations, and an Interface Repository. The Object Request Broker conceptually mediates requests between client stubs and server skeletons, analogous to Remote Procedure Call mechanisms used in Sun RPC and DCE/RPC. Implementation repositories and naming services provided by vendors such as BEA Systems, Iona Technologies, and Novell enabled service location similar to LDAP directories used by Microsoft and Netscape Communications Corporation. Interoperability protocols like the Internet Inter-ORB Protocol drew parallels with TCP/IP stacks and influenced integration with CORBA-aware application servers from Oracle Corporation and IBM WebSphere.

Interface Definition Language (IDL)

CORBA's IDL specifies interfaces in a language-neutral form to generate bindings for languages such as C++, Java, Python, Ada, Smalltalk, and Visual Basic. IDL mappings were published by the Object Management Group and implemented by vendors including Sun Microsystems and Oracle Corporation. IDL enabled tools to produce client stubs and server skeletons similar to the code generation used in Protocol Buffers or Apache Thrift, and its repository model paralleled metadata approaches in WSDL used by Microsoft and IBM in web services. Language mappings addressed ABI and type compatibility concerns faced by projects such as GNU Compiler Collection and platform vendors including Red Hat and Microsoft.

Implementations and Language Bindings

Commercial and open-source CORBA implementations were provided by companies and projects such as Borland, Iona Technologies (Orbix), Orbix customers, JacORB, TAO (The ACE ORB), ORBacus, MICO (Mico), OpenORB, and Sun ONE (formerly Sun ONE ORB). These implementations offered bindings for C++, Java, Python, Perl, Tcl, and Ada. Tool vendors like Rational Software and Microsoft provided IDE integration and modeling support used alongside UML tooling from Sparx Systems and Enterprise Architect. Real-time CORBA profiles addressed deterministic requirements in systems developed by Lockheed Martin, Thales Group, and BAE Systems.

Interoperability and Standards

Interoperability efforts centered on the Internet Inter-ORB Protocol and standards promulgated by the Object Management Group, often coordinated with other standards bodies like the IETF and ISO. The CORBA Interoperability Testbed involved vendors such as IBM, Sun Microsystems, Oracle Corporation, HP, and Siemens to validate cross-vendor compatibility. Extensions and related standards—such as CORBA Components, CORBA Notification Service, and the Real-Time CORBA specification—aligned with enterprise integration platforms from IBM WebSphere and Oracle Fusion Middleware, and competed with alternatives from Microsoft and Apache Software Foundation projects.

Use Cases and Applications

CORBA saw adoption in large-scale, mission-critical systems: avionics and defense systems by Lockheed Martin and Northrop Grumman, telecom infrastructure by AT&T and Alcatel-Lucent, financial trading platforms by Deutsche Bank and Goldman Sachs, manufacturing control systems at General Motors and Siemens, and scientific computing at NASA and European Space Agency. Integration patterns included legacy system wrapping for UNIX-based systems, multi-language service composition, and distributed control in industrial automation used by ABB and Schneider Electric.

Criticisms and Decline

CORBA attracted criticism for complexity, heavyweight specifications, and vendor-specific extensions, which analysts at firms like Gartner and Forrester Research documented. The rise of simpler, web-centric protocols such as SOAP, REST, JSON, and technologies promoted by Microsoft and Google reduced CORBA's prevalence. Additionally, platform-specific alternatives like Java RMI and emerging RPC frameworks including Protocol Buffers and gRPC shifted developer preference away from CORBA, contributing to its decline in new greenfield projects despite continued maintenance in legacy systems at organizations like Boeing and Siemens.

Category:Middleware