Application release system and application release method

Abstract

The invention relates to an application publishing system and method, and the system comprises a presentation layer which is used for providing a user interaction interface and obtaining the configuration information of a user; the publishing system platform layer is used for deploying various publishing platforms, and the publishing platforms are used for publishing applications; the application layer is used for binding the tenants and the publishing platform according to the configuration information, and the application layer comprises one or any combination of a platform nano-management docking management module, a platform resource synchronization module and a platform tenant authorization module; and the logic layer is used for carrying out logic abstract packaging on the business of each module in the application layer. According to the invention, transverse expansion and management of various publishing platforms can be supported, and operation and operation and maintenance management are facilitated.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of application publishing control, and in particular to an application publishing system and an application publishing method. Background Art

[0002] With the rapid development of Internet technology, new technologies such as Internet finance and artificial intelligence have driven enterprises to run their application businesses on cloud infrastructure in a containerized manner. In order to improve customer satisfaction and respond quickly to market changes, it is becoming increasingly important for enterprises to release applications frequently and in small batches. Therefore, the application release platform is crucial in modern application development and operation and maintenance, providing a standardized, automated, controllable and traceable application release method.

[0003] However, with the growth of the number of users, a single publishing platform can no longer meet the demand. Using only a single publishing platform can easily cause the system to crash or run slowly, and multiple publishing platforms need to be used. At present, the industry lacks a unified standard for release management. The features and release processes of the release platforms developed by different manufacturers vary, and there is a lack of a unified portal to manage these differentiated platforms. The existing defects include: a single release platform does not support horizontal expansion and is difficult to adapt to the growth of the number of users; the lack of compatibility between the release platforms requires enterprises to purchase multiple systems and conduct secondary development, which increases the cost and complexity of use, and the lack of a unified management and control method makes it difficult to achieve effective management of different release platforms and reasonable allocation of resources. The existing application release methods have problems with inconvenient operation and maintenance management. Summary of the invention

[0004] The technical problem to be solved by this application is to provide an application publishing system and an application publishing method, which can support horizontal expansion and management of multiple publishing platforms, and facilitate operation and maintenance management.

[0005] The technical solution adopted by the present application to solve the above-mentioned technical problems is an application publishing system, including: a presentation layer, which is used to provide a user interaction interface and obtain user configuration information; a publishing system platform layer, which is used to deploy multiple publishing platforms, and the publishing platform is used to publish applications; an application layer, which is used to bind tenants and publishing platforms according to configuration information, and the application layer includes: one or any combination of a platform management and docking management module, a platform resource synchronization module, and a platform tenant authorization module; a logic layer, which is used to logically abstract and encapsulate the business of each module in the application layer.

[0006] In one embodiment of the present application, users include cloud platform administrators; the platform management and docking management module is configured to: manage and dock tenants and publishing platforms according to user instructions and manage authentication information of the publishing platform; the platform resource synchronization module is configured to: obtain non-managed resources of the publishing platform and synchronize the non-managed resources to the database; manage the resource synchronization cycle of the publishing platform according to user instructions; the platform tenant authorization module is configured to: manage the authorization binding relationship between the tenant and the publishing platform according to the configuration policy.

[0007] In one embodiment of the present application, users include tenant users; the application layer is also used to execute application publishing tasks according to configuration information and a publishing platform, and the application layer also includes: one or any combination of an identity authentication and access control module, a publishing management module, and a log audit module; wherein the identity authentication and access control module is configured to: verify the identity of the user according to the login information and log in to the application publishing system after the verification is passed; determine the corresponding publishing platform according to the tenant information to which the user belongs; assign the application publishing task to the corresponding bound publishing platform according to the user's publishing operation; the publishing management module is configured to: publish and manage applications according to user instructions; and display the standard application publishing process to users; the log audit module is configured to: record the application publishing operation log, and the publishing operation log includes one or any combination of a security log, a system log, and a business log.

