CarrierWave provides a set of facilities that automate and extend the EJB Value Object (or Data Transfer Object) pattern into supporting arbitrary value graphs. Specifically, CarrierWave provides a code generator that creates typed value objects from the source code of corresponding business objects, a client interface supporting the selection, modification, deletion, and invocation of business objects, and near-transparent business object persistence through various object persistence applications and interfaces like JDO.
OAF is the Object Activation Framework for GNOME. It has a similar purpose to gnorba, the GNOME 1.x CORBA activation library, and will replace it for GNOME 2.0. It allows you to do much more powerful activation queries than gnorba. Each server is described by an XML file that defines its attributes. When querying or activating, one may specify complex requirements using the OAF query language.
Aorta is a load-balancing clustered P2P application. It executes Tasklets (which have the ability to split themselves into sub tasks that can be executed in pararell). A typical cluster contains of a LAN with 1-256 computers, each one running aorta. A Tasklet can be of any type ranging from encoding MP3s, Genomic DNA Alignment, or simply to rendering Web pages for high speed/heavily loaded Web sites. You can make functions calls to C/C++, applications like Matlab, etc.
Ice is a modern alternative to object middleware such as CORBA or COM/DCOM/COM+. It is easy to learn, yet provides a powerful network infrastructure for demanding technical applications. It features an object-oriented specification language, easy to use C++ and Java mappings, a highly efficient protocol (including protocol compression), asynchronous method invocation and dispatch, dynamic transport plug-ins, TCP/IP and UDP/IP support, SSL-based security, a firewall solution, and much more.
Spif (Simplest Possible Infrastructure Framework) provides a simple API for model object access and uses a chain of responsibility to realize the infrastructure behind the interface. This means that you can write business code which accesses persistent, possibly remote objects without worrying about locking, distribution persistence, caching, etc. Using Spif, such features are easy to change later, without changing business code.