CN106095698A - OO caching write, read method and device - Google Patents

Abstract

The invention relates to an object-oriented cache writing and reading method and device. The object-oriented cache write method includes: when a write request is received, calling a general object storage interface; determining the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and character to generate the key of the object to be written; serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class; through the general object The storage interface writes the stream to the cache based on the key. According to the present invention, the object-oriented language and the cache can be combined to realize direct access to objects in the object-oriented language, thereby greatly reducing the development workload, improving the portability and efficiency of development, and reducing the read and write load of the external storage device. Solve the bottleneck problem of read and write performance of external storage devices, thereby greatly improving system performance.

Description

Object-oriented cache writing and reading method and device

technical field

The invention relates to the technical field of caching, in particular to an object-oriented caching writing and reading method and device.

Background technique

For a large-scale Web (web page) system, the number of users is very large, resulting in a very high load on the server, so the disk read and write performance is low, and memory needs to be used as a cache to improve the performance of the entire system. The cache can directly provide services to most users, avoiding each request of users from accessing low-performance external storage devices, thereby improving the efficiency of the entire system. Therefore, caching is extremely important to improve the performance of the entire system.

Existing large-scale Web systems are usually developed using object-oriented languages. Object-oriented is a software development method, which refers to the use of encapsulation, inheritance and polymorphism in program design. Encapsulation refers to binding the properties and behavior of an object existing in the real world together and placing them in a logical unit. This logical unit is responsible for hiding the described attributes, and all access to the internal attributes of the object can only be realized through the provided user interface. Doing so can not only protect the object attributes, but also improve the maintainability of the software system. An object is anything that people want to study, ranging from simple integers to complex airplanes. It can not only represent specific things, but also represent abstract rules, plans or events. Objects have state, and an object uses data values to describe its state. Objects also have operations, which are used to change the state of the object, and the object and its operations are the behavior of the object. The object realizes the combination of data and operation, so that the data and operation are encapsulated in the unity of the object. A class is an abstraction of objects with the same characteristics and behavior. Therefore, a class is an abstraction of an object, and an object is the embodiment of a class. It can also be said that an object is an instance of a class. A class is actually a data type. For example, a parrot can be considered a class, and a specific parrot can be considered an object. A class has attributes, which are an abstraction of the state of an object, and the attributes of a class are described by a data structure. A class has an operation, which is an abstraction of the behavior of an object, described by the name of the operation and the method that implements the operation.

Cache refers to the buffer for data exchange. When a piece of hardware wants to read data, it will first search for the required data from the cache. If it finds it, it will execute it directly. If it cannot find it, it will search it from the next-level storage device. . Since the cache reads and writes much faster than the next-level storage device, the cache can help the entire system run faster. The working principle of caching is "locality of reference", including temporal locality and spatial locality. Time locality means that after a certain data is accessed once, it will be accessed again in a short time; spatial locality means that the CPU (Central Processing Unit, central processing unit) needs a certain data at a certain moment, Then it is likely that the next step will need data near it. For the application program, the locality of reference phenomenon will appear in both the instruction flow and the data flow. Since the reading and writing speed of the computer's memory is much faster than that of the hard disk, the data read from the hard disk can be temporarily stored in the memory, and there is no need to read from the hard disk again when using the data later. In this way, the overall reading and writing speed is greatly improved. This process is based on the locality principle cited above to use the memory as a hard disk cache.

Existing large-scale Web systems are usually developed using object-oriented languages, but the current caching technology cannot well meet the development needs of object-oriented systems. Specifically, when using caching technology in an object-oriented system, the protocol cannot be used universally among various classes, and developers need to design serialization and deserialization protocols for each class, and develop and deserialize each class separately. Debugging, resulting in a lot of time-consuming, error-prone, and low efficiency of the entire process.

Contents of the invention

technical problem

In view of this, the technical problem to be solved by the present invention is that the existing caching technology has poor adaptability in object-oriented systems, resulting in low development efficiency.

solution

In order to solve the above technical problems, according to an embodiment of the present invention, an object-oriented cache writing method is provided, including:

In the case of receiving a write request, call the general object storage interface;

Determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate a key of the object to be written according to the unique identifier;

Serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class;

Writing the stream into the cache according to the key through the common object storage interface.

For the above method, in a possible implementation manner, after writing the stream into the cache according to the key through the general object storage interface, the method further includes:

Write the stream to external storage according to the key.

For the above method, in a possible implementation manner, the object to be written is serialized into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, including:

determining all the parameter types specified in the preset protocol through the general object storage interface, and determining parameter values of all the parameter types corresponding to the object to be written;

Converting information of the preset protocol and parameter values of all parameter types corresponding to the object to be written into a stream through the general object storage interface according to the parameter format specified in the preset protocol.

For the above method, in a possible implementation manner, the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, all The name parameter of the method, the name parameter of the method of creating the object of the class to which the object belongs, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs.

In order to solve the above technical problems, according to another embodiment of the present invention, an object-oriented cache reading method is provided, including:

In the case of receiving a query request, determine the key corresponding to the query request through the general object query interface;

If the stream corresponding to the key is found from the cache through the general object query interface, deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can for deserialization of arbitrary classes;

Returning the object through the general object query interface to respond to the query request.

For the above method, in a possible implementation manner, after determining the key corresponding to the query request through the general object query interface, the method further includes:

If the stream corresponding to the key cannot be found from the cache through the general object query interface, then search for the stream corresponding to the key from an external storage device;

If the stream corresponding to the key is found from the external storage device, deserialize the stream into the object according to the parameter type and the parameter format stipulated in the preset protocol, and return the said object in response to said query request.

For the above method, in a possible implementation, the stream is deserialized into an object according to the parameter type and parameter format specified in the preset protocol, including:

Obtaining the information of the preset protocol from the stream, and determining the parameter type and the parameter format specified in the preset protocol according to the information of the preset protocol;

Deserialize the stream into the object according to the parameter type and the parameter format specified in the preset protocol, and all parameter values of the parameter type in the stream.

For the above method, in a possible implementation manner, the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, all The name parameter of the method, the name parameter of the method of creating the object of the class to which the object belongs, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs.

In order to solve the above technical problems, according to another embodiment of the present invention, an object-oriented cache writing device is provided, including:

A generic object storage interface calling module, configured to call the generic object storage interface when a write request is received;

A key generation module, configured to determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate the key of the object to be written according to the unique identifier;

A serialization module, configured to serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class;

A cache writing module, configured to write the stream into the cache according to the key through the common object storage interface.

For the above device, in a possible implementation manner, the device further includes:

An external storage device writing module, configured to write the stream into an external storage device according to the key.

For the above device, in a possible implementation manner, the serialization module includes:

A parameter value determining submodule, configured to determine all the parameter types specified in the preset protocol through the general object storage interface, and determine parameter values of all the parameter types corresponding to the object to be written;

The serialization submodule is used to store the information of the preset protocol and all the parameter types corresponding to the object to be written according to the parameter format stipulated in the preset protocol through the general object storage interface The parameter value is converted to a stream.

For the above device, in a possible implementation manner, the parameter type includes: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, all The name parameter of the method, the name parameter of the method of creating the object of the class to which the object belongs, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs.

In order to solve the above technical problems, according to another embodiment of the present invention, an object-oriented cache reading device is provided, including:

A key determination module, configured to determine the key corresponding to the query request through the general object query interface when the query request is received;

A deserialization module, configured to deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol if the stream corresponding to the key is found from the cache through the general object query interface , the preset protocol can be used for deserialization of any class;

The first query response module is configured to return the object through the general object query interface to respond to the query request.

For the above device, in a possible implementation manner, the device further includes:

A first search module, configured to search for the stream corresponding to the key from an external storage device if the stream corresponding to the key cannot be found from the cache through the general object query interface;

The second query response module is configured to deserialize the stream according to the parameter type and the parameter format stipulated in the preset protocol if the stream corresponding to the key is found from the external storage device for the object and return the object in response to the query request.

For the above device, in a possible implementation manner, the deserialization module includes:

A parameter type and format determining submodule, configured to obtain information of the preset protocol from the stream, and determine the parameter type and the parameter format specified in the preset protocol according to the information of the preset protocol ;

The deserialization submodule is used to deserialize the stream into the object.

For the above device, in a possible implementation manner, the parameter type includes: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, all The name parameter of the method, the name parameter of the method of creating the object of the class to which the object belongs, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs.

Beneficial effect

By encapsulating the general object storage interface and the general object query interface, setting a preset protocol that can be used for serialization and deserialization of any class, the object-oriented cache writing method, reading method and device according to the embodiment of the present invention can Combining the object-oriented language with the cache, the objects in the object-oriented language can be directly accessed through the encapsulated general object storage interface and general object query interface, thereby greatly reducing the development workload, improving the portability and efficiency of development, and enabling Reduce the read and write load of the external storage device, solve the bottleneck problem of the read and write performance of the external storage device, thereby greatly improving the system performance; when the object-oriented cache writing method, reading method and device of the embodiment of the present invention are applied to the server Under certain circumstances, the access speed of the server can be greatly improved, and higher concurrency can be supported, so that the number of servers required for the same amount of users is greatly reduced.