[0008] In one embodiment of the present application, the user interaction interface includes: a tenant user interface, including a tenant user login authentication interface and an interactive interface related to the application publishing process; a platform management interface, including a management interface for a cloud platform administrator to configure the publishing platform, a tenant authorization interface, and a resource synchronization interface.

[0009] In one embodiment of the present application, one publishing platform is bound to one tenant or multiple tenants, and one tenant is bound to one publishing platform.

[0010] In one embodiment of the present application, the application publishing system also includes a data layer, which includes a database and a cache library. The database is used to store user data, log data, permission configuration data, and resource information; the cache library is used to improve the reading speed of data access.

[0011] In one embodiment of the present application, the application publishing system also includes an infrastructure layer, and the hardware resources of the infrastructure layer include: one or any combination of servers, storage devices, network devices, and load balancers.

[0012] In order to solve the above-mentioned technical problems, the present application also proposes an application publishing method, which uses the above-mentioned application publishing system, including: obtaining the configuration information of the cloud platform administrator, and managing and connecting multiple publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator; obtaining non-managed resources of the publishing platform, and synchronizing the non-managed resources to the database; binding the tenant and the publishing platform; obtaining and verifying the login information of the tenant user, and displaying the relevant interactive interface in the application publishing process after the verification is passed; obtaining the configuration information of the tenant user, and executing the application publishing task according to the configuration information of the tenant user and the publishing platform.

[0013] In one embodiment of the present application, after the step of managing and connecting multiple publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator, it also includes: detecting the connection status between the publishing platform and the application publishing system according to a preset period; if the connection status is connection failure, an alarm is sent to the cloud platform administrator.

[0014] In one embodiment of the present application, the step of executing the application publishing task according to the configuration information of the tenant user and the publishing platform includes: allocating the application to the corresponding bound publishing platform according to the configuration information and publishing operation of the tenant user; and recording the publishing operation log of the application.

[0015] The technical solution of the present application adopts a modular architecture design, which divides the application publishing system into a presentation layer, a publishing system platform layer, an application layer, and a logic layer, and sets up multiple independent functional modules in the application layer. This setting is easy to expand. The application publishing system adopts an open interface and standardized data format, and can support the access and data exchange of multiple publishing platforms. Users can flexibly configure the system and set management policies through the presentation layer. The present application unifies the application publishing standards, unifies the application publishing operation process at the top, and shields the specific usage differences of different publishing platforms at the bottom. Users only need to focus on the publishing of their own business processes to improve management efficiency and user experience.

[0016] The application publishing system of the present application can adapt to the characteristics and requirements of different publishing platforms, support the docking of different platforms to the maximum extent, support the horizontal expansion and management of multiple publishing platforms, can adapt to the growing user needs, and can disperse the user's publishing needs to different publishing platforms for publishing, which is convenient for operation and maintenance management, and can reduce the load and pressure of the entire system operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below with reference to the accompanying drawings, wherein:

[0018] Figure 1 is a schematic diagram of an application publishing system according to an embodiment of the present application;

[0019] Figure 2 is a schematic diagram of an application publishing system according to another embodiment of the present application;

[0020] Figure 3 is an exemplary flow chart of an application publishing method according to an embodiment of the present application;

[0021] Figure 4 This is a flow chart of a cloud platform administrator using an application publishing system in one embodiment of the present application;

[0022] Figure 5 This is a flow chart of a tenant user using an application publishing system in one embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are described in detail below with reference to the accompanying drawings.

[0024] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application may also be implemented in other ways different from those described herein, and therefore the present application is not limited to the specific embodiments disclosed below.

[0025] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0026] Flowcharts are used in the present application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed accurately in order. On the contrary, various steps may be processed in reverse order or simultaneously. At the same time, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0027] The following first introduces the main factors analyzed and considered when designing the application publishing system and application publishing method of this application. The specific design of the application publishing system and application publishing method will be introduced later.

[0028] As enterprises and services expand, the number of users continues to increase, and a single publishing platform can no longer meet current usage needs. Therefore, the publishing platform needs to be expanded horizontally. Specifically, the demand for horizontal expansion comes from the following aspects:

