Business deployment method, device and storage medium of data center

Abstract

The present application discloses a business deployment method, device and storage medium of a data middle station, and the business deployment method of the data middle station includes: receiving metadata of newly deployed business uploaded by the business end, and persistently storing the metadata of newly deployed business to the target database; the target database detects the existence of metadata storage event of newly deployed business, and generates an event notification of storage event; the event notification of storage event is sent to the data middle station management end, so that the data middle station management end updates the deployment mark of the newly deployed business to deployed, and opens the operation menu of the newly deployed business. The decoupling between business instances is realized, so that each business instance can be independently and freely combined and deployed, which improves the flexibility of business deployment of the data middle station, and can accurately and quickly know the deployment status of business instances.

Description

Technical Field

[0001] The present application relates to the technical field of data middle platform, and in particular to a business deployment method, device and storage medium of a data middle platform. Background Art

[0002] With the rapid growth of data volume and the exponential growth of data volume, facing massive data will inevitably lead to four problems: data is difficult to understand, difficult to obtain, difficult to process and difficult to organize. Based on this, the data middle platform is established on the basis of big data technology to centrally collect, integrate, store, manage, process and share all data resources to achieve efficient utilization and added value of data assets.

[0003] However, the data processing requirements in different scenarios are different. How to improve the flexibility of big data processing services and improve the application value of data middle-end systems are urgent problems that technical personnel in this field need to solve. Summary of the invention

[0004] In order to solve the above technical problems, the present application at least provides a business deployment method, device and storage medium of a data middle station.

[0005] The first aspect of the present application provides a business deployment method for a data middle platform, which is applied to a database side, and a target database is deployed on the database side; the method includes: receiving metadata of a newly deployed business uploaded by a business side, and persistently storing the metadata of the newly deployed business to a target database; the target database detects the existence of a metadata storage event for the newly deployed business, and generates an event notification of the storage event; the event notification of the storage event is sent to a data middle platform management side, so that the data middle platform management side updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0006] In one embodiment, the target database comprises a remote dictionary service database.

[0007] In one embodiment, the target database stores metadata of the business instance via a key-value pair data structure, wherein the key in the key-value pair is used to store the business identifier of the business instance, and the value in the key-value pair is used to store the metadata of the business instance; the target database detects the existence of a metadata storage event for a newly deployed business, and generates an event notification for the storage event, including: if the target database detects that data of the key-value pair whose business identifier belongs to the newly deployed business has changed, it is determined that there is a metadata storage event for the newly deployed business, and an event notification for the storage event is generated.

[0008] A second aspect of the present application provides a business deployment method for a data middle platform, which is applied to the data middle platform management end, and the method includes: receiving an event notification of a storage event of a newly deployed business sent by a database end; wherein the event notification of the storage event is generated by a target database after the database end receives the metadata of the newly deployed business uploaded by the business end, and persistently stores the metadata of the newly deployed business in a target database; updating the deployment flag of the newly deployed business to deployed, and opening an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0009] In one embodiment, before receiving the event notification of the storage event of the newly deployed business sent by the database end, the method also includes: deploying the essential business instance, the essential business instance includes a gateway module, a management center module, and a service discovery and configuration management module, the gateway module receives the event notification of the storage event of the newly deployed business sent by the database end, instructs the service discovery and configuration management module to modify the deployment flag of the newly deployed business to deployed, and instructs the management center module to open the operation menu of the newly deployed business.

[0010] In one embodiment, the essential business instance also includes a front-end page module, which is used to display an operation menu for the newly deployed business, and the metadata of the newly deployed business includes interface information and permission information of the newly deployed business; the method also includes: the front-end page module generates an operation request in response to the function entry of the operation menu being triggered; the gateway module detects whether the operation request satisfies the permission information of the newly deployed business; if so, the gateway module forwards the operation request to the newly deployed business based on the interface information of the newly deployed business.

[0011] The third aspect of the present application provides a business deployment method for a data middle platform, which is applied to a business end, and the business end includes multiple business instances; the method includes: in response to any business instance being selected, the selected business instance is used as a newly deployed business, and metadata of the newly deployed business is obtained; the metadata of the newly deployed business is uploaded to the database end, so that the database end stores the metadata of the newly deployed business persistently in the target database, and the target database detects the existence of a metadata storage event of the newly deployed business, generates an event notification of the storage event, and forwards the event notification of the storage event to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0012] In one embodiment, a data upload program is provided in the service startup program corresponding to each business instance; in response to any business instance being selected, the selected business instance is treated as a newly deployed business, and metadata of the newly deployed business is obtained, including: in response to any business instance being selected, the selected business instance is treated as a newly deployed business, and the service startup program of the newly deployed business is called; based on the data upload program in the service startup program, the interface information and permission information of the newly deployed business are scanned to obtain metadata of the newly deployed business.

