See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
With the Datagrid APIs, a client can send requests to one partition, a subset of partitions, or all the partitions in a grid. The client can specify a list of keys, and the ObjectGrid determines the set of partitions that are hosting the keys. The request is then sent to all the partitions in the set in parallel and the client waits for the results. The client can also send requests without specifying keys. In this case, requests are sent to all partitions.
Data Grid agents that are deployed to the grid do not work in client mode. These agents work directly against the primary shard. Working directly against the primary shard results in maximum performance, allowing tens of thousands or more transactions per second because the agent works with the data at full memory speeds. Working directly with the primary shard also means that a DataGrid agent can only see data that is within that shard. This provides some interesting opportunities that cannot be done on a client.
A normal ObjectGrid client must be able determine the partition from the transaction. This ability is necessary because the client needs to route the request. If an agent is directly attached to a shard, then no routing is needed. All requests go against that shard. Because the agent is directly attached to a shard, data in other maps in the shard can be accessed without worrying about common partitioning keys, and so on, because no routing occurs.
For more details on DataGrid, refer to ObjectGrid DataGrid API.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