[0029] 1. The number of users is constantly growing, and a single publishing platform cannot support user needs, so horizontal expansion is needed. When the number of publishing users surges, the system of a single publishing platform is prone to crash or slow operation. Therefore, an adaptive control architecture with horizontal expansion capabilities is needed to disperse user publishing needs to different publishing platforms.

[0030] 2. Adapt to the publishing needs of different users. Different publishing platforms usually have different characteristics and scales, and a single publishing platform is often difficult to adapt to these diverse needs. Therefore, an adaptive control architecture that can flexibly adapt to the characteristics and scales of different publishing platforms is needed to meet the needs of users on different platforms.

[0031] 3. Disaster recovery and security considerations. In a modern publishing environment, if special circumstances occur, disaster recovery preparations need to be made to ensure that when a publishing platform fails, publishing tasks can be directed to other publishing platforms to avoid blocking the company's publishing process. Therefore, it is necessary to deploy multiple publishing platforms to deal with possible abnormal situations.

[0032] 4. The publishing business is unified for users, and the underlying publishing platform is shielded from users. Since different publishing platforms have different characteristics, the user learning cost is high and the operation is inconvenient. Therefore, it is necessary to provide a unified entrance and publishing standard to unify the publishing operation at the top and shield the specific usage differences of different publishing platforms at the bottom. Users only need to focus on the publishing of their own business processes without paying too much attention to the differences in the underlying platforms, thereby improving management efficiency and user experience.

[0033] 5. Tenant binding, each tenant uses its own publishing platform. Each publishing platform company will provide a unified portal for users to use, but different users may want to use different publishing platforms. To meet this demand, it is necessary to connect different publishing platforms under the same portal and bind the publishing platforms to their respective tenants as needed. It can be set that the bound tenants can only use the bound platform to publish application content, so as to achieve the isolation of publishing platforms and tenants, which is convenient for operation and maintenance management.

[0034] 6. Multiple publishing platforms facilitate management and docking. After the horizontal expansion of multiple publishing platforms, the unified portal needs to be more convenient for managing these publishing platforms. Therefore, an adaptive control architecture that can adapt to different publishing platforms is required, so that the publishing platform can be offline for maintenance or new publishing platforms can be online for management at any time as needed.

[0035] In summary, in view of the situation of multiple publishing platforms, an adaptive control architecture and operation method that supports horizontal expansion and management of multiple publishing platforms is needed. This architecture and method can improve management efficiency and user experience and meet the growing needs of enterprises and users.

[0036] The specific design of the application publishing system and application publishing method of this application will be introduced later.

[0037] The present application proposes an application publishing system that can be used in application scenarios that facilitate the deployment, expansion, and management of multiple publishing platforms and facilitate users to publish applications.

[0038] Figure 1 is a schematic diagram of an application publishing system according to an embodiment of the present application, with reference to Figure 1 As shown, the application publishing system 100 of this embodiment includes: a presentation layer 110, which is used to provide a user interaction interface and obtain user configuration information; a publishing system platform layer 140, which is used to deploy multiple publishing platforms, and the publishing platform is used to publish applications; an application layer 120, which is used to bind tenants and publishing platforms according to configuration information, and the application layer 120 includes: a platform management and docking management module 123, a platform resource synchronization module 125, and a platform tenant authorization module 122, or any combination thereof; a logic layer 130, which is used to perform logical abstraction encapsulation on the business of each module in the application layer 120.

[0039] Exemplarily, the above-mentioned layers and modules in the application publishing system 100 of the present application can be implemented by a computer hardware device composed of a processor and a memory. Specifically, the above-mentioned layers and modules are stored in the memory as program units, and the processor executes each program unit stored in the memory to implement thread control. The overall architecture of the application publishing system 100 of the present application adopts the idea of ​​modular design. By splitting the different functional modules of the application publishing system 100, flexible management of different publishing platforms can be achieved.