[0013] The fourth aspect of the present application provides a business deployment device for a data middle platform, which is deployed on the database side, and the device includes: a data storage module, which is used to receive metadata of newly deployed services uploaded by the business side, and persistently store the metadata of the newly deployed services in a target database; a notification generation module, which is used for the target database to detect the presence of a metadata storage event of the newly deployed services, and generate an event notification of the storage event; a notification sending module, which is used to send the event notification of the storage event to the data middle platform management side, so that the data middle platform management side updates the deployment flag of the newly deployed services to deployed, and opens an operation menu for the newly deployed services; wherein the operation menu is composed of a function entry for calling the newly deployed services.

[0014] The fifth aspect of the present application provides a business deployment device for a data middle platform, which is deployed on the data middle platform management end, and the device includes: a notification receiving module, which is used to receive event notifications of storage events of newly deployed businesses sent by the database end; wherein the event notifications of storage events are generated by the target database after the database end receives the metadata of the newly deployed business uploaded by the business end, and persistently stores the metadata of the newly deployed business in the target database; an identification update and menu opening module, which is used to update the deployment identification of the newly deployed business to deployed, and open the operation menu of the newly deployed business; wherein the operation menu is composed of function entries for calling the newly deployed business.

[0015] In a sixth aspect, the present application provides a business deployment device for a data middle platform, which is deployed at a business end, and the device includes: a data acquisition module, which is used to respond to any business instance being selected, take the selected business instance as a newly deployed business, and obtain metadata of the newly deployed business; a data upload module, which is used to upload the metadata of the newly deployed business to the database end, so that the database end stores the metadata of the newly deployed business persistently in the target database, and the target database detects the existence of a metadata storage event of the newly deployed business, generates an event notification of the storage event, and forwards the event notification of the storage event to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0016] The seventh aspect of the present application provides an electronic device, including a memory and a processor, the processor being used to execute program instructions stored in the memory to implement the business deployment method of the above-mentioned data middle station.

[0017] In an eighth aspect, the present application provides a computer-readable storage medium on which program instructions are stored, and when the program instructions are executed by a processor, the business deployment method of the above-mentioned data middle platform is implemented.

[0018] The above scheme receives the metadata of the newly deployed business uploaded by the business end, and persistently stores the metadata of the newly deployed business to the target database; the target database detects the existence of a metadata storage event for the newly deployed business, and generates an event notification of the storage event; the event notification of the storage event is sent to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens the operation menu of the newly deployed business, thereby realizing the decoupling between business instances, allowing each business instance to be independently and freely combined and deployed, thereby improving the flexibility of the data middle platform business deployment, and accurately and quickly knowing the deployment status of the business instances.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0021] Figure 1 It is a schematic diagram of an implementation environment of a solution provided by an embodiment of the present application;

[0022] Figure 2 It is a flowchart of a service deployment method of a data middle station shown in an exemplary embodiment of the present application;

[0023] Figure 3 is a flowchart of a service deployment method of a data middle station shown in another exemplary embodiment of the present application;

[0024] Figure 4 is a flowchart of a service deployment method of a data middle station shown in another exemplary embodiment of the present application;

[0025] Figure 5 It is a schematic diagram of a service deployment method of a data middle station shown in an exemplary embodiment of the present application;

[0026] Figure 6 is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present application;

[0027] Figure 7 It is a schematic diagram of the structure of a computer-readable storage medium shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0028] The scheme of the embodiment of the present application is described in detail below in conjunction with the drawings of the specification.

[0029] In the following description, for the purpose of explanation rather than limitation, specific details such as specific system structures, interfaces, and technologies are provided to facilitate a thorough understanding of the present application.

[0030] The term "and / or" in this article is only an association information describing the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the previous and next associated objects are in an "or" relationship. In addition, "many" in this article means two or more than two. In addition, the term "at least one" in this article means any combination of at least two of any one or more of a plurality of, for example, including at least one of A, B, and C, can mean including any one or more elements selected from the set consisting of A, B, and C.