Other features and aspects of the present invention will become apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the invention and together with the description, serve to explain the principles of the invention.

FIG. 1 shows a flowchart of an implementation of an object-oriented cache writing method according to an embodiment of the present invention;

FIG. 2 shows a schematic diagram of another implementation flowchart of an object-oriented cache writing method according to an embodiment of the present invention;

FIG. 3 shows a schematic diagram of a specific implementation flowchart of step S103 of an object-oriented cache writing method according to an embodiment of the present invention;

FIG. 4 shows an implementation flowchart of an object-oriented cache reading method according to an embodiment of the present invention;

FIG. 5 shows a schematic diagram of another implementation flowchart of an object-oriented cache reading method according to an embodiment of the present invention;

FIG. 6 shows a schematic diagram of a specific implementation flowchart of deserializing a stream into an object according to the parameter type and parameter format specified in the preset protocol in step S402 of the object-oriented cache reading method according to an embodiment of the present invention;

FIG. 7 shows a structural block diagram of an object-oriented cache writing device according to an embodiment of the present invention;

FIG. 8 shows a structural block diagram of an object-oriented cache reading device according to an embodiment of the present invention;

FIG. 9 shows an exemplary structural block diagram of an object-oriented cache writing device according to an embodiment of the present invention;

Fig. 10 shows an exemplary structural block diagram of an object-oriented cache reading device according to an embodiment of the present invention.

detailed description

Various exemplary embodiments, features, and aspects of the invention will be described in detail below with reference to the accompanying drawings. The same reference numbers in the figures indicate functionally identical or similar elements. While various aspects of the embodiments are shown in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as superior or better than other embodiments.

In addition, in order to better illustrate the present invention, numerous specific details are given in the specific embodiments below. It will be understood by those skilled in the art that the present invention may be practiced without certain of the specific details. In some instances, methods, means, components and circuits well known to those skilled in the art have not been described in detail in order to highlight the gist of the present invention.

Example 1

FIG. 1 shows a flowchart of an implementation of an object-oriented cache writing method according to an embodiment of the present invention. As shown in Figure 1, the method mainly includes:

In step S101, when a write request is received, a common object storage interface is invoked.

It should be noted that the embodiment of the present invention can be applied to any system developed based on object-oriented language, for example, it can be applied to a background server of a website.

Wherein, the general object storage interface may be a general interface for storing objects of a class for external calling. Calling this common object storage interface can directly write objects of any class into the cache of the object-oriented system.

In the embodiment of the present invention, when the external interface receives a write request, the external interface calls the general object storage interface, so that the general object storage interface writes the object to be written corresponding to the write request into the cache.

In step S102, the unique identifier of the object to be written corresponding to the write request is determined through the common object storage interface, and a key of the object to be written is generated according to the unique identifier.

Wherein, the unique identifier of the object to be written can include an attribute name of the object to be written and the attribute value corresponding to the attribute name, and the object to be written can be uniquely determined according to the attribute value, so that the unique identifier can be as an access token. Generating the key of the object to be written according to the unique identifier may be: using the character string obtained by converting the unique identifier as the key of the object to be written.

In step S103, the object to be written is serialized into a stream through the universal object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class.

Wherein, the stream may be a byte stream or a character stream, which is not limited here. A byte stream is composed of bytes, and a character stream is composed of characters. In the embodiment of the present invention, the byte stream may refer to encapsulating the object to be written into a series of continuous bytes according to a preset protocol; the character stream may refer to encapsulating the object to be written into a series of continuous characters according to a preset protocol. A class can be any class defined in an object-oriented language, and an object is an instance of a class.

In the embodiment of the present invention, a general preset protocol that can be used for serialization of any class can be pre-designed, and the preset protocol can be called through a general object storage interface to implement writing objects in the cache. Since there is no need to design protocols for each class separately, the development workload is greatly reduced, and the convenience and efficiency of development are improved.

In step S104, the stream is written into the cache according to the key through the common object storage interface.

In this embodiment of the present invention, the cache may use memory as a storage device. The cache can be stored in a key-value pair, and a hash table can be used as a data structure. The key can be an arbitrary string, and the value can also be an arbitrary string. A key corresponds to a value. The hash table can determine the storage location of the value according to the key, thus realizing constant level search, update and deletion. In this embodiment of the present invention, the value in the key-value pair may refer to a stream.