[0040] Exemplarily, the user referred to in this application may be a cloud platform administrator or an ordinary tenant user. The configuration information of the cloud platform administrator includes: operating instructions for managing tenant information, operating instructions for managing the publishing platform, etc.; the configuration information of ordinary tenant users includes: login information (such as account password), operating instructions for publishing applications, instructions for managing applications, etc. The publishing system platform layer 140 is mainly used to deploy publishing platforms of different manufacturers and provide basic atomic publishing capabilities. The publishing system platform layer 140 can be deployed on the infrastructure of the data center (such as servers and other hardware devices). The logic layer 130 contains business rules and processing logic, and can logically encapsulate the business of each module in the application layer 120 in combination with the company's business. For example, the business is: how to handle user authorization, how to record logs, etc.

[0041] Exemplarily, the application layer 120 of the present application can realize the function of flexibly binding tenants and publishing platforms, for example, each tenant uses its own independent publishing platform, and different publishing platforms can be bound to corresponding tenants for use according to actual needs. Specifically, it can be set that once a tenant is bound to a publishing platform, the tenant can only use the publishing platform to which it is bound when publishing application content, and cannot use the publishing platforms under other tenants. Such a setting can achieve effective isolation between the publishing platform and the tenant, and facilitate operation and maintenance management.

[0042] The tenants and publishing platforms of this application can be flexibly configured and managed. Specific tenants can be bound to specific publishing platforms as needed without the upper-level business being aware of it. This application facilitates the management of multiple publishing platforms, and can be taken offline for maintenance at any time as needed, and new publishing platforms can be put online for management. During the application release process, if there are problems with the new version of the application, the publishing platform of this application can support rolling back to the previous stable version to ensure the continuous operation of the system and the stability of the service.

[0043] The technical solution of the present application adopts a modular architecture design, by splitting the application publishing system 100 into a presentation layer 110, a publishing system platform layer 140, an application layer 120, and a logic layer 130, and setting a plurality of independent functional modules in the application layer 120. This setting is easy to expand. The application publishing system 100 adopts an open interface and a standardized data format, and can support the access and data exchange of multiple publishing platforms; users can flexibly configure the system and set management policies through the presentation layer 110. The present application unifies the application publishing standards, unifies the application publishing operation process at the top, and shields the specific usage differences of different publishing platforms at the bottom. Users only need to focus on the publishing of their own business processes to improve management efficiency and user experience.

[0044] The application publishing system 100 of the present application can adapt to the characteristics and requirements of different publishing platforms, support the docking of different platforms to the maximum extent, support the horizontal expansion and management of multiple publishing platforms, can adapt to the growing user needs, and can disperse the user's publishing needs to different publishing platforms for publishing, which is easy to operate and maintain, and can reduce the load and pressure of the entire system operation.

[0045] Figure 2 Schematic diagram of an application publishing system according to another embodiment of the present application. Figure 2 As shown, in some embodiments, the user interaction interface provided by the presentation layer 110 includes: a tenant user interface, including a tenant user login authentication interface and related interaction interfaces during the application publishing process; a platform management interface, including a management interface for a cloud platform administrator to configure the publishing platform, a tenant authorization interface, and a resource synchronization interface.

[0046] For example, the application can realize the unified publishing standard for users through the presentation layer 110, and the underlying publishing platform (such as Figure 2 Publishing platform A to publishing platform D) shown in the figure are shielded for users. Users do not need to pay too much attention to the usage differences of the underlying publishing platforms, but only need to focus on the business process publishing themselves, which can reduce the user's usage learning cost and improve management efficiency and user experience.

[0047] In some embodiments, one publishing platform is bound to one tenant or multiple tenants, and one tenant is bound to one publishing platform. For example, in actual applications, it can also be set so that a tenant can unbind a problematic publishing platform and bind a normal publishing platform at the same time, so that in the event of a failure of a publishing platform, the application publishing task can be directed to other publishing platforms without blocking the company's publishing process.