[0031] The following is a description of the business deployment method of the data center provided in the embodiment of the present application.

[0032] Please refer to Figure 1 , which shows a schematic diagram of a solution implementation environment provided by an embodiment of the present application. The solution implementation environment may include a data middle station management end, a database end, and a business end that are interconnected and communicated with each other.

[0033] The business end can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server, which is not limited in this application.

[0034] The business end includes multiple business instances. For example, a business instance can be a service built based on a microservice architecture, or a business instance can be a Pod in a kubernetes (K8s) cluster. Pod is the smallest resource management component in kubernetes. Pod is also a resource object that minimizes the running of containerized applications. A Pod represents a process running in a K8s cluster. Of course, business instances can also be implemented in other ways, which is not limited in this application.

[0035] A target database is deployed in the database end, and the target database has data persistence storage capability, as well as storage event detection and notification capability. For example, the target database includes a (Remote Dictionary Server, Redis) remote dictionary service database. Of course, other databases with data persistence storage capability, as well as storage event detection and notification capability can also be selected as the target database, and this application does not limit this.

[0036] The data middle platform management end is used to implement the business deployment management and business function implementation of the data middle platform.

[0037] It should be noted that the data middle platform management end, database end and business end in this application can be different physical devices respectively, and multiple of the data middle platform management end, database end and business end can also be integrated into the same physical device. The data middle platform management end, database end and business end together constitute the data middle platform system.

[0038] See also Figure 2 , Figure 2 is a flowchart of a data center service deployment method shown in an exemplary embodiment of the present application. The data center service deployment method can be applied to Figure 1 The implementation environment shown is specifically executed by the database side in the implementation environment.

[0039] like Figure 2 As shown, the service deployment method of the data middle station includes at least steps S210 to S230, which are described in detail as follows:

[0040] Step S210: receiving metadata of the newly deployed service uploaded by the service end, and persistently storing the metadata of the newly deployed service in the target database.

[0041] The metadata of the newly deployed business uploaded by the business end is persistently stored in the target database.

[0042] By persistently storing the metadata of newly deployed services, you can quickly and accurately learn about the deployment status of business instances, and avoid situations where you cannot determine whether a business instance is not deployed or has a fault because the business instance goes offline when it fails.

[0043] Step S220: the target database detects the presence of a metadata storage event for a newly deployed service and generates an event notification of the storage event.

[0044] The target database has the ability to detect storage events. When a metadata storage event of a newly deployed business is detected, an event notification of the storage event is generated.

[0045] Exemplarily, the target database stores metadata of the business through a key-value pair data structure, where the key in the key-value pair is used to store the business identifier of the business, and the value in the key-value pair is used to store the metadata of the business; the target database detects the existence of a metadata storage event for a newly deployed business, and generates an event notification of the storage event, including: if the target database detects that the data of the value corresponding to the key whose business identifier belongs to the newly deployed business has changed, it is determined that there is a metadata storage event for the newly deployed business, and an event notification of the storage event is generated.

[0046] For example, a hash data structure is used to store the metadata of each business instance. The key in the key-value pair is represented by hash_key, and the value in the key-value pair is represented by hash_value. Assume that the storage structure of the metadata of the business instance is: client_request_mapping_hash_key; hash_value is also a hash structure of (key, value), where the key is the business identifier of the business instance (such as the service name), and the value is the metadata of the business instance, such as a list of metadata information of all interfaces of the business instance, including but not limited to the request path, menu number, permission code, etc.

[0047] For example, the storage structure of the metadata of a business instance in the target database is as follows:

[0048] {

[0049] "dataSecurity": [{},{},{}],

[0050] "dataExplore": [{},{},{}],

[0051] "dataQuality": [{},{},{}]

[0052] }

[0053] Among them, "dataSecurity", "dataExplore", "dataQuality" and so on are the business identifiers of the business instance, and [{},{},{}] represents a list of metadata information, such as request path, menu number, permission code, etc. For example:

[0054] {

[0055] "uri": " / dataCompute / projectManagement / resourceInstance", / / Request path "method": "POST", / / Request method

[0056] "requirePermissions": [ / / Application Programming Interface (API) permission information

[0057] {

[0058] "menu": "Menu 1", / / Menu number

[0059] "code": 2 / / Permission code

[0060] },

[0061] {

[0062] "menu": "Menu 2",

[0063] "code": 1

[0064] }

[0065] ],

[0066] }