Wherein, step S104 may specifically be: write the stream into the cache based on the hash algorithm based on the key through the common object storage interface.

The embodiment of the present invention encapsulates the process of writing objects into the cache as a general object storage interface, and calling the general object storage interface can directly write objects of classes in an object-oriented language into the cache.

In a possible implementation manner, before step S101, the method further includes: instantiating the class, generating an object to be written, and assigning values to the object to be written according to each attribute defined by the class.

FIG. 2 shows a schematic diagram of another implementation flowchart of an object-oriented cache writing method according to an embodiment of the present invention. As shown in Figure 2, the method mainly includes:

In step S201, in the case of receiving a write request, call the common object storage interface;

In step S202, determine the unique identifier of the object to be written corresponding to the write request through the common object storage interface, and generate the key of the object to be written according to the unique identifier;

In step S203, serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class;

In step S204, the stream is written into the cache according to the key through the common object storage interface;

In step S205, the stream is written to the external storage device according to the key.

In a possible implementation manner, after the stream is written into the cache according to the key through the common object storage interface, the stream is written into the external storage device according to the key. Here, the external storage device may be a hard disk, which is not limited here. External storage devices are used to store data permanently.

FIG. 3 shows a schematic diagram of a specific implementation flowchart of step S103 of the object-oriented cache writing method according to an embodiment of the present invention. As shown in Figure 3, the object to be written is serialized into a stream through the general object storage interface according to the parameter type and parameter format stipulated in the preset protocol, including:

In step S301, determine all parameter types specified in the preset protocol through the common object storage interface, and determine parameter values of all parameter types corresponding to the object to be written;

In step S302, the information of the preset protocol and parameter values of all parameter types corresponding to the object to be written are converted into a stream through the common object storage interface according to the parameter format specified by the preset protocol.

Wherein, the information of the preset protocol may include the identifier of the preset protocol and the version number of the preset protocol. The parameter format can include the order of the individual parameters in the stream. The parameter format may also include a coding standard of the parameter, for example, the coding standard of the parameter is ASCII (American Standard Code for Information Interchange, American Standard Code for Information Interchange).

In a possible implementation, the parameter types include: name parameters of the class to which the object belongs, name parameters of all attributes of the object, parameters of all attribute values of the object, name parameters of all methods of the object, and parameters of the class to which the object belongs The name parameter of the method, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs, etc.

For example, the parameters of the object to be written include: the name of the class to which the object to be written belongs, all attribute names of the object to be written, all attribute values of the object to be written, names of all methods of the object to be written, The name of the method for creating the object to be written by the class described in the input object, all attribute names of the class to which the object to be written belongs, and all attribute values of the class to which the object to be written belongs.

In this way, by encapsulating the common object storage interface and setting a preset protocol that can be used for serialization of any class, the object-oriented cache writing method according to the embodiment of the present invention can combine the object-oriented language with the cache, and can pass the encapsulation The universal object storage interface enables direct writing of objects in object-oriented languages, thereby greatly reducing the development workload, improving the portability and efficiency of development, reducing the read and write load of external storage devices, and solving the read and write performance bottleneck of external storage devices problems, thereby greatly improving system performance; when the object-oriented cache writing method of the embodiment of the present invention is applied to the server side, the access speed of the server can be greatly improved, and higher concurrency can be supported, so that the same amount of users needs The number of servers is greatly reduced.

Example 2

FIG. 4 shows a flowchart of an implementation of an object-oriented cache reading method according to an embodiment of the present invention. As shown in Figure 4, the method mainly includes:

In step S401, when a query request is received, the key corresponding to the query request is determined through the general object query interface.

Wherein, the general object query interface may be a general interface for querying objects of a class according to a query request for external calls. Calling the general object query interface can directly query and obtain objects from the object-oriented cache according to the query request, that is, the result returned by the general object query interface is an object. This generic object query interface supports queries on arbitrary classes.

In the embodiment of the present invention, determining the key corresponding to the query request through the general object query interface may be: determining the query condition corresponding to the query request through the general object query interface, and determining the key corresponding to the query condition according to a pre-stored mapping list.

In step S402, if the stream corresponding to the key is found from the cache through the general object query interface, the stream is deserialized into an object according to the parameter type and parameter format specified in the preset protocol. The preset protocol can be used for any type of Deserialize.

After the key corresponding to the query request is determined through the general object query interface, the key is searched in the cache based on the hash algorithm through the general object query interface.