[0048] In some embodiments, the user includes a cloud platform administrator. The platform side of the application publishing system 100 is mainly configured by the cloud platform administrator to manage and connect the publishing platform and authorize tenants. Through the management of the binding relationship between tenants and the publishing platform, horizontal expansion management of multiple publishing platforms can be achieved, thereby improving the overall scalability and fault tolerance of the system.

[0049] refer to Figure 2 As shown, the platform management and docking management module 123 is configured to: manage and dock tenants and publishing platforms according to user instructions and manage the authentication information of the publishing platform. Exemplarily, the platform management and docking management module 123 is used by the cloud platform administrator to manage the management and docking of different tenants. Management and docking refers to integrating different tenants (or user groups, business departments, etc.) and their resources into the publishing platform.

[0050] The platform resource synchronization module 125 is configured to: obtain the non-managed resources of the publishing platform, synchronize the non-managed resources to the database; and manage the resource synchronization cycle of the publishing platform according to user instructions. Exemplarily, the platform resource synchronization module 125 can ensure that the non-managed internal resources of the publishing platform can be automatically synchronized into the library, for example, regularly capture the non-managed resources (such as various data files, database records, etc.) inside the publishing platform, and the platform resource synchronization module 125 can automatically synchronize them to the resource library of the application publishing system 100 to ensure the integrity and accuracy of the resources.

[0051] The platform tenant authorization module 122 is configured to manage the authorization binding relationship between the tenant and the publishing platform according to the configuration policy. Exemplarily, the platform tenant authorization module 122 can manage the configuration policy of the correspondence between the tenant and the publishing platform, and can authorize different publishing platforms to different tenants to achieve isolation between tenants and different publishing platforms.

[0052] In some embodiments, the user includes a tenant user. The application layer 120 is also used to execute application publishing tasks according to configuration information and a publishing platform. The tenant side of the application publishing system 100 is mainly oriented to common tenant users, providing unified user login authentication, publishing operations, etc.

[0053] refer to Figure 2 As shown, in some embodiments, the application layer 120 further includes: an identity authentication and access control module 121 , a release management module 124 , and a log audit module 126 , or any combination thereof.

[0054] The identity authentication and access control module 121 is configured to: verify the identity of the user according to the login information and log in to the application publishing system 100 after the verification is passed; determine the corresponding publishing platform according to the tenant information to which the user belongs; and assign the application publishing task to the corresponding bound publishing platform according to the user's publishing operation. Exemplarily, the identity authentication and access control module 121 is responsible for user identity authentication, authority allocation, and user access control, and can perform diversion control on different publishing platforms for the user's application publishing operation. For example, when a publishing platform fails, the application publishing can be diverted to other publishing platforms without blocking the company's publishing process.

[0055] The publishing management module 124 is configured to: publish and manage applications according to user instructions; and display the application publishing standard process to users. Exemplarily, the publishing management module 124 allows tenant users to publish and manage applications, provides users with a unified publishing standard process abstraction, and shields the differences between different publishing platforms.

[0056] The log audit module 126 is configured to record the release operation log of the application, and the release operation log includes one or any combination of security logs, system logs, and business logs. Exemplarily, the log audit module 126 can provide a log monitoring function, allowing users to monitor the release status and performance indicators in real time. The log audit module 126 can integrate change management and version control functions, so that each application release can be tracked, which is convenient for quickly locating problems.

[0057] This application uses the identity authentication and access control module 121 and the log audit module 126 to enable the system to effectively prevent various security threats and attacks; record the system's operation logs, including operation logs and error logs, to facilitate system troubleshooting and log analysis, and to ensure the stable operation of the system and post-audit.

[0058] refer to Figure 2 As shown, in some embodiments, the application publishing system 100 also includes a data layer 160, and the data layer 160 includes a database and a cache library. The database is used to store user data, log data, permission configuration data, and resource information; the cache library is used to improve the reading speed of data access.

[0059] In some embodiments, the application publishing system 100 further includes an infrastructure layer 150. The hardware resources of the infrastructure layer 150 include: one or any combination of servers, storage, network equipment, and load balancers. Exemplarily, the infrastructure layer 150 can provide hardware resources for upper-layer services.