[0067] The above is an example of a metadata information list. It should be understood that in actual application, other data can be selected as metadata uploaded to the target database, and this application does not limit this.

[0068] When a business instance is started and its metadata is uploaded to the target database, the value corresponding to the client_request_mapping_hash_key key changes. At this time, the target database generates an event notification for the storage event.

[0069] Step S230: Send the event notification of the storage event to the data middle platform management end, so that the data middle platform management end updates the deployment mark of the newly deployed business to deployed, and opens the operation menu of the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0070] After receiving the event notification, the data center management end perceives the deployment of a newly deployed business, and reads the value corresponding to the client_request_mapping_hash_key key from the target database to obtain the business ID of the newly deployed business, updates the deployment ID of the newly deployed business to deployed, and opens the operation menu of the newly deployed business to realize deployment awareness of the newly deployed business.

[0071] See also Figure 3 , Figure 3is a flowchart of a service deployment method of a data center station shown in another exemplary embodiment of the present application. The service deployment method of the data center station can be applied to Figure 1 The implementation environment shown is specifically executed by the business end in the implementation environment.

[0072] like Figure 3 As shown, the service deployment method of the data center includes at least steps S310 to S320, which are described in detail as follows:

[0073] Step S310: In response to any service instance being selected, the selected service instance is used as a newly deployed service, and metadata of the newly deployed service is obtained.

[0074] The business side includes multiple business instances, including but not limited to data standards, data organization, data access, data quality, data exploration, data development, data protection umbrella, etc. Any business instance is used as a newly deployed business.

[0075] For example, it can be to obtain demand information on the data middle platform application scenario, determine the business instances that match the data middle platform application scenario by analyzing the demand information, and use the matching business instances as newly deployed businesses; it can also be to display the deployable business instances on the front-end page, and based on the selection operations performed on the displayed business instances, use the selected business instances as newly deployed businesses.

[0076] In some embodiments, a data upload program is provided in the service startup program corresponding to each business instance; in response to any business instance being selected, the selected business instance is used as a newly deployed business, and the service startup program of the newly deployed business is called; based on the data upload program in the service startup program, the interface information and permission information of the newly deployed business are scanned to obtain the metadata of the newly deployed business.

[0077] For example, each business instance introduces the @EnableAuthClient annotation in the service startup program. The @EnableAuthClient annotation introduces the RequestMappingConfigure.class object through import. As a data upload program, this object will detect the ApplicationReadyEvent event, scan all interface information after the business instance is successfully started, and upload the interface information and permission information as metadata to the target database.

[0078] Through the above method, each business instance will automatically upload the metadata of its own module to the target database for storage when the service is started, thereby improving the perceived speed of business deployment.

[0079] Step S320: Upload the metadata of the newly deployed business to the database side, so that the database side will persistently store the metadata of the newly deployed business to the target database. The target database detects the existence of a metadata storage event for the newly deployed business, generates an event notification of the storage event, and forwards the event notification of the storage event to the data middle-end management side, so that the data middle-end management side updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0080] Optionally, after the business instance uploads its own metadata, the Hypertext Transfer Protocol (HTTP) interface of the management center module is further called to pull the metadata of the data middle-office system so that services can be provided to the outside world. The metadata of the data middle-office system pulled includes but is not limited to: project space information of the data middle-office system, connection information of external data sources, storage / computing engine information, etc.

[0081] See also Figure 4 , Figure 4 is a flowchart of a service deployment method of a data center station shown in another exemplary embodiment of the present application. The service deployment method of the data center station can be applied to Figure 1 The implementation environment shown is specifically executed by the data middle platform management terminal in the implementation environment.

[0082] like Figure 4 As shown, the service deployment method of the data center includes at least steps S410 to S420, which are described in detail as follows:

[0083] Step S410: receiving an event notification of a storage event of a newly deployed service sent by the database end; wherein the event notification of the storage event is generated by the target database after the database end receives metadata of the newly deployed service uploaded by the service end and persistently stores the metadata of the newly deployed service in the target database.

[0084] Step S420: updating the deployment flag of the newly deployed service to deployed, and opening an operation menu of the newly deployed service; wherein the operation menu is composed of a function entry for invoking the newly deployed service.

[0085] In some implementations, essential business instances are deployed preferentially. For example, essential business instances include front-end page modules, gateway modules, management center modules, service discovery and configuration management modules, etc. Essential business instances are deployed preferentially when building a data middle-office system. Other business instances are not deployed when building a data middle-office system, but are deployed during subsequent system upgrades.