In the embodiment of the present invention, a general preset protocol that can be used for deserialization of any class can be pre-designed, and the preset protocol can be called through a general object query interface to realize querying objects in the cache. Since there is no need to design protocols for each class separately, the development workload is greatly reduced, and the convenience and efficiency of development are improved.

In step S403, the object is returned through the common object query interface to respond to the query request.

In the embodiment of the present invention, after the stream is deserialized into an object through the general object query interface, the general object query interface provides the object to the external interface.

In the embodiment of the present invention, by encapsulating the process of obtaining streams from the cache and deserializing them into objects as a general object query interface, calling the general object query interface can directly read objects of classes in object-oriented languages from the cache.

FIG. 5 shows a schematic diagram of another implementation flowchart of an object-oriented cache reading method according to an embodiment of the present invention. As shown in Figure 5, the method mainly includes:

In step S501, when a query request is received, the key corresponding to the query request is determined through the general object query interface.

In step S502, if the stream corresponding to the key is found from the cache through the general object query interface, the stream is deserialized into an object according to the parameter type and parameter format specified in the preset protocol. The preset protocol can be used for any type of Deserialize.

In step S503, the object is returned through the common object query interface to respond to the query request.

In step S504, if the stream corresponding to the key cannot be found from the cache through the general object query interface, the stream corresponding to the key is searched from an external storage device.

In step S505, if the stream corresponding to the key is found from the external storage device, the stream is deserialized into an object according to the parameter type and format specified in the preset protocol, and the object is returned to respond to the query request.

Fig. 6 shows a schematic diagram of a specific implementation flowchart of deserializing a stream into an object according to the parameter type and parameter format specified in the preset protocol in step S402 of the object-oriented cache reading method according to an embodiment of the present invention. As shown in Figure 6, deserialize the stream into an object according to the parameter type and parameter format stipulated in the preset protocol, including:

In step S601, the information of the preset protocol is obtained from the stream, and the parameter type and parameter format specified by the preset protocol are determined according to the information of the preset protocol;

In step S602, the stream is deserialized into an object according to the parameter type and parameter format stipulated in the preset protocol, and parameter values of all parameter types in the stream.

Wherein, the information of the preset protocol may include the identifier of the preset protocol and the version number of the preset protocol. According to the identifier of the preset protocol and the version number of the preset protocol, the parameter type and parameter format specified in the preset protocol can be determined, so that all parameter types and parameter formats in the stream can be determined.

In a possible implementation, the parameter types include: name parameters of the class to which the object belongs, name parameters of all attributes of the object, parameters of all attribute values of the object, name parameters of all methods of the object, and parameters of the class to which the object belongs The name parameter of the method, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs, etc.

In this way, by encapsulating the general object query interface and setting a preset protocol that can be used for deserialization of any class, the object-oriented cache reading method according to the embodiment of the present invention can combine the object-oriented language with the cache, and can pass the general The object query interface can directly read the objects in the object-oriented language, thereby greatly reducing the development workload, improving the portability and efficiency of development, reducing the read and write load of external storage devices, and solving the bottleneck problem of the read and write performance of external storage devices , thereby greatly improving system performance; when the object-oriented cache reading method of the embodiment of the present invention is applied to the server side, the access speed of the server can be greatly improved, and higher concurrency can be supported, so that the server required by the same amount of users The number is greatly reduced.

Example 3

Fig. 7 shows a structural block diagram of an object-oriented cache writing device according to an embodiment of the present invention. The device may be a server, or other cache writing device, which is not limited here. For ease of description, only parts related to the embodiments of the present invention are shown. As shown in Figure 7, the device includes:

A general object storage interface calling module 71, configured to call the general object storage interface when a write request is received;

The key generation module 72 is used to determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate the key of the object to be written according to the unique identifier;

The serialization module 73 is used to serialize the object to be written into a stream according to the parameter type and parameter format specified in the preset protocol through the general object storage interface, and the preset protocol can be used for serialization of any class;

The cache writing module 74 is configured to write the stream into the cache according to the key through the common object storage interface.

In a possible implementation manner, the device further includes:

The external storage device writing module 75 is configured to write the stream into the external storage device according to the key.

In a possible implementation, the serialization module 73 includes:

The parameter value determination sub-module 731 is used to determine all parameter types specified in the preset protocol through the common object storage interface, and determine the parameter values of all parameter types corresponding to the object to be written;

The serialization sub-module 732 is configured to convert the information of the preset protocol and the parameter values of all parameter types corresponding to the object to be written into a stream through the common object storage interface according to the parameter format specified by the preset protocol.

