Java object cache server for databases

• US 8,156,085 B2
• Filed: 03/30/2007
• Issued: 04/10/2012
• Est. Priority Date: 04/17/2003
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Dominguez, Frank Jr., Moellenhoff, Dave, Chan, Eric
• Primary Examiner(s): Ali, Mohammad
• Assistant Examiner(s): HASAN, SYED HAROON
• Application Number:
  US11/694,850
• Publication Number:
  US 20070288510A1
• Time in Patent Office: 1,838 Days
• Field of Search: None
• US Class Current: 707/689
• CPC Class Codes: H04L 67/5651 Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A cache server is provided in a network for storing Java objects for retrieval by one or multiple application servers. Application server(s) are configured to request an object from the cache server, rather than requesting the Java object directly from a database, so as to reduce processing load on the database and free up database resources. Responsive to a request for a Java object from an application server, e.g., in an HTTP request, the cache server determines if the object is stored in memory and if so, serializes the requested object and sends the serialized object to the requesting server, e.g., in an HTTP response. The requesting server then deserializes the Java object. If the object is not stored in memory, the cache server instantiates the object (typically by requesting the object from the database), serializes the instantiated object and sends it to the requesting server. Cache coherency methods are also provided.

Claims

1. A method of providing an object from a cache server to a requesting system, the method comprising the steps, implemented in a cache server, of:

receiving a request from a requesting system, the request identifying an object;

responsive to said request, determining whether the identified object is stored in the cache server; and

if the identified object is stored in the cache server;

serializing the identified object into a byte stream to form a serialized object; and

sending the serialized object to the requesting system; and

if the identified object is not stored in the cache server instantiating the identified object;

serializing the instantiated Java object into a byte stream to form a serialized object; and

sending the serialized Java object to the requesting system; and

receiving an invalidation request from a requesting system to invalidate an object on the cache server and identifying an object to rebuild; and

rebuilding the identified object responsive to receiving the invalidation request.

2. The method of claim 1, wherein instantiating includes:

requesting the identified object from the object database; and

receiving the requested object from the object database.

3. The method of claim 1, further including storing the instantiated Java-object in the cache server.

4. The method of claim 1, wherein the received request is an HTTP request, and wherein sending the serialized object includes sending the object in an HTTP response to the requesting system.

5. The method of claim 1, further including automatically removing, from the cache server, objects that have not been accessed within a specified access interval.

6. The method of claim 1, further including automatically removing, from the cache server, one or more Java-objects when it is determined that a specified number of objects are stored in the cache server.

7. The method of claim 1, further including:

receiving an update message from a requesting system, said update message identifying a second object to update; and

updating the second identified object responsive to receiving the update message.

8. The method of claim 1, further including storing the serialized object to a disk.

9. The method of claim 1, further including storing the serialized object to a disk drive.

10. The method of claim 1, wherein the object is a Java object.

11. An object cache server communicably coupled to an object database and one or more requesting systems, the cache server comprising:

a processor; and

a memory for storing objects,

wherein the server is configured to;

receive a request from a requesting system, said request identifying an object;

determine whether the identified object is stored in the memory; and

if the identified object is stored in memory;

serialize the identified object into a byte stream to form a serialized object; and

send the serialized object to the requesting system; and

if the identified object is not stored in memory;

instantiate the identified object;

serialize the instantiated object into a byte stream to form a serialized object; and

send the serialized object to the requesting system; and

wherein the server is further configured to rebuild a object stored in the memory in response to an invalidation request from a system to invalidate an object on the server, said invalidation request identifying the object to be rebuilt.

12. The server of claim 11, wherein the server is further configured to automatically remove, from the memory, objects that have not been accessed within a specified access interval.

13. The server of claim 11, wherein the server is further configured to automatically remove objects from the memory when it is determined that a specified number of objects are stored in the memory.

14. The server of claim 11, wherein the server is further configured to update an object stored in the memory in response to an update message from a system, said update message identifying the object to be updated.

15. The server of claim 11, further including a disk drive, wherein the server is further configured to store the serialized object to the disk drive.

16. The system of claim 15, wherein the serialized object stored to the disk drive includes a version number, wherein objects stored in the database each include a version number, and wherein upon a start-up of the cache server, the cache server retrieves the version number of the serialized object from the disk drive, requests the version number of the object from the database and compares the version number of the object from the disk drive with the version number from the database.

17. A method of rebuilding an object in an object cache server, comprising the steps, implemented in the cache server, of:

receiving an invalidation request, said invalidation request to invalidate an object on the cache server and identifying a first object in the cache server to be rebuilt;

rebuilding the first object; and

maintaining an original copy of the first object in the cache server as the cache server is rebuilding the first object, such that the cache server is able to provide the original copy in response to a request for the first object as the first object is being rebuilt.

18. The method of claim 17, further comprising sending the original copy of the first object to a requesting system in response to a request for the first object received while the first object is being rebuilt.

19. The method of claim 17, further comprising:

receiving a second invalidation request identifying the first object, said second invalidation request being received while the first object is being rebuilt; and

processing the second invalidation request after the first object has been rebuilt.

20. The method of claim 17, further comprising:

receiving a plurality of second invalidation requests identifying the first object while the first object is being rebuilt;

setting a flag in response to each second invalidation request; and

processing each second invalidation request in the order received.

21. The method of claim 20, wherein for each second invalidation request, processing includes:

rebuilding the object according to the second invalidation request;

maintaining a copy of the object in the cache server as it exists before being rebuilt; and

thereafter replacing the object with the rebuilt object.

22. The method of claim 17, further comprising after rebuilding the first object, replacing the original object in the cache server with the rebuilt object.

23. The method of claim 17, wherein the first object is a Java object.

24. The method of claim 17, further comprising maintaining an original copy of the first object in the cache server as the cache server is rebuilding the first object, such that the cache server is able to provide the original copy in response to a request for the first object as the first object is being rebuilt.

25. A method of providing an object from a cache server to a requesting system, the cache server being communicably coupled to an object database and one or more requesting systems, the method comprising the steps, implemented in a cache server, of:

receiving a request from a requesting system, the request identifying an object;

responsive to said request, determining whether the identified object is stored in the cache server; and

if the identified object is stored in the cache server;

sending the object to the requesting system; and

if the identified object is not stored in the cache server;

instantiating the identified object; and

sending the instantiated object to the requesting system; and

receiving an invalidation request from a requesting system to invalidate an object on the cache server and identifying an object to rebuild; and

rebuilding the identified object responsive to receiving the invalidation request.

26. The method of claim 25, wherein the object is a Java object.