[0086] Among them, the front-end page module: provides the global wide area network (World Wide Web, WEB) service for accessing the data middle platform system;

[0087] Gateway module: Mainly responsible for forwarding requests from WEB browsers to various business instances, and can also provide unified authentication, log auditing and other functions.

[0088] Management center module: The metadata center in the data middle-office system is responsible for the system’s account information, menu and permission information, connection information of various data sources, etc.

[0089] Service discovery and configuration management module (Nacos): Responsible for implementing service configuration and service discovery functions in the Spring Cloud ecosystem. It is a dynamic service discovery, configuration management, and service management platform that makes it easier to build cloud-native applications.

[0090] Exemplarily, a required business instance is deployed, which includes a gateway module, a management center module, a service discovery and configuration management module. The gateway module receives an event notification of a storage event of a newly deployed business sent by the database end, instructs the service discovery and configuration management module to modify the deployment flag of the newly deployed business to deployed, and instructs the management center module to open an operation menu for the newly deployed business.

[0091] For example, the deployment identifier of a business instance is stored as a configuration file in the Nacos configuration center. It is a properties file structure, where each Key represents the business identifier of a business instance, and the Value indicates whether the business instance is deployed, with 0 representing undeployed and 1 representing deployed. For example:

[0092] dataSecurity=1

[0093] dataExplore=1

[0094] dataQuality=0

[0095] dataDev=1

[0096] dataCollection=0

[0097] dataGovernance=1

[0098] When the gateway module service is started, the gateway module will read the deployment identifier of the business instance in Nacos. If it does not exist, it means that all modules have not been deployed yet, and then initialize the configuration of the deployment identifier of a business instance to Nacos, where the initialization defaults the deployment identifier of all business instances to 0. And, if the deployment identifier of the business instance is 0, the operation menu of the business instance is hidden, and if the deployment identifier of the business instance is 1, the operation menu of the business instance is opened.

[0099] After the gateway module receives the event notification of the storage event of the newly deployed business, that is, it perceives that there is a business instance deployed, it reads the business identifier of the newly deployed business from the target database, compares it with the business identifiers of the existing business instances in Nacos, modifies the deployment identifier of the newly deployed business in Nacos, and changes the value of the deployment identifier from 0 to 1; and calls the API interface of the management center module to open the operation menu of the newly deployed business.

[0100] It should be noted that if the data middle-office system starts to be deployed from the required business instance, the data middle-office system will only display the operation menu related to the required business instance, and the operation menu of the undeployed business instance will not be displayed. When an optional business instance is successfully deployed, its corresponding operation menu will be displayed, providing an entry for using the functions of the business instance.

[0101] In some embodiments, the essential business instance also includes a front-end page module, which is used to display an operation menu for the newly deployed business, and the metadata of the newly deployed business includes interface information and permission information of the newly deployed business; the method also includes: the front-end page module generates an operation request in response to the function entry of the operation menu being triggered; the gateway module detects whether the operation request satisfies the permission information of the newly deployed business; if so, the gateway module forwards the operation request to the newly deployed business based on the interface information of the newly deployed business.

[0102] After the gateway module service is successfully started, the front-end page module generates an operation request in response to the function entry of the operation menu being triggered. The gateway module detects whether the business instance is deployed based on the business identifier corresponding to the operation menu. If not, the operation request is intercepted and a prompt message indicating that the business is not deployed is returned. If it is deployed, the operation request is checked for permissions based on the permission information of the business instance stored in the target database. If the permission information is met, the gateway module forwards the operation request to the newly deployed business based on the interface information of the newly deployed business.

[0103] For an example, see Figure 5 , Figure 5 This is a schematic diagram of a service deployment method of a data center according to an embodiment of the present application. Figure 5As shown, there are multiple business instances on the business side. In response to any business instance being selected, the selected business instance is used as a newly deployed business, the metadata of the newly deployed business is obtained, the metadata of the newly deployed business is uploaded to the remote dictionary service database Redis, Redis persistently stores the metadata of the newly deployed business, and generates an event notification of the storage event of the newly deployed business, and sends the event notification of the storage event to the gateway module. The gateway module receives the event notification and modifies the deployment identifier of the newly deployed business in the service discovery and configuration management module Nacos, and changes the value of the deployment identifier from 0 to 1, and the gateway module calls the API interface of the management center module to open the operation menu of the newly deployed business.