[0060] The present application also proposes an application publishing method, using the application publishing system 100 as described above.

[0061] Figure 3 is an exemplary flow chart of an application publishing method according to an embodiment of the present application, with reference to Figure 3 As shown, the application publishing method of this embodiment includes the following steps:

[0062] Step S110: Obtain the configuration information of the cloud platform administrator, and manage and connect various publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator.

[0063] Step S120: Acquire the non-managed resources of the publishing platform and synchronize the non-managed resources to the database.

[0064] Step S130: Bind the tenant to the publishing platform.

[0065] Step S140: Acquire and verify the login information of the tenant user, and display the relevant interactive interface in the application publishing process after the verification is passed.

[0066] Step S150: Obtain the configuration information of the tenant user, and execute the application publishing task according to the configuration information of the tenant user and the publishing platform.

[0067] Exemplarily, steps S110 to S130 are equivalent to the steps executed internally by the application publishing system 100 after the application publishing system 100 receives an operation instruction from a cloud platform administrator (platform-side user); steps S140 to S150 are equivalent to the steps executed internally by the application publishing system 100 after the application publishing system 100 receives an operation instruction from a tenant user (tenant-side user).

[0068] Figure 4 This is a flow chart of a cloud platform administrator using an application publishing system in one embodiment of the present application. Figure 5 This is a flow chart of a tenant user using an application publishing system in one embodiment of the present application. Figure 4 , Figure 5 Some of the steps are user operations, and some of the steps are steps performed internally by the application publishing system 100. Figure 4 and Figure 5 The above steps S110 to S150 are described in detail:

[0069] In step S110, the configuration information of the cloud platform administrator is obtained, and the various publishing platforms are managed and connected to the application publishing system according to the configuration information of the cloud platform administrator. Figure 4 Step S410 and step S420 in .

[0070] In some embodiments, after the step of managing and connecting multiple publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator, it also includes: detecting the connection status between the publishing platform and the application publishing system according to a preset period; if the connection status is a connection failure, an alarm is sent to the cloud platform administrator. Exemplarily, this step corresponds to Figure 4 Step S430, step S440, step S441. This application can ensure the availability of the system by setting up a publishing platform connectivity fault detection mechanism, and present it in time when facing hardware failures or abnormal situations, which is convenient for operation and maintenance personnel to handle.

[0071] In step S120, the non-managed resources of the publishing platform are obtained and synchronized to the database. Figure 4 Step S450 and step S460 in .

[0072] In step S130, the tenant and the publishing platform are bound. For example, step S130 corresponds to Figure 4 Steps S470, S480, and S490 in the process.

[0073] Exemplarily, the configuration of the platform management end is the core of the application publishing system 100 , and its main function is to achieve unified management and control of multiple publishing platforms and to bind relationships with tenants so that tenant-side users can use the application publishing system 100 normally.

[0074] Combination Figure 2 and Figure 4As shown, exemplarily, first, the cloud platform administrator configures the management access of different publishing platforms through the platform management and docking management module 123, that is, adds, edits and removes publishing platforms in the application publishing system 100. While managing and docking, it supports the configuration of different API (Application Programming Interface) request interaction authentication methods for different publishing platforms. The method of adding a publishing platform requires the information and type of the publishing platform to be passed in and registered with the system. The method of removing a publishing platform requires the identification of the publishing platform to be passed in, remove it from the system, and release the corresponding resources, and the publishing task will not be scheduled to the platform. At the same time, in order to improve the scalability of the system, the platform management and docking management module 123 supports the horizontal expansion and management of multiple publishing platforms in implementation, and adjusts the configuration of the publishing platform according to different publishing platform types and characteristics to adapt to system changes and uncertainties. It supports periodic detection of publishing platform connectivity, and if the platform status is unavailable, it will be displayed in time to inform the cloud platform administrator to handle it.

