7.1.4: Other Distributed Object Technologies

Introduction to Cloud Computing · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    7.1.4: Other Distributed Object Technologies

    In addition to RPC, RMI, and CORBA, several other distributed object or component systems have played roles in distributed computing:

    • DCOM (Distributed Component Object Model): A Microsoft technology that extends COM (Component Object Model) to work across network boundaries. DCOM allows software components on different Windows machines to communicate as if the components were local, using a protocol called ORPC (Object RPC) behind the scenes. DCOM was used in Windows enterprise applications (e.g., for OLE/ActiveX components distributed across machines). Its usage is largely Windows-specific and it faced similar complexity issues as CORBA in practice.
    • .NET Remoting: In the early .NET framework, Microsoft provided .NET Remoting for object communication between application domains, potentially over a network. It allowed objects to be marshaled by value or by reference. .NET Remoting could use various channels (TCP, HTTP) and formatters (binary, SOAP). However, .NET Remoting was complex and has since been deprecated in favor of simpler web-service-based approaches (like ASP.NET Web Services, WCF, and now gRPC for .NET).
    • Enterprise JavaBeans (EJB) and RMI-IIOP: In the Java Enterprise world, EJBs (in early J2EE) were components that could be distributed. EJB remote interfaces used RMI underneath, often combined with CORBA’s IIOP (RMI-IIOP) to allow interoperability with CORBA clients. This blended approach let Java EJB servers talk to non-Java CORBA ORBs if needed. Over time, EJB remote invocation has also shifted toward simpler REST/gRPC calls in modern cloud designs.
    • Ice (Internet Communications Engine): A more modern take on distributed objects by ZeroC, Inc. Ice is a toolkit that in some ways learned from CORBA’s history, providing an object middleware with an IDL (Slice), support for multiple languages, but with a slimmer, easier-to-use design. It’s used in some performance-sensitive systems but is not as widespread as mainstream web service technologies.

    In summary, distributed object systems provided a crucial abstraction in distributed computing by making remote calls look like local object method invocations. This made it easier to build client-server applications and service-oriented architectures before web services and APIs took hold. However, tightly-coupled interfaces and platform dependencies (as in RMI or DCOM) and complexity (as in full CORBA) limited the universality of these approaches. The need for language-agnostic, loosely-coupled communication set the stage for web services, which we cover next.


    This page titled 7.1.4: Other Distributed Object Technologies was last modified on Sat, 12 Sep 2026 08:40:42 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Felix Amoruwa.