In a possible implementation, the parameter types include: name parameters of the class to which the object belongs, name parameters of all attributes of the object, parameters of all attribute values of the object, name parameters of all methods of the object, and parameters of the class to which the object belongs The name parameter of the method, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs, etc.

In this way, by encapsulating the general object storage interface and setting a preset protocol that can be used for serialization of any class, the object-oriented cache writing device according to the embodiment of the present invention can combine the object-oriented language with the cache, and can pass the encapsulated The universal object storage interface enables direct writing of objects in object-oriented languages, thereby greatly reducing the development workload, improving the portability and efficiency of development, reducing the read and write load of external storage devices, and solving the read and write performance bottleneck of external storage devices problems, thereby greatly improving system performance; when the object-oriented cache writing device of the embodiment of the present invention is applied to the server side, the access speed of the server can be greatly improved, and higher concurrency can be supported, so that the same amount of users needs The number of servers is greatly reduced.

Example 4

Fig. 8 shows a structural block diagram of an object-oriented cache reading device according to an embodiment of the present invention. The device may be a server, or other cache reading device, which is not limited here. For ease of description, only parts related to the embodiments of the present invention are shown. As shown in Figure 8, the device includes:

A key determination module 81, configured to determine the key corresponding to the query request through the general object query interface when the query request is received;

The deserialization module 82 is used to deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol if the stream corresponding to the key is found from the cache through the general object query interface. The preset protocol can be used for Deserialization of arbitrary classes;

The first query response module 83 is configured to return objects through the common object query interface to respond to query requests.

In a possible implementation manner, the device further includes:

The first search module 84 is used to find the stream corresponding to the key from the external storage device if the stream corresponding to the key cannot be found from the cache through the general object query interface;

The second query response module 85 is configured to deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol if the stream corresponding to the key is found from the external storage device, and return the object to respond to the query request .

In a possible implementation, the deserialization module 82 includes:

The parameter type and format determination submodule 821 is used to obtain the information of the preset protocol from the stream, and determine the parameter type and parameter format specified in the preset protocol according to the information of the preset protocol;

The deserialization submodule 822 is configured to deserialize the stream into an object according to the parameter type and parameter format stipulated in the preset protocol, and the parameter values of all parameter types in the stream.

In a possible implementation, the parameter types include: name parameters of the class to which the object belongs, name parameters of all attributes of the object, parameters of all attribute values of the object, name parameters of all methods of the object, and parameters of the class to which the object belongs The name parameter of the method, all the attribute name parameters of the class to which the object belongs, and all the attribute value parameters of the class to which the object belongs, etc.

In this way, by encapsulating the general object query interface and setting a preset protocol that can be used for deserialization of any class, the object-oriented cache reading device according to the embodiment of the present invention can combine the object-oriented language with the cache, and can pass the general The object query interface can directly read the objects in the object-oriented language, thereby greatly reducing the development workload, improving the portability and efficiency of development, reducing the read and write load of external storage devices, and solving the bottleneck problem of the read and write performance of external storage devices , thereby greatly improving system performance; when the object-oriented cache reading device of the embodiment of the present invention is applied to the server side, the access speed of the server can be greatly improved, and higher concurrency can be supported, so that the server required by the same amount of users The number is greatly reduced.

Example 5

FIG. 9 shows an exemplary structural block diagram of an object-oriented cache writing device according to another embodiment of the present invention. The object-oriented cache writing apparatus 1100 may be a host server with computing capabilities, a personal computer PC, or a portable portable computer or terminal. The specific embodiments of the present invention do not limit the specific implementation of the computing nodes.

The object-oriented cache writing device 1100 includes a processor (processor) 1110 , a communication interface (Communications Interface) 1120 , a memory (memory) 1130 and a bus 1140 . Wherein, the processor 1110 , the communication interface 1120 , and the memory 1130 communicate with each other through the bus 1140 .

The communication interface 1120 is used for communicating with network devices, where the network devices include, for example, a virtual machine management center, shared storage, and the like.

The processor 1110 is used to execute programs. The processor 1110 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

The storage 1130 is used for storing files. The memory 1130 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Memory 1130 may also be a memory array. The storage 1130 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

In a possible implementation manner, the above program may be a program code including computer operation instructions. Specifically, the program may contain instructions to:

In the case of receiving a write request, call the general object storage interface;

Determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate a key of the object to be written according to the unique identifier;

Serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class;

Writing the stream into the cache according to the key through the common object storage interface.