[0104] In addition, after the business instance uploads its own metadata, the HTTP interface of the management center module is called to pull the metadata of the data middle-office system so that it can provide services to the outside world. The metadata of the data middle-office system pulled includes but is not limited to: project space information of the data middle-office system, connection information of external data sources, storage / computing engine information, etc.; after modifying the deployment identifier of the newly deployed business, Nacos will also push the latest business deployment information to other business instances, so that all other business instances in the data middle-office system can also perceive the new business instance deployment.

[0105] By selectively deploying some business instances, the flexibility of data center business deployment is improved. Since all business instances only interact with the target database during the deployment process, there is no interaction between business instances, which achieves decoupling between business instances, allowing each business instance to be independently and freely combined and deployed. In addition, the target database's data persistence storage capabilities and automatic detection and notification capabilities of storage events can not only accurately and quickly obtain the deployment status of business instances, but also avoid the situation where the business instance is offline due to a failure, making it impossible to determine whether the business instance is not deployed or has a failure. In addition, it can automatically notify business deployment events, which reduces performance loss in the program compared to the method of periodic polling to detect whether there is a deployed business.

[0106] The present application also provides a business deployment device for a data middle platform, which is deployed on the database side, and the device includes: a data storage module, which is used to receive the metadata of the newly deployed business uploaded by the business side, and persistently store the metadata of the newly deployed business to the target database; a notification generation module, which is used for the target database to detect the existence of a metadata storage event of the newly deployed business, and generate an event notification of the storage event; a notification sending module, which is used to send the event notification of the storage event to the data middle platform management side, so that the data middle platform management side updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0107] The present application also provides a business deployment device for a data middle platform, which is deployed on the data middle platform management end, and the device includes: a notification receiving module, which is used to receive event notifications of storage events of newly deployed businesses sent by the database end; wherein the event notifications of storage events are generated by the target database after the database end receives the metadata of the newly deployed business uploaded by the business end, and the metadata of the newly deployed business is persistently stored in the target database; an identification update and menu opening module, which is used to update the deployment identification of the newly deployed business to deployed, and open the operation menu of the newly deployed business; wherein the operation menu is composed of function entries for calling the newly deployed business.

[0108] The present application also provides a business deployment device for a data middle platform, which is deployed at the business end, and the device includes: a data acquisition module, which is used to respond to any business instance being selected, take the selected business instance as a newly deployed business, and obtain the metadata of the newly deployed business; a data upload module, which is used to upload the metadata of the newly deployed business to the database end, so that the database end stores the metadata of the newly deployed business persistently in the target database, and the target database detects the existence of a metadata storage event of the newly deployed business, generates an event notification of the storage event, and forwards the event notification of the storage event to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business; wherein the operation menu is composed of a function entry for calling the newly deployed business.

[0109] It should be noted that the business deployment device of the data middle station provided in the above embodiment and the business deployment method of the data middle station provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment and will not be repeated here. In actual applications, the business deployment device of the data middle station provided in the above embodiment can distribute the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0110] See also Figure 6 , Figure 6 6 is a schematic diagram of the structure of an embodiment of an electronic device of the present application. The electronic device 600 includes a memory 601 and a processor 602, and the processor 602 is used to execute program instructions stored in the memory 601 to implement the steps in any of the above-mentioned data center service deployment method embodiments. In a specific implementation scenario, the electronic device 600 may include but is not limited to: a microcomputer, a server, and in addition, the electronic device 600 may also include a mobile device such as a laptop computer and a tablet computer, which is not limited here.

[0111] Specifically, the processor 602 is used to control itself and the memory 601 to implement the steps in any of the above-mentioned data middle station business deployment method embodiments. The processor 602 may also be referred to as a central processing unit (CPU). The processor 602 may be an integrated circuit chip having signal processing capabilities. The processor 602 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. In addition, the processor 602 may be implemented by an integrated circuit chip.

[0112] See also Figure 7 , Figure 7 The computer-readable storage medium 700 stores program instructions 710 that can be executed by a processor, and the program instructions 710 are used to implement the steps in any of the above-mentioned data center service deployment method embodiments.

[0113] In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiments. The specific implementation can refer to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0114] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0115] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0116] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

Claims

