Real Time Client - RTC

Skip to end of metadata
Go to start of metadata

The Coherence Real Time Client provides secure and scalable access from client applications into a Coherence Data Grid. Coherence RTC extends the Data Grid to the Desktop, providing the same core API as the rest of the Coherence product line. As of Coherence 3.2, Coherence RTC is licensed as Coherence Real Time Client.

Connectivity into the Coherence Data Grid is achieved via Coherence*Extend technology, which enables a client application to connect to a particular server within the Data Grid. Since the connections are load-balanced across all of the servers in the Data Grid, this approach to connectivity can scale to support tens of thousands of clients.

This section provides the following information:

Uses

The primary use case for Coherence RTC is to provide clients with read-only/read-mostly access to data held in a Coherence cluster. Clients can query clustered caches and receive real-time updates as the data changes. Clients may also initiate server-side data manipulation tasks, including aggregations and processing. For more information on aggregations and processing, see the following API:

  • Java: ${xhtml} and ${xhtml}
     
  • C++: ${xhtml} and ${xhtml}

Cache Access

Normally, client applications are granted only read access to the data being managed by the Data Grid (delegating cache updates to Data Grid Agents), although it is possible to enable direct read/write access.

Local Caches

While the client application can directly access the caches managed by the Data Grid, that may be inefficient depending on the network infrastructure. For efficiency, the client application can use both Near Caching (Java, C++, or .NET) and Continuous Query Caching (Java, C++, or .NET) to maintain cache data locally.

Event Notification

Using the standard Coherence [event model|data changes that occur within the Data Grid are visible to the client application. Since the client application indicates the exact events that it is interested in, only those events are actually delivered over the wire, resulting in efficient use of network bandwidth and client processing.

For more information on the event model, see:

Agent Invocation

Since the client application will likely only have read-only access, any manipulation of data is done within the Data Grid itself; the mechanism for this is the Data Grid Agent, which is presented by these API:

  • Java: ${xhtml}
     
  • C++: ${xhtml}

Clients may invoke tasks, aggregators and processors for server-side cached objects using the InvocableMap methods.

Connection Failover

If the server to which the client application is attached happens to fail, the connection is automatically re-established to another server, and then any locally cached data is re-synced with the cluster.

Labels:
events events Delete
clients clients Delete
rtc rtc Delete
localcache localcache Delete
near-cache near-cache Delete
agents agents Delete
core-concept core-concept Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.