Assuming that the above is the first possible implementation manner, in the second possible implementation manner provided on the basis of the first possible implementation manner, the program may further include instructions for performing the following operations:

After writing the stream into the cache according to the key through the common object storage interface, write the stream into an external storage device according to the key.

In a third possible implementation manner provided on the basis of the first possible implementation manner, the program may further include instructions for performing the following operations:

Serialize the object to be written into a stream according to the parameter type and parameter format specified in the preset protocol through the general object storage interface, including:

determining all the parameter types specified in the preset protocol through the general object storage interface, and determining parameter values of all the parameter types corresponding to the object to be written;

Converting information of the preset protocol and parameter values of all parameter types corresponding to the object to be written into a stream through the general object storage interface according to the parameter format specified in the preset protocol.

In the fourth possible implementation manner provided based on the first, second or third possible implementation manner, the program may further include instructions for performing the following operations:

The parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, name parameters of all methods of the object, and the creation parameters of the class to which the object belongs Name parameters of the method of the object, all attribute name parameters of the class to which the object belongs, and all attribute value parameters of the class to which the object belongs.

Example 6

FIG. 10 shows an exemplary structural block diagram of an object-oriented cache reading device according to another embodiment of the present invention. The object-oriented cache reading device 1200 may be a host server with computing capabilities, a personal computer PC, or a portable portable computer or terminal. The specific embodiments of the present invention do not limit the specific implementation of the computing nodes.

The object-oriented cache reading device 1200 includes a processor 1210 , a communication interface 1220 , a memory 1230 and a bus 1240 . Wherein, the processor 1210 , the communication interface 1220 , and the memory 1230 communicate with each other through the bus 1240 .

The communication interface 1220 is used for communicating with network devices, where the network devices include, for example, a virtual machine management center, shared storage, and the like.

The processor 1210 is used to execute programs. Processor 1210 may be a central processing unit CPU, or an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present invention.

The storage 1230 is used to store files. The memory 1230 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. Memory 1230 may also be a memory array. The storage 1230 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

In a possible implementation manner, the above program may be a program code including computer operation instructions. Specifically, the program may contain instructions to:

In the case of receiving a query request, determine the key corresponding to the query request through the general object query interface;

If the stream corresponding to the key is found from the cache through the general object query interface, deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can for deserialization of arbitrary classes;

Returning the object through the general object query interface to respond to the query request.

Assuming that the above is the first possible implementation manner, in the second possible implementation manner provided on the basis of the first possible implementation manner, the program may further include instructions for performing the following operations:

After the key corresponding to the query request is determined through the general object query interface, if the stream corresponding to the key cannot be found from the cache through the general object query interface, then the key corresponding to the key is searched from the external storage device. flow;

If the stream corresponding to the key is found from the external storage device, deserialize the stream into the object according to the parameter type and the parameter format stipulated in the preset protocol, and return the said object in response to said query request.

In the fourth possible implementation manner provided based on the first or second possible implementation manner, the program may further include instructions for performing the following operations:

Deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol, including:

Obtaining the information of the preset protocol from the stream, and determining the parameter type and the parameter format specified in the preset protocol according to the information of the preset protocol;

Deserialize the stream into the object according to the parameter type and the parameter format specified in the preset protocol, and all parameter values of the parameter type in the stream.

In the fourth possible implementation manner provided based on the first or second possible implementation manner, the program may further include instructions for performing the following operations:

The parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, name parameters of all methods of the object, and the creation parameters of the class to which the object belongs Name parameters of the method of the object, all attribute name parameters of the class to which the object belongs, and all attribute value parameters of the class to which the object belongs.

Those skilled in the art can appreciate that each exemplary module and algorithm steps in the embodiments described herein can be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in the form of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may choose different methods to implement the described functions for specific applications, but this implementation should not be regarded as exceeding the scope of the present invention.

If the functions are implemented in the form of computer software and sold or used as an independent product, it can be considered that all or part of the technical solution of the present invention (such as the part that contributes to the prior art) is In the form of computer software products. The computer software product is usually stored in a computer-readable non-volatile storage medium, and includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all the methods of the various embodiments of the present invention. or partial steps. The aforementioned storage medium includes various media capable of storing program codes such as U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (16)

