Cloud-native content management systems, methods, devices, and storage media
By deploying a cloud-native content management system in a Kubernetes cluster, and utilizing the combination of MinIO and Elasticsearch to manage different types of content, the problem of low efficiency in traditional systems under high concurrency is solved, and the efficient and stable operation and fast query of the content management system are achieved.
Patent Information
- Application Number
- CN202310633494.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-05-31
AI Technical Summary
Under high business concurrency, traditional content management systems struggle to maintain efficient operation, impacting content publishing and access efficiency.
We employ a cloud-native content management system deployed on a Kubernetes cluster. We utilize the MinIO storage system and the Elasticsearch search engine to manage different types of content, and store and query content through the interfaces of the MinIO client and the Elasticsearch client, optimizing the database structure.
It improves the stability and efficiency of the content management system under high concurrency, ensures fast access and retrieval of different types of content, and enhances the user experience.
Smart Images

Figure CN117009031B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of cloud computing technology, and in particular to a cloud-native content management system, method, device, and storage medium. Background Technology
[0002] A Content Management System (CMS) is a software system that sits between the web front-end and back-end office systems or processes.
[0003] Content creators, editors, and publishers use CMS to submit, modify, approve, and publish content. Even with high user traffic and concurrency, CMS maintains high efficiency, which is crucial for improving the work efficiency of both content publishers and users. Summary of the Invention
[0004] This invention provides a cloud-native content management system, method, device, and storage medium that can ensure the efficient operation of the content management system under high business concurrency.
[0005] According to one aspect of the present invention, a cloud-native content management system is provided, deployed on at least one worker node of a Kubernetes cluster, comprising: a business logic layer and a data layer;
[0006] The business logic layer, including the MinIO client and the Elasticsearch client, is used to respond to user content addition requests and store the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client.
[0007] The data layer, comprising the MinIO storage system and the Elasticsearch search engine, is used to store the content to be added via at least one of the MinIO storage system and the Elasticsearch search engine.
[0008] Optional, business logic layer, specifically used for:
[0009] Respond to the user's content addition request and determine the data type of the content to be added associated with the content addition request;
[0010] If the data type of the content to be added is text, the Elasticsearch client's first storage addition interface is called through the content addition interface to store the content to be added in the Elasticsearch search engine in the data layer.
[0011] When the data type of the content to be added is an object, the content addition interface calls the second storage addition interface provided by the MinIO client to store the content to be added in the MinIO storage system in the data layer. The storage address of the content in the MinIO storage system is then stored in the Elasticsearch search engine. The business logic layer, by calling the storage addition interfaces provided by the MinIO client and the Elasticsearch client, stores the content to be added in the MinIO storage system and the Elasticsearch search engine in the data layer. This allows for backend maintenance of information displayed on the frontend, optimizes the database structure of traditional content management systems, and improves the efficiency of adding content.
[0012] Optional, cloud-native content management systems also include:
[0013] The presentation layer is used to display the content stored in the MinIO storage system and the Elasticsearch search engine from the front end. Through the presentation layer, the stored content can be displayed, providing users accessing the content management system with an intuitive view of the content.
[0014] Optionally, the business logic layer is also used for:
[0015] Respond to the user's content display request and determine the data type of the content to be displayed associated with the content display request;
[0016] If the data type of the content to be displayed is text, the content to be displayed is queried in the Elasticsearch search engine in the data layer through the content query interface, and then sent to the presentation layer.
[0017] When the data type of the content to be displayed is an object, the content query interface searches the Elasticsearch search engine in the data layer for the storage address of the content in the MinIO storage system. Then, it retrieves the content from the MinIO storage system using that storage address and sends it to the presentation layer. When the business logic layer receives a content display request, it queries either the Elasticsearch search engine or the MinIO storage system based on the data type of the content to be displayed. This ensures fast content retrieval and rendering, improving the user experience of the content management system.
[0018] Optionally, a Kubernetes cluster includes at least one master node and at least one worker node;
[0019] The master node is used to control the number of worker nodes and the number of containers in the worker nodes in the Kubernetes cluster based on the business concurrency.
[0020] The worker nodes include a first container group for deploying the business logic layer, a second container group for deploying the MinIO storage system, a third container group for deploying the Elasticsearch search engine, a fourth container group for deploying the front-end services of the presentation layer, and a fifth container group for deploying the back-end services of the presentation layer. By deploying the content management system on at least one worker node in the Kubernetes cluster, on the one hand, in the event of a worker node failure, the business of the failed node can be transferred to other worker nodes to continue execution, ensuring high system availability; on the other hand, when there is an explosive increase in user traffic, the number of worker nodes or the number of containers within worker nodes can be increased to ensure the stability of system operation.
[0021] According to another aspect of the present invention, a cloud-native content management method is provided, applied to the cloud-native content management system described in any embodiment of the present invention, comprising:
[0022] The business logic layer responds to the user's content addition request by storing the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client;
[0023] The data layer stores the data to be added using at least one of the MinIO storage system and the Elasticsearch search engine.
[0024] Optionally, the business logic layer responds to the user's content addition request by storing the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client, including:
[0025] The business logic layer responds to the user's content addition request and determines the data type of the content to be added associated with the content addition request;
[0026] When the data type of the content to be added is text, the business logic layer calls the first storage addition interface provided by the Elasticsearch client through the content addition interface to store the content to be added in the Elasticsearch search engine in the data layer.
[0027] When the data type of the content to be added is an object, the business logic layer calls the second storage add interface provided by the MinIO client through the content add interface to store the content to be added in the MinIO storage system in the data layer, and then stores the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine. When adding content, the business logic layer optimizes the database structure of traditional content management systems by calling the storage add interfaces provided by the MinIO client and the Elasticsearch client, thereby improving the efficiency of content addition.
[0028] Optional, cloud-native content management methods also include:
[0029] The business logic layer responds to the user's content display request and determines the data type of the content to be displayed associated with the content display request;
[0030] When the data type of the content to be displayed is text, the business logic layer queries the Elasticsearch search engine in the data layer through the content query interface and sends the content to be displayed to the presentation layer.
[0031] When the data type of the content to be displayed is an object, the business logic layer queries the Elasticsearch search engine in the data layer for the storage address of the content to be displayed in the MinIO storage system through the content query interface, and then queries the MinIO storage system for the content to be displayed through the storage address, and sends the content to be displayed to the presentation layer.
[0032] The presentation layer displays the content sent by the business logic layer. When the business logic layer receives a content display request, it queries the Elasticsearch search engine or the MinIO storage system based on the data type of the content to be displayed. This ensures fast query speed and rapid rendering of the content, improving the user experience of the content management system.
[0033] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:
[0034] At least one processor; and
[0035] A memory that is communicatively connected to at least one processor; wherein,
[0036] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to execute the cloud-native content management method of any embodiment of the present invention.
[0037] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute and implement the cloud-native content management method of any embodiment of the present invention.
[0038] The technical solution of this invention, by deploying the content management system on at least one worker node in a Kubernetes cluster, can ensure system stability even under surges in user traffic by increasing the number of worker nodes or the number of containers within those worker nodes. The business logic layer includes a MinIO client and an Elasticsearch client. Upon receiving content to be stored, text-type content can be stored in the Elasticsearch search engine, while object-type content can be stored in the MinIO storage system. This leverages the advantages of both the Elasticsearch search engine and the MinIO storage system to improve the efficiency of the content management system in managing different types of content.
[0039] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description
[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0041] Figure 1a This is a schematic diagram of the structure of a cloud-native content management system provided in an embodiment of the present invention;
[0042] Figure 1b This is an operating environment for a cloud-native content management system provided according to an embodiment of the present invention;
[0043] Figure 2 This is a schematic diagram of the structure of a cloud-native content management system provided in an embodiment of the present invention;
[0044] Figure 3 This is a flowchart of a cloud-native content management method provided according to an embodiment of the present invention;
[0045] Figure 4 This is a flowchart of a cloud-native content management method provided according to an embodiment of the present invention;
[0046] Figure 5 This is a schematic diagram of the structure of an electronic device that implements the cloud-native content management method of this invention. Detailed Implementation
[0047] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0048] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0049] Figure 1a This invention provides a schematic diagram of the structure of a cloud-native content management system, which is applicable to situations where a highly available content management system is built based on containerized applications. The cloud-native content management system is deployed on at least one worker node 100 of a Kubernetes cluster, and includes a business logic layer 110 and a data layer 120.
[0050] The business logic layer 110 includes a MinIO client 111 and an Elasticsearch client 112, which are used to respond to user content addition requests and store the content to be added to the data layer 120 through at least one of the MinIO client 111 and the Elasticsearch client 112.
[0051] The business logic layer 110 is based on the Spring Cloud framework and includes the MinIO client 111 and the Elasticsearch client 112. Specifically, the business logic layer 110 can be divided according to the types of content the content management system needs to manage. For example, for enterprise businesses using this content management system, it provides homepage management, title management, and content management. Homepage management can include a homepage query interface for querying the homepage, a homepage add interface for adding content to the homepage, a homepage modify interface for modifying homepage content, and a homepage delete interface for deleting homepage content. Similarly, title management can include a title query interface, a title add interface, a title modify interface, and a title delete interface; content management can also include a content query interface, a content add interface, a content modify interface, and a content delete interface.
[0052] In addition, the business logic layer 110 also includes storage addition and storage deletion interfaces provided by the MinIO client 111 and the Elasticsearch client 112, which are used to instruct the data layer 120 to store and delete content.
[0053] When the business logic layer 110 receives a user's content addition request, it stores the content to be added in the data layer 120 using at least one of the MinIO client 111 and the Elasticsearch client 112. Specifically, upon receiving the user's content addition request, the business logic layer 110 can first determine the data type of the content to be added associated with the content addition request. If the content to be added is a text type, such as text or data, it is stored in the data layer 120 using the Elasticsearch client 112 to ensure fast access to text-type content; if the content to be added is an object type, such as an image or video, it is stored in the data layer 120 using the MinIO client 111 to achieve fast access to object-type data.
[0054] Optional, business logic layer 110, specifically used for:
[0055] Respond to the user's content addition request and determine the data type of the content to be added associated with the content addition request;
[0056] If the data type of the content to be added is text, the first storage addition interface provided by the Elasticsearch client 112 is called through the content addition interface to store the content to be added in the Elasticsearch search engine 122 in the data layer 120.
[0057] If the data type of the content to be added is an object, the second storage addition interface provided by the MinIO client 111 is called through the content addition interface to store the content to be added in the MinIO storage system 121 in the data layer 120, and the storage address of the content to be added in the MinIO storage system 121 is stored in the Elasticsearch search engine 122.
[0058] In this optional embodiment, when the business logic layer 110 receives a content addition request initiated by a user, it first reads the content to be added contained in the content addition request, and then determines the data type of the content to be added. For example, the content to be added can be text, data, images, audio, and video. Different storage methods can be used to store the content to be added for different data types.
[0059] Specifically, when the data type of the content to be added is text, data, or other text-based types, the content addition interface in the business logic layer 110 calls the first storage addition interface provided by the Elasticsearch client 112 to store the content to be added in the Elasticsearch search engine 122 in the data layer 120. By calling the first storage addition interface provided by the Elasticsearch client 112 to store text-based content, efficient storage and retrieval of the content to be added can be achieved. The content addition interface can be a homepage addition interface for the homepage, a title addition interface for titles, or a content addition interface for content under titles.
[0060] When the data type of the content to be added is an object such as an image, audio, or video, the content addition interface in the business logic layer 110 calls the second storage addition interface provided by the MinIO client 111 to store the content to be added in the MinIO storage system 121 in the data layer 120. Simultaneously, the storage address of the content to be added in the MinIO storage system 121 is stored in the Elasticsearch search engine 122. Through this storage method, on the one hand, the advantage of the MinIO storage system 121 in storing large volumes of unstructured data can be utilized to achieve efficient storage and retrieval of object-type content to be added; on the other hand, storing the address of the object-type content to be added in the MinIO storage system 121 in the Elasticsearch search engine 122 can leverage the efficient retrieval advantages of the Elasticsearch search engine 122 to quickly locate the position of the content to be added in the MinIO storage system 121, ensuring fast content querying and rendering.
[0061] Data layer 120 includes a MinIO storage system 121 and an Elasticsearch search engine 122 for storing content to be added via at least one of the MinIO storage system 121 and the Elasticsearch search engine 122.
[0062] In this embodiment of the invention, the cloud-native content management system further includes a data layer 120, which includes a MinIO storage system 121 and an Elasticsearch search engine 122. The data layer 120 is used to store content to be added through at least one of the MinIO storage system 121 and the Elasticsearch search engine 122. Specifically, the data layer 120 can store object-type content through the MinIO storage system 121, leveraging the advantages of the MinIO storage system 121 in storing large volumes of unstructured data to achieve fast storage and retrieval of object-type content to be added. It can also store text-type content through the Elasticsearch search engine 122, leveraging the advantages of the Elasticsearch search engine 122 in storing and retrieving text-type content to achieve fast storage and retrieval of text-type content to be added.
[0063] Optionally, a Kubernetes cluster includes at least one master node and at least one worker node (100).
[0064] Master node 140 is used to control the number of worker nodes 100 and the number of containers in worker nodes 100 based on business concurrency.
[0065] Worker node 100 includes a first container group 101 for deploying the business logic layer 110, a second container group 102 for deploying the MinIO storage system 121, a third container group 103 for deploying the Elasticsearch search engine 122, a fourth container group 104 for deploying the front-end services of the presentation layer, and a fifth container group 105 for deploying the back-end services of the presentation layer.
[0066] The cloud-native content management system provided in this embodiment of the invention operates in a Kubernetes cluster comprising at least one master node 140 and at least one worker node 100. Each worker node 100 includes multiple container groups (pods), and each container group includes at least one container. The master node 140 manages at least one worker node 100 in Kubernetes; specifically, it can create or destroy worker nodes 100 and the containers within worker nodes 100. When business concurrency increases and service needs to be scaled up, the master node 140 can increase the number of worker nodes 100 or increase the number of replicas of containers within container groups to achieve stateless service and provide highly available service to users.
[0067] A container group is the smallest unit of Kubernetes scheduling. It manages at least one container within it and provides services to the outside world through the local network. If a container in the container group fails or restarts, it can quickly retrieve content from the MinIO storage system 121 and the Elasticsearch search engine 122 through other normally running containers to continue to replace the failed or restarted container and provide the corresponding services to the outside world.
[0068] The runtime environment of a cloud-native content management system, such as Figure 1b As shown, worker node 100 includes a node network interface card (eth0) based on a Kubernetes cluster network, supporting node traffic inflow and outflow. The node network interface card communicates with the virtual network interfaces (veth0) of each container group contained within the node through a virtual bridge, and the container groups also communicate with each other through virtual network interfaces. In this embodiment of the invention, worker node 100 includes a first container group 101 for deploying the business logic layer 110, a second container group 102 for deploying the MinIO storage system 121, a third container group 103 for deploying the Elasticsearch search engine 122, a fourth container group 104 for deploying the front-end services of the presentation layer, and a fifth container group 105 for deploying the back-end services of the presentation layer. Each container group includes at least one container. If a container in a container group fails, the services provided by that container can be transferred to other containers in the container group to continue execution, thereby achieving high availability of the content management system.
[0069] The technical solution of this invention, by deploying the content management system on at least one worker node in a Kubernetes cluster, can ensure system stability even under surges in user traffic by increasing the number of worker nodes or the number of containers within those worker nodes. The business logic layer includes a MinIO client and an Elasticsearch client. Upon receiving content to be stored, text-type content can be stored in the Elasticsearch search engine, while object-type content can be stored in the MinIO storage system. This leverages the advantages of both the Elasticsearch search engine and the MinIO storage system to improve the efficiency of the content management system in managing different types of content.
[0070] Figure 2 This invention provides a schematic diagram of the structure of a cloud-native content management system. The cloud-native content management system is deployed on at least one worker node of a Kubernetes cluster and includes a business logic layer 110, a data layer 120, and a presentation layer 130. The Kubernetes cluster includes at least one master node 140 and at least one worker node 100.
[0071] The business logic layer 110 includes a MinIO client 111 and an Elasticsearch client 112, which are used to respond to user content addition requests and store the content to be added to the data layer 120 through at least one of the MinIO client 111 and the Elasticsearch client 112.
[0072] Data layer 120 includes a MinIO storage system 121 and an Elasticsearch search engine 122 for storing content to be added via at least one of the MinIO storage system 121 and the Elasticsearch search engine 122.
[0073] Presentation layer 130 is used to display the content stored in the MinIO storage system 121 and the Elasticsearch search engine 122 on the front end.
[0074] In this embodiment of the invention, the cloud-native content management system further includes a presentation layer 130, which is used for front-end display of content stored in the MinIO storage system 121 and the Elasticsearch search engine 122. For example, the presentation layer 130 can display homepages, products, solutions, support and services provided by the content provider, all of which are stored in the MinIO storage system 121 or the Elasticsearch search engine 122.
[0075] In a specific example, presentation layer 130 can be based on the front-end framework Vue, using Hyper Text Markup Language (Html), Cascading Style Sheets (CSS), and JavaScript to display content such as the homepage, products, solutions, support, and services provided by the content display provider.
[0076] Business logic layer 110 is also used for:
[0077] Respond to the user's content display request and determine the data type of the content to be displayed associated with the content display request;
[0078] If the data type of the content to be displayed is text, the content to be displayed is queried in the Elasticsearch search engine 122 of the data layer 120 through the content query interface, and the content to be displayed is sent to the presentation layer 130.
[0079] If the data type of the content to be displayed is an object, the Elasticsearch search engine 122 in the data layer 120 queries the storage address of the content to be displayed in the MinIO storage system 121 through the content query interface, and then queries the MinIO storage system 121 for the content to be displayed through the storage address, and sends the content to be displayed to the presentation layer 130.
[0080] In this embodiment of the invention, when the business logic layer 110 receives a content display request initiated by a user, it first determines the data type of the content to be displayed associated with the content display request. The data type may include text types and object types. For example, text types may include text or data types, and object types may include images, audio, and video types.
[0081] If the data type of the content to be displayed is determined to be text, the business logic layer 110 queries the Elasticsearch search engine 122 in the data layer 120 for the content to be displayed using a pre-defined content query interface, and then sends the content to be displayed to the presentation layer 130. If the data type of the content to be displayed is determined to be object, the business logic layer 110 queries the Elasticsearch search engine 122 in the data layer 120 for the storage address of the content to be displayed in the MinIO storage system 121, and then queries the MinIO storage system 121 for the content to be displayed using the storage address, and then sends the content to be displayed to the presentation layer 130. The content query interface can be a homepage query interface for the homepage, a title query interface for the title, or a content query interface for content under the title.
[0082] In addition, when the business logic layer 110 receives a content modification request initiated by a user, it can first search for the content to be modified in the MinIO storage system 121 or the Elasticsearch search engine 122 according to the data type of the content to be modified associated with the content modification request, and then modify the content to be modified.
[0083] When the business logic layer 110 receives a content deletion request from a user, it can first determine the data type of the content to be deleted associated with the deletion request. If the content to be deleted is text, it can directly search for and delete the content in the Elasticsearch search engine 122; if the content to be deleted is an object, it can delete the storage address of the content to be deleted in the MinIO storage system 121 in the Elasticsearch search engine 122. When the user accesses the front-end page later, the content to be deleted will not be displayed because the storage address is missing.
[0084] The above process does not directly delete the content to be deleted in the MinIO storage system 121. Instead, it deletes the storage address in the Elasticsearch search engine 122. On the one hand, this prevents the front-end page from displaying the content to be deleted. On the other hand, when users need to add the content to be deleted again in the future, they can directly add the storage address in the Elasticsearch search engine 122 without having to store the content to be added in the MinIO storage system 121, thus saving storage time.
[0085] In a specific example, a user logs into the backend of a cloud-native content management system and stores the title content provided by the content provider in data layer 120. When subsequently accessing the frontend page, the user can retrieve the title content from data layer 120 and display it on the front end. If a title needs to be modified or deleted, the user can log back into the backend of the cloud-native content management system to modify or delete the title content stored in data layer 120. When subsequently accessing the frontend page, the user can retrieve the title content from data layer 120. If the title content has been deleted, it will not be displayed; if it has been modified, the modified title content will be displayed on the front end. The management of content and the homepage follows the same process as the title management, and will not be repeated here.
[0086] The technical solution of this invention, by deploying the content management system on at least one worker node in a Kubernetes cluster, can ensure system stability even under surges in user traffic by increasing the number of worker nodes or the number of containers within those worker nodes. The business logic layer includes a MinIO client and an Elasticsearch client. Upon receiving a content display request, it can retrieve the content to be displayed from the Elasticsearch search engine or the MinIO storage system. Leveraging the advantages of the Elasticsearch search engine and the MinIO storage system improves the search efficiency of the content management system for different types of content, thereby enhancing the user experience of the content management system.
[0087] Figure 3 This invention provides a flowchart of a cloud-native content management method. This embodiment is applicable to scenarios where a highly available content management system is built based on containerized applications. The method can be executed by a cloud-native content management system deployed on at least one worker node of a Kubernetes cluster. Figure 3 As shown, the method includes:
[0088] S310 The business logic layer responds to the user's content addition request and stores the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client.
[0089] The business logic layer includes MinIO clients and Elasticsearch clients. The MinIO client and Elasticsearch client are the user-facing clients deployed in the business logic layer for the MinIO storage system and the Elasticsearch search engine, respectively. Users can store content in the MinIO storage system and the Elasticsearch search engine through the MinIO client and Elasticsearch client, respectively.
[0090] In this embodiment of the invention, when the business logic layer receives a user's content addition request, it stores the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client. Specifically, in response to the user's content addition request, the business logic layer first calls the storage addition interface provided by the MinIO client or the Elasticsearch client through a pre-defined content addition interface to store the content to be added in the MinIO storage system and the Elasticsearch search engine, thereby achieving fast storage of the content to be added.
[0091] S320, the data layer stores the data to be added through at least one of the MinIO storage system and the Elasticsearch search engine.
[0092] In this embodiment of the invention, the business logic layer calls the storage addition interface provided by the MinIO client through the content addition interface to store the content to be added into the MinIO storage system in the data layer. Similarly, the business logic layer calls the storage addition interface provided by the Elasticsearch client through the content addition interface to store the content to be added into the Elasticsearch search engine in the data layer.
[0093] The MinIO storage system provides fast access to large volumes of unstructured data, while the Elasticsearch search engine provides fast storage for text data. Therefore, in this embodiment of the invention, text-type content to be added can be stored in the Elasticsearch search engine, and object-type content to be added can be stored in the MinIO storage system. Furthermore, to quickly locate object-type content in the MinIO storage system, the storage location of the object-type content to be stored in the MinIO storage system can be stored in the Elasticsearch search engine.
[0094] The technical solution of this invention involves the business logic layer responding to a user's content addition request and storing the content to be added to the data layer through at least one of a MinIO client and an Elasticsearch client. The data layer then stores the data to be added through at least one of a MinIO storage system and an Elasticsearch search engine, thereby improving the efficiency of the content management system in managing content.
[0095] Figure 4 This is a flowchart illustrating a cloud-native content management method provided in this embodiment of the invention. This embodiment further refines the above embodiments, providing specific steps for the business logic layer to respond to a user's content addition request and store the content to be added to the data layer using at least one of a MinIO client and an Elasticsearch client. For example... Figure 4 As shown, the method includes:
[0096] S410. The business logic layer responds to the user's content addition request and determines the data type of the content to be added associated with the content addition request.
[0097] In this embodiment of the invention, in response to a user's content addition request, the business logic layer first reads the data type of the content to be added associated with the content addition request. The data type of the content to be added may include text types such as text and data, and may also include object types such as images, audio, or video.
[0098] S420. When the data type of the content to be added is text, the business logic layer calls the first storage add interface provided by the Elasticsearch client through the content add interface to store the content to be added in the Elasticsearch search engine in the data layer.
[0099] In this embodiment of the invention, when the data type of the content to be added is text, the business logic layer calls the first storage addition interface provided by the Elasticsearch client through a pre-defined content addition interface to store the content to be added in the Elasticsearch search engine in the data layer. Leveraging the advantages of Elasticsearch search engine's fast storage and retrieval, rapid access to text-type data to be added can be achieved.
[0100] In a specific example, the content to be added is a title, and its data type is text. In this case, the business logic layer stores the title content to be added in the Elasticsearch search engine in the data layer by calling the first storage add interface provided by the Elasticsearch client.
[0101] S430. When the data type of the content to be added is an object, the business logic layer calls the second storage add interface provided by the MinIO client through the content add interface to store the content to be added in the MinIO storage system in the data layer, and stores the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine.
[0102] In this embodiment of the invention, when the data type of the content to be added is an object, the business logic layer calls the second storage addition interface provided by the MinIO client through a pre-defined content addition interface to store the content to be added in the MinIO storage system in the data layer, and stores the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine. On the one hand, the advantage of the MinIO storage system in quickly accessing unstructured data is utilized to achieve efficient access to the object type data to be added. On the other hand, storing the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine leverages the fast storage and retrieval advantages of the Elasticsearch search engine to quickly locate the storage address of the object type content in the MinIO storage system, further accelerating the retrieval of object type content.
[0103] In a specific example, the content to be added is the specific content under the title, and its data type is video. At this time, the business logic layer calls the second storage add interface provided by the MinIO client to store the video content to be added to the MinIO storage system in the data layer, and stores the storage address of the video content in the MinIO storage system to the Elasticsearch search engine.
[0104] S440, the data layer stores the data to be added using at least one of the MinIO storage system and the Elasticsearch search engine.
[0105] S450: The business logic layer responds to the user's content display request and determines the data type of the content to be displayed associated with the content display request.
[0106] In this embodiment of the invention, the business logic layer, in response to a user-initiated content display request, first reads the data type of the content to be displayed associated with the content display request. The data type of the content to be displayed may include text types such as text and data, and may also include object types such as images, audio, or video.
[0107] S460. When the data type of the content to be displayed is text, the business logic layer queries the Elasticsearch search engine in the data layer through the content query interface to retrieve the content to be displayed, and then sends the content to be displayed to the presentation layer.
[0108] In this embodiment of the invention, when the data type of the content to be displayed is text, the business logic layer queries the Elasticsearch search engine in the data layer for the content to be displayed through a pre-built content query interface. Finally, the retrieved content is sent to the presentation layer to instruct it to display the content. Leveraging the advantages of Elasticsearch's fast storage and retrieval capabilities, rapid querying and display of text-based content can be achieved.
[0109] S470. When the data type of the content to be displayed is an object, the business logic layer queries the Elasticsearch search engine in the data layer for the storage address of the content to be displayed in the MinIO storage system through the content query interface, and then queries the MinIO storage system for the content to be displayed through the storage address, and sends the content to be displayed to the presentation layer.
[0110] In this embodiment of the invention, when the data type of the content to be displayed is an object, the business logic layer uses a pre-defined content query interface to query the storage address of the content to be displayed in the MinIO storage system from the Elasticsearch search engine in the data layer, and then queries the MinIO storage system for the content to be displayed using the storage address. Finally, the content to be displayed is sent to the presentation layer to instruct the presentation layer to render and display the content. On the one hand, the advantage of the MinIO storage system in quickly accessing unstructured data is utilized to achieve efficient retrieval of object-type data to be added. On the other hand, storing the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine leverages the fast storage and retrieval advantages of the Elasticsearch search engine to quickly locate the storage address of object-type content in the MinIO storage system, further accelerating the retrieval of object-type content.
[0111] S480, The presentation layer displays the content to be displayed sent by the business logic layer.
[0112] In this embodiment of the invention, the presentation layer renders and displays the content to be displayed after receiving the content to be displayed from the business logic layer.
[0113] The technical solution of this invention utilizes the advantage of the MinIO storage system in quickly accessing unstructured data to achieve efficient retrieval of object-type data to be added. The storage addresses of text-type content and object-type content in the MinIO storage system are stored in the Elasticsearch search engine. Taking advantage of the fast storage and retrieval capabilities of the Elasticsearch search engine, text-type content can be quickly queried, and the storage address of object-type content in the MinIO storage system can be quickly located, thus achieving efficient querying of content of different data types.
[0114] Figure 5 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0115] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0116] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0117] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as cloud-native content management methods.
[0118] In some embodiments, the cloud-native content management method can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the cloud-native content management method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute the cloud-native content management method by any other suitable means (e.g., by means of firmware).
[0119] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0120] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0121] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0122] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0123] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0124] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.
[0125] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0126] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A cloud-native content management system, characterized in that, Deployed on at least one worker node in a Kubernetes cluster, including: a business logic layer and a data layer; The business logic layer includes a MinIO client and an Elasticsearch client, which are used to respond to user content addition requests and store the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client; The data layer includes a MinIO storage system and an Elasticsearch search engine, used to store the content to be added through at least one of the MinIO storage system and the Elasticsearch search engine; The business logic layer is specifically used for: In response to a user's content addition request, determine the data type of the content to be added associated with the content addition request; If the data type of the content to be added is text, the first storage addition interface provided by the Elasticsearch client is called through the content addition interface to store the content to be added in the Elasticsearch search engine in the data layer; If the data type of the content to be added is an object, the second storage addition interface provided by the MinIO client is called through the content addition interface to store the content to be added in the MinIO storage system in the data layer, and the storage address of the content to be added in the MinIO storage system is stored in the Elasticsearch search engine.
2. The system according to claim 1, characterized in that, Also includes: The presentation layer is used to display the content stored in the MinIO storage system and the Elasticsearch search engine on the front end.
3. The system according to claim 2, characterized in that, The business logic layer is also used for: In response to a user's content display request, determine the data type of the content to be displayed associated with the content display request; If the data type of the content to be displayed is text, the content to be displayed is queried in the Elasticsearch search engine of the data layer through the content query interface, and then the content to be displayed is sent to the presentation layer. If the data type of the content to be displayed is an object, the storage address of the content to be displayed in the MinIO storage system is queried in the Elasticsearch search engine of the data layer through the content query interface, and the content to be displayed is then queried in the MinIO storage system through the storage address, and the content to be displayed is sent to the presentation layer.
4. The system according to claim 2, characterized in that, The Kubernetes cluster includes at least one master node and at least one worker node; The master node is used to control the number of worker nodes and the number of containers in the worker nodes in the Kubernetes cluster based on the business concurrency. The working node includes a first container group for deploying the business logic layer, a second container group for deploying the MinIO storage system, a third container group for deploying the Elasticsearch search engine, a fourth container group for deploying the front-end services of the presentation layer, and a fifth container group for deploying the back-end services of the presentation layer.
5. A cloud-native content management method, characterized in that, Applied to any one of the cloud-native content management systems described in claims 1-4, comprising: The business logic layer responds to the user's content addition request and stores the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client; The data layer stores the content to be added using at least one of the MinIO storage system and the Elasticsearch search engine.
6. The method according to claim 5, characterized in that, The business logic layer responds to the user's content addition request and stores the content to be added to the data layer through at least one of the MinIO client and the Elasticsearch client, including: The business logic layer responds to the user's content addition request and determines the data type of the content to be added associated with the content addition request; When the data type of the content to be added is text, the business logic layer calls the first storage add interface provided by the Elasticsearch client through the content add interface to store the content to be added in the Elasticsearch search engine in the data layer; When the data type of the content to be added is an object, the business logic layer calls the second storage addition interface provided by the MinIO client through the content addition interface to store the content to be added in the MinIO storage system in the data layer, and stores the storage address of the content to be added in the MinIO storage system in the Elasticsearch search engine.
7. The method according to claim 5, characterized in that, Also includes: The business logic layer responds to the user's content display request and determines the data type of the content to be displayed associated with the content display request; If the data type of the content to be displayed is text, the business logic layer queries the Elasticsearch search engine in the data layer through the content query interface and sends the content to be displayed to the presentation layer. When the data type of the content to be displayed is an object, the business logic layer queries the Elasticsearch search engine in the data layer for the storage address of the content to be displayed in the MinIO storage system through the content query interface, and then queries the MinIO storage system for the content to be displayed through the storage address, and sends the content to be displayed to the presentation layer. The presentation layer displays the content to be displayed sent by the business logic layer.
8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the cloud-native content management method according to any one of claims 5-7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the cloud-native content management method according to any one of claims 5-7.
Citation Information
Patent Citations
Crawler crawling data statistical method and system based on distributed storage
CN112528121A
Aero-engine FADEC system software defect case visual query management system based on knowledge graph
CN113987139A