1. A data center service deployment method, characterized in that: Applied to a database end, the database end is deployed with a target database; the method comprises: Receive metadata of the newly deployed service uploaded by the service end, and persistently store the metadata of the newly deployed service in the target database; wherein the metadata of the newly deployed service includes interface information and permission information of the newly deployed service; The target database detects the existence of a metadata storage event of the newly deployed service, and generates an event notification of the storage event; An event notification of the storage event is sent to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business. The operation menu is composed of a function entry for calling the newly deployed business. In response to the function entry of the operation menu being triggered, an operation request is generated, and it is detected whether the operation request satisfies the permission information of the newly deployed business. If so, the operation request is forwarded to the newly deployed business based on the interface information of the newly deployed business.

2. The method according to claim 1, characterized in that The target database includes a remote dictionary service database.

3. The method according to claim 1, characterized in that The target database stores metadata of the business instance through a key-value pair data structure, wherein the key in the key-value pair is used to store the business identifier of the business instance, and the value in the key-value pair is used to store the metadata of the business instance; The target database detects the presence of a metadata storage event of the newly deployed service and generates an event notification of the storage event, including: The target database detects that the data of the key-value pair of the service identifier belonging to the newly deployed service has changed, then determines that there is a metadata storage event of the newly deployed service, and generates an event notification of the storage event.

4. A data center service deployment method, characterized in that: Applied to the data center management end, the method includes: Receiving an event notification of a storage event of a newly deployed service sent by a database end; wherein the event notification of the storage event is generated by the target database after the database end receives metadata of the newly deployed service uploaded by the service end and persistently stores the metadata of the newly deployed service in a target database, wherein the metadata of the newly deployed service includes interface information and permission information of the newly deployed service; Updating the deployment flag of the newly deployed service to deployed, and opening the operation menu of the newly deployed service; wherein the operation menu is composed of a function entry for calling the newly deployed service; In response to the function entry of the operation menu being triggered, an operation request is generated, and it is detected whether the operation request meets the authority information of the newly deployed service. If so, the operation request is forwarded to the newly deployed service based on the interface information of the newly deployed service.

5. The method according to claim 4, characterized in that Before receiving the event notification of the storage event of the newly deployed service sent by the database end, the method further includes: Deploy the essential business instance, which includes a gateway module, a management center module, a service discovery and configuration management module. The gateway module receives the event notification of the storage event of the newly deployed business sent by the database end, instructs the service discovery and configuration management module to modify the deployment flag of the newly deployed business to deployed, and instructs the management center module to open the operation menu of the newly deployed business.

6. The method according to claim 5, characterized in that The essential service instance further includes a front-end page module, and the front-end page module is used to display an operation menu for the newly deployed service; the method further includes: The front-end page module generates an operation request in response to the function entry of the operation menu being triggered; The gateway module detects whether the operation request satisfies the authority information of the newly deployed service; If so, the gateway module forwards the operation request to the newly deployed service based on the interface information of the newly deployed service.

7. A data center service deployment method, characterized in that: Applied to a business end, the business end includes multiple business instances; the method includes: In response to any service instance being selected, the selected service instance is used as a newly deployed service, and metadata of the newly deployed service is acquired, where the metadata of the newly deployed service includes interface information and permission information of the newly deployed service; The metadata of the newly deployed business is uploaded to the database end, so that the database end persistently stores the metadata of the newly deployed business to the target database. The target database detects the existence of a metadata storage event of the newly deployed business, generates an event notification of the storage event, and forwards the event notification of the storage event to the data middle platform management end, so that the data middle platform management end updates the deployment flag of the newly deployed business to deployed, and opens an operation menu for the newly deployed business. The operation menu consists of a function entry for calling the newly deployed business. In response to the function entry of the operation menu being triggered, an operation request is generated, and it is detected whether the operation request satisfies the permission information of the newly deployed business. If so, the operation request is forwarded to the newly deployed business based on the interface information of the newly deployed business.

8. The method according to claim 7, characterized in that A data upload program is set in the service startup program corresponding to each business instance; In response to any service instance being selected, taking the selected service instance as a newly deployed service, and obtaining metadata of the newly deployed service, including: In response to any service instance being selected, the selected service instance is used as a newly deployed service, and a service startup program of the newly deployed service is called; The data upload program in the service startup program scans the interface information and permission information of the newly deployed service to obtain metadata of the newly deployed service.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the processor is configured to execute program instructions stored in the memory to implement the steps in the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program instructions, and the program instructions can be executed by a processor to implement the steps in the method according to any one of claims 1 to 8.

Images