[0075] Secondly, the platform resource synchronization module 125 is used to configure the resource synchronization tasks at the platform level as needed to ensure that the internal resources of the platform that are not managed can be automatically synchronized into the warehouse for use when publishing. The platform resource synchronization cycle strategy can be flexibly configured, and the strategy can be configured at the granularity of minutes, hours, days, months, etc. The synchronization execution of platform resources can also be manually triggered to perform synchronization in a timely manner in an emergency.

[0076] Again, the cloud platform administrator can manage the configuration policy of the correspondence between tenants and platforms through the platform tenant authorization module 122 on the platform side, and can authorize different publishing platforms to different tenants, so as to achieve isolation between tenants and different platforms on the tenant side. After the cloud platform administrator first manages and connects the publishing platform on the platform side, he can authorize and bind the relationship between the specific publishing platform and the specific tenant. Exemplarily, the correspondence between the platform and the tenant is one-to-many, that is, multiple different tenants can use the same publishing platform for publishing, but the same tenant cannot use different publishing platforms, and the tenant who has bound the platform cannot be bound to a different publishing platform again. And the binding relationship between the tenant and the publishing platform can be removed, and after the removal, it can be bound to other publishing platforms again, and then the publishing operations performed by the tenant will be distributed to the newly bound publishing platform.

[0077] In step S140, the login information of the tenant user is obtained and verified, and after the verification is passed, the relevant interactive interface in the application publishing process is displayed. Figure 5 Step S510, step S520, step S530, step S531, step S540.

[0078] In step S150, the configuration information of the tenant user is obtained, and the application publishing task is executed according to the configuration information of the tenant user and the publishing platform. Figure 5 Steps S541~S590 and steps S610~S630.

[0079] In some embodiments, the step of executing the application publishing task according to the configuration information of the tenant user and the publishing platform includes: allocating the application to the corresponding bound publishing platform according to the configuration information and publishing operation of the tenant user; and recording the publishing operation log of the application.

[0080] Combination Figure 2 and Figure 5 As shown, exemplarily, the tenant side is mainly for users who need to use the application publishing function. When the tenant side user logs in to the system, the identity authentication module is used for identity authentication first, and the application publishing system 100 is logged in after the authentication is passed. Secondly, when the tenant user performs the application publishing operation, the identity authentication and access control module 121 will be passed. This module mainly implements the scheduling and allocation of publishing tasks, implements task scheduling according to the tenants bound to the publishing platform on the platform side, and reasonably allocates the publishing tasks to different publishing platforms. The core implementation idea of ​​this module is: since the platform side has performed the authorization configuration of tenants and publishing platforms, thereby determining the publishing platform that a tenant should request or operate, when an ordinary user logs in to the system, the tenant to which he belongs is determined, and the authorized publishing platform can be determined. Further, it can be determined according to the current tenant to which the application publishing task is sent for scheduling.

[0081] Exemplarily, when the API of the tenant user's publishing request is processed by the access control module and the publishing platform to be scheduled is determined, the application can be published and managed through the publishing management module 124. The publishing management module 124 provides users with a unified publishing standard process abstraction to shield the differences between different publishing platforms.

[0082] This application manages the publishing platform on the platform side and configures the tenant relationship binding. When performing application publishing operations on the tenant side, the current tenant and the configured platform authorized tenant can be compared to determine the publishing platform to be used by the current tenant. Through the implementation steps on the platform side and the tenant side, the horizontal expansion and disaster recovery capabilities of multiple publishing platforms can be achieved.

[0083] The present application also includes a computer-readable medium storing a computer program code, which implements the software publishing method described above when executed by a processor.

[0084] When the software publishing method is implemented as a computer program, it can also be stored in a computer-readable storage medium as a product. For example, a computer-readable storage medium can include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD), a digital versatile disk (DVD)), a smart card, and a flash memory device (e.g., an electrically erasable programmable read-only memory (EPROM), a card, a stick, a key drive). In addition, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" can include, but is not limited to, wireless channels and various other media (and / or storage media) that can store, contain and / or carry code and / or instructions and / or data.

