Success Stories

Jini Success Stories


A performant, persistent implementation of the JavaSpaces API, which is much more suitable for enterprise-grade use than the (in-memory only) reference implementation, Outrigger see here.

A re-packaging of the Blitz project to build with Maven is available here. It makes easy to provision a reliable, persistent JavaSpace with Rio.


Glyph is a set of utilities and annotations to speed up development for Jini-enabled applications.


Rio is an open source technology that provides a dynamic architecture for developing, deploying and managing distributed systems composed of services.

Rio turns a network of compute resources into a dynamic service, providing a policy based approach for fault detection and recovery, scalability and dynamic deployment. Key to the architecture are a set of dynamic capabilities and reliance on policy-based and SLA mechanisms.

Developing services for use with Rio is simple. Rio provides a non-intrusive model that removes the complexity surrounding service development and deployment.

Key features include:

  1. Dynamic architecture for distributed systems
  2. Built-in fault detection and recovery for your services
  3. Policy based SLA enforcement
  4. Support for external systems, encapsulate the control and monitoring of other frameworks
  5. Built-in support for Maven artifact resolution at deploy time
  6. Extensible service development & deployment support:
    1. POJOs
    2. Spring
    3. Maven based artifact resolution

Sucden Financial Limited

Sucden Financial Limited develops its own futures and options trading system called STAR, built primarily on the Java and Jini (Apache River) technologies.

The development of the system began when I joined Sucden almost ten years ago, beginning with connection to the Liffe derivatives exchange. It soon became the company’s primary trading system, and connectivity to the ICE and LME exchanges quickly followed.

With many local and remote users and ever increasing trading volumes, the typically n-tier architecture was difficult to upgrade, suffered from problems with scalability and was very susceptible to communications failures between it and the exchange host systems.

In 2006 we started a project to migrate to a service oriented architecture, specifically choosing Jini as a 100% Java solution. Jini had been around for a long time and I always thought it held great promise for our kinds of application, which needed very high throughput and fault tolerance – we (myself, Phil Harron and Hector Angel), were itching to use it for something useful. We hired IncaX consultants Phil Bishop and Nigel Warren to help us get going on the project. In 2007, Tom Hobbs and Ian Wood joined us and we began building all kinds of service management tools and infrastructure to encapsulate the complexities of Jini. A new kind of STAR was finally born early in 2009.

Jini has allowed us to move all our business logic into services, allowing for superb scalability, redundant exchange connections, and fault tolerant patterns which enable us to upgrade and perform maintenance in a live scenario. The system can monitor itself and alert support staff of problems automatically.

To visualize and manage the entire system, we built an application on the Netbeans platform where we can immediately see the interaction between services and generally monitor the health of the system as a whole. This is an ideal platform on which to present the Jini service UIs.

We are looking forward to upgrading to the Apache River code in 2011 and hope that the renewed efforts on this open source project will help to spread the word about this excellent technology far and wide."

Mark Phipps Front Office Development Manager, Sucden Financial Limited.

JGDMS - Java Global Discovered Micro Services

The github code is forked off River trunk, just before the Ivy dependency build changes and the 3.0 release was branched.

Additions include:

As soon as River community decides these improvements can be integrated back.