This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (June 2014) (Learn how and when to remove this message) This article provides insufficient context for those unfamiliar with the subject. Please help improve the article by providing more context for the reader. (February 2018) (Learn how and when to remove this message) (Learn how and when to remove this message)

In computing, fragmented objects are truly distributed objects. It is a novel design principle extending the traditional concept of stub based distribution.

In contrast to distributed objects, they are physically distributed and encapsulate the distribution in the object itself. Parts of the object - named fragments - may exist on different nodes and provide the object's interface. Each client accessing a fragmented object by its unique object identity presumes a local fragment. Fragmented objects may act like a RPC-based infrastructure or a (caching) smart proxy as well. Therefore, clients cannot distinguish between the access of a local object, a local stub or a local fragment. Full transparency is gained by the following characteristics of fragmented objects.

Arbitrary protocols may be chosen for the internal communication between the fragments. For instance, this allows to hide real-time protocols (e.g., RTP for media streaming) behind a standard CORBA interface.

The internal structure of a fragmented object is arranged by the object developer/deployer. It may be client–server, hierarchical, peer-to-peer and others. Thus, a downward compatibility to stub based distribution is ensured.

As both the distribution of state and functionality are hidden behind the object interface, their respective distribution over the fragments is also arbitrary. In addition, an application using a fragmented object can also tolerate a change in distributions which is achieved by exchanging the fragment at one or multiple hosts. This procedure can either be triggered by a user who changes object properties or by the fragmented object itself (that is, the collectivity of its fragments,) e.g., when some fragment is considered to have failed. Of course, an exchange request may trigger one or more other internal changes. The object developer can migrate the state and the functionality over the fragments by providing different fragment implementations. Those dynamically change inside the fragmented objects. A flexible internal partitioning is achieved, providing transparent fault-tolerant replications as well.

• Aspectix – The Aspectix group works on several projects that focus on middleware architecture, adaptive and quality-of-service-aware applications, fault tolerance, aspect-oriented programming, and automated source-code transformation.
• FORMI – FORMI is an extension of Java RMI.
• Globe – This project looks at a powerful unifying paradigm for the construction of large-scale wide area distributed systems: distributed shared objects.
• SOS – The SOMIW object-oriented Operating System.

• Structure and Encapsulation in Distributed Systems: the Proxy Principle
• Fragmented objects for distributed abstractions
• Globe: A Wide-Area Distributed System
• Integrating fragmented objects into a CORBA environment
• FORMI: An RMI Extension for Adaptive Applications Archived 2007-08-15 at the Wayback Machine
• FORMI: Integrating Adaptive Fragmented Objects into Java RMI

• Aspectix
• FORMI
• Globe -
• SOS