OpenSpaces Remoting Components

Added by Shay Banon, last edited by Aleia Hutcherson on May 19, 2008  (view change)
  Search Here
Searching XAP 6.0 Documentation

                                               
Summary: Remoting allows you to use remote invocations of POJO services, with the space as the transport layer.

Overview

Spring provides support for different remoting technologies. OpenSpaces uses the same concepts to provide remoting using the space as the underlying protocol.

Some benefits of using the space as the transport layer include:

  • High availability – since the space by its nature (based on the cluster topology) is highly available, remote invocations get this feature automatically when using the space as the transport layer.
  • Load-balancing – when using a space with a partitioned cluster topology, each remote invocation is automatically directed to the appropriate partition (based on its routing handler), providing automatic load-balancing.
  • Performance – remote invocations are represented in fast internal OpenSpaces objects, providing fast serialization and transport over the net.
  • Asynchronous execution – by its nature, remoting support is asynchronous, allowing for much higher throughput of remote invocations. OpenSpaces allows you to use asynchronous execution using Futures, and also provides synchronous support (built on top of it).

OpenSpaces supports two types of remoting, distinguished by the communication protocol performed between the client and the server, called Async Remoting and Sync Remoting.


IMPORTANT: This is an old version of GigaSpaces XAP. Click here for the latest version.
GigaSpaces 6.0 Documentation Contents (Current Page in Bold)

    Java

    C++

    .NET

    Middleware Capabilities

    Configuration and Management

Add GigaSpaces wiki search to your browser search engines!
(works on Firefox 2 and Internet Explorer 7)

Labels

 
(None)