1. An object-oriented cache write method, characterized in that, comprising: In the case of receiving a write request, call the general object storage interface; Determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate a key of the object to be written according to the unique identifier; Serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class; Writing the stream into the cache according to the key through the common object storage interface. 2. The method according to claim 1, wherein after writing the stream into the cache according to the key through the general object storage interface, the method further comprises: Write the stream to external storage according to the key. 3. The method according to claim 1, wherein serializing the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol includes: determining all the parameter types specified in the preset protocol through the general object storage interface, and determining parameter values of all the parameter types corresponding to the object to be written; Converting information of the preset protocol and parameter values of all parameter types corresponding to the object to be written into a stream through the general object storage interface according to the parameter format specified in the preset protocol. 4. The method according to any one of claims 1 to 3, wherein the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, and all attribute values of the object Parameters, name parameters of all methods of the object, name parameters of the class to which the object belongs parameter. 5. An object-oriented cache reading method, comprising: In the case of receiving a query request, determine the key corresponding to the query request through the general object query interface; If the stream corresponding to the key is found from the cache through the general object query interface, deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can for deserialization of arbitrary classes; Returning the object through the general object query interface to respond to the query request. 6. The method according to claim 5, characterized in that, after the key corresponding to the query request is determined through the general object query interface, the method further comprises: If the stream corresponding to the key cannot be found from the cache through the general object query interface, then search for the stream corresponding to the key from an external storage device; If the stream corresponding to the key is found from the external storage device, deserialize the stream into the object according to the parameter type and the parameter format stipulated in the preset protocol, and return the said object in response to said query request. 7. The method according to claim 5 or 6, wherein deserializing the stream into an object according to the parameter type and parameter format stipulated in the preset protocol includes: Obtaining the information of the preset protocol from the stream, and determining the parameter type and the parameter format specified in the preset protocol according to the information of the preset protocol; Deserialize the stream into the object according to the parameter type and the parameter format specified in the preset protocol, and all parameter values of the parameter type in the stream. 8. The method according to claim 5 or 6, wherein the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, the Name parameters of all methods of the object, name parameters of methods for creating the object of the class to which the object belongs, name parameters of all attributes of the class to which the object belongs, and all attribute value parameters of the class to which the object belongs. 9. An object-oriented cache writing device, characterized in that, comprising: A generic object storage interface calling module, configured to call the generic object storage interface when a write request is received; A key generation module, configured to determine the unique identifier of the object to be written corresponding to the write request through the general object storage interface, and generate the key of the object to be written according to the unique identifier; A serialization module, configured to serialize the object to be written into a stream through the general object storage interface according to the parameter type and parameter format specified in the preset protocol, and the preset protocol can be used for serialization of any class; A cache writing module, configured to write the stream into the cache according to the key through the common object storage interface. 10. The device according to claim 9, further comprising: An external storage device writing module, configured to write the stream into an external storage device according to the key. 11. The device according to claim 9, wherein the serialization module comprises: A parameter value determining submodule, configured to determine all the parameter types specified in the preset protocol through the general object storage interface, and determine parameter values of all the parameter types corresponding to the object to be written; The serialization submodule is used to store the information of the preset protocol and all the parameter types corresponding to the object to be written according to the parameter format stipulated in the preset protocol through the general object storage interface The parameter value is converted to a stream. 12. The device according to any one of claims 9 to 11, wherein the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, and all attribute values of the object Parameters, name parameters of all methods of the object, name parameters of the class to which the object belongs parameter. 13. An object-oriented cache reading device, comprising: A key determination module, configured to determine the key corresponding to the query request through the general object query interface when the query request is received; A deserialization module, configured to deserialize the stream into an object according to the parameter type and parameter format specified in the preset protocol if the stream corresponding to the key is found from the cache through the general object query interface , the preset protocol can be used for deserialization of any class; The first query response module is configured to return the object through the general object query interface to respond to the query request. 14. The device according to claim 13, further comprising: A first search module, configured to search for the stream corresponding to the key from an external storage device if the stream corresponding to the key cannot be found from the cache through the general object query interface; The second query response module is configured to deserialize the stream according to the parameter type and the parameter format stipulated in the preset protocol if the stream corresponding to the key is found from the external storage device for the object and return the object in response to the query request. 15. The device according to claim 13 or 14, wherein the deserialization module comprises: A parameter type and format determining submodule, configured to obtain information of the preset protocol from the stream, and determine the parameter type and the parameter format specified in the preset protocol according to the information of the preset protocol ; The deserialization submodule is used to deserialize the stream into the object. 16. The device according to claim 13 or 14, wherein the parameter types include: the name parameter of the class to which the object belongs, all attribute name parameters of the object, all attribute value parameters of the object, the Name parameters of all methods of the object, name parameters of methods for creating the object of the class to which the object belongs, name parameters of all attributes of the class to which the object belongs, and all attribute value parameters of the class to which the object belongs.