[0085] It should be understood that the embodiments described above are only illustrative. The embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processor may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and / or other electronic units designed to perform the functions described herein, or a combination thereof.

[0086] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0087] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0088] The basic concepts have been described above. Obviously, for those skilled in the art, the above application disclosure is only an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0089] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0090] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of the present application are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

Claims

1. An application publishing system, characterized in that: include: The presentation layer is used to provide a user interface and obtain user configuration information; The publishing system platform layer is used to deploy multiple publishing platforms, which are used to publish applications. An application layer, used to bind the tenant to the publishing platform according to the configuration information, the application layer comprising: a platform management and docking management module, a platform resource synchronization module, and a platform tenant authorization module, or any combination thereof; The logic layer is used to perform logical abstraction and encapsulation of the services of each module in the application layer.

2. The application publishing system according to claim 1, characterized in that: The user includes a cloud platform administrator; the platform management and docking management module is configured to: perform management and docking of the tenant and the publishing platform according to user instructions and manage the authentication information of the publishing platform; The platform resource synchronization module is configured to: obtain non-managed resources of the publishing platform, synchronize the non-managed resources to the database; manage the resource synchronization cycle of the publishing platform according to user instructions; The platform tenant authorization module is configured to manage the authorization binding relationship between the tenant and the publishing platform according to a configuration policy.

3. The application publishing system according to claim 1 or 2, characterized in that: The users include tenant users; The application layer is also used to execute application publishing tasks according to the configuration information and the publishing platform, and the application layer also includes: one or any combination of identity authentication and access control module, publishing management module, and log audit module; wherein, The identity authentication and access control module is configured to: verify the identity of the user according to the login information and log in to the application publishing system after the verification; determine the corresponding publishing platform according to the tenant information to which the user belongs; and assign the application publishing task to the corresponding bound publishing platform according to the publishing operation of the user; The release management module is configured to: release and manage the application according to user instructions; and display the application release standard process to the user; The log audit module is configured to record a release operation log of the application, wherein the release operation log includes one or any combination of a security log, a system log, and a business log.

4. The application publishing system according to claim 1, characterized in that: The user interaction interface comprises: Tenant user interface, including tenant user login authentication interface and related interactive interfaces during application publishing; The platform management interface includes the management interface for cloud platform administrators to configure and publish the platform, the tenant authorization interface, and the resource synchronization interface.

5. The application publishing system according to claim 1, characterized in that: One publishing platform is bound to one tenant or multiple tenants, and one tenant is bound to one publishing platform.

6. The application publishing system according to claim 1, characterized in that: It also includes a data layer, which includes a database and a cache library. The database is used to store user data, log data, permission configuration data, and resource information; the cache library is used to improve the reading speed of data access.

7. The application publishing system according to claim 1, characterized in that: It also includes an infrastructure layer, and the hardware resources of the infrastructure layer include: one or any combination of servers, storage devices, network devices, and load balancers.

8. An application publishing method, characterized in that: Using the application publishing system as described in any one of claims 1 to 7, comprising: Obtain configuration information of a cloud platform administrator, and manage and connect multiple publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator; Acquire non-managed resources of the publishing platform, and synchronize the non-managed resources to the database; Binding the tenant to the publishing platform; Obtain and verify the tenant user's login information, and display the relevant interactive interface during the application release process after verification; The configuration information of the tenant user is obtained, and the application publishing task is executed according to the configuration information of the tenant user and the publishing platform.

9. The application publishing method according to claim 8, characterized in that: After the step of managing and connecting multiple publishing platforms to the application publishing system according to the configuration information of the cloud platform administrator, it also includes: detecting the connection status between the publishing platform and the application publishing system according to a preset period; if the connection status is a connection failure, an alarm is sent to the cloud platform administrator.

10. The application publishing method according to claim 8, characterized in that: The step of executing the application publishing task by the publishing platform according to the configuration information of the tenant user includes: Allocating the application to a corresponding bound publishing platform according to the configuration information and publishing operation of the tenant user; Record the release operation log of the application.

Images