SYSTEM AND METHOD FOR PROVIDING DATA INTEROPERABILITY IN A DISTRIBUTED DATA GRID

• US 20150172405A1
• Filed: 06/19/2014
• Published: 06/18/2015
• Est. Priority Date: 12/13/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lee, Robert H., Howes, Jason John, BIHANI, Ballav
• Granted Patent: US 9,497,283 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A system and method can support data interoperability in a distributed data grid. The system can provide an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid. Furthermore, the acceptor can receive incoming data from a first client, which can be a non-native client that is associated with a client application. Additionally, the system allows a second client, which can be a native client associated with the distributed cache, to share the received incoming data with the first client.

Claims

1. A method for supporting data interoperability in a distributed data grid, comprising:

providing an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid;

receiving, via the acceptor, incoming data from a first client associated with a client application; and

allowing a second client associated with the cache to share the received incoming data with the first client.

2. The method according to claim 1, further comprising:

allowing the first client to be a non-native client that is associated with a non-native server, and

allowing the second client to be a native client of the distributed data grid.

3. The method according to claim 2, further comprising:

allowing the client application to replace the non-native client with another native client.

4. The method according to claim 2, further comprising:

allowing the non-native client to be one of

a memcached client, and

a representational state transfer (REST) client.

5. The method according to claim 1, further comprising:

allowing the first client to be implemented using a programming language that is not supported by the distributed data grid.

6. The method according to claim 1, further comprising:

allowing the first client to use a serializer to convert one or more software objects into a binary format.

7. The method according to claim 6, further comprising:

storing, via the acceptor, the incoming data in a binary format directly in the cache.

8. The method according to claim 1, further comprising:

providing another acceptor in the distributed data grid, wherein said another acceptor operates to use a serializer to covert incoming data received from another client into a binary format.

9. The method according to claim 1, further comprising:

allowing the acceptor to be configured as a proxy service that is provided by the distributed data grid.

10. The method according to claim 9, further comprising:

configuring the acceptor in a configuration file that is associated with the distributed data grid.

11. A system for supporting data interoperability in a distributed data grid, comprising:

one or more microprocessors;

the distributed data grid, which runs on the one or more microprocessors, that operates to provide an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid;

receive, via the acceptor, incoming data from a first client associated with a client application; and

allow a second client associated with the distributed cache to share the received incoming data with the first client.

12. The system according to claim 11, wherein:

the first client is a non-native client that is associated with a non-native server, and

the second client is a native client of the distributed data grid.

13. The system according to claim 12, wherein:

the client application operates to replace the non-native client with another native client.

14. The system according to claim 12, wherein:

the non-native client is one of

a memcached client, and

a representational state transfer (REST) client.

15. The system according to claim 11, wherein:

the first client is implemented using a programming language that is not supported by the distributed data grid.

16. The system according to claim 11, wherein:

the first client operates to use a serializer to convert one or more software objects into a binary format.

17. The system according to claim 16, wherein:

the acceptor operates to store the incoming data directly in the distributed cache.

18. The system according to claim 11, wherein:

the distributed data grid operates to provide another acceptor in the distributed data grid, wherein said another acceptor operates to use a serializer to covert incoming data received from another client into a binary format.

19. The system according to claim 11, wherein:

the acceptor is configured in a configuration file, which is associated with the distributed data grid, as a proxy service that is provided by the distributed data grid.

20. A non-transitory machine readable storage medium having instructions stored thereon for supporting metadata compression in a distributed data grid that when executed cause a system to perform the steps comprising:

providing an acceptor in the distributed data grid, wherein the acceptor is associated with a cache that is based on the distributed data grid;

receiving, via the acceptor, incoming data from a first client associated with a client application; and

allowing a second client associated with the distributed cache to share the received incoming data with the first client.