Project starting method and device, computer device and storage medium

Abstract

The application belongs to the fields of big data and financial technology, and relates to a project starting method, which comprises the following steps: extracting user information from a received starting request, and performing permission verification on the user based on the user information and a permission level model; if the user passes the permission verification, it is judged whether first dependency relationship data is stored in a local cache; if the first dependency relationship data is not stored in the local cache, it is judged whether second dependency relationship data is stored in a Redis cache; if the second dependency relationship data is not stored in the Redis cache, but third dependency relationship data is stored in a remote service, the third dependency relationship data is acquired from the remote service; and the target project is processed based on the third dependency relationship data. The application also provides a project starting device, a computer device and a storage medium. In addition, the third dependency relationship data can be stored in a block chain. The application effectively improves the starting speed of the target project based on the use of the cache.

Description

Technical Field

[0001] This application relates to the fields of big data technology and fintech, and in particular to project initiation methods, devices, computer equipment and storage media. Background Technology

[0002] In the financial and insurance sector, the construction and maintenance of a benefits system has become a crucial aspect in improving business marketing effectiveness. A benefits system provides users with a flexible and diverse benefits experience by defining and managing various benefits packages (typically containing services, resources, or privileges available to users). However, with the expansion of business scale and the increase in the types of benefits, the dependencies between benefits packages have become increasingly complex, forming a vast and intertwined web of dependencies.

[0003] In existing technologies, to efficiently handle these complex dependencies during the runtime of the rights system, dependency loading code is typically executed before the local project of the rights system starts to load the rights package dependencies into local memory. However, since the number of rights packages involved in the rights package dependencies is very large, when running the dependency loading code, it is necessary to start the analysis from the root node and then query the database for information on the dependent rights packages one by one. Since database query operations are extremely time-consuming, this results in a long startup time and low startup speed for the local project. Summary of the Invention

[0004] The purpose of this application is to provide a project startup method, apparatus, computer equipment, and storage medium to solve the technical problems of long startup time and low startup speed of existing local project startup methods.

[0005] To address the aforementioned technical problems, this application provides a project initiation method, employing the following technical solution:

[0006] Determine whether a user-triggered launch request for the target project has been received; wherein the launch request carries the user's user information;

[0007] If so, extract the user information from the startup request, and verify the user's permissions based on the user information and a preset permission level model;

[0008] If the user passes the permission verification, then determine whether the first dependency data of the specified version corresponding to the target project is stored in the preset local cache;

[0009] If the first dependency relationship data is not stored in the local cache, it is determined whether second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache;

[0010] If the second dependency relationship data is not stored in the Redis cache, it is determined whether third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service;

[0011] If the third dependency relationship data is stored in the remote service, the third dependency relationship data is obtained from the remote service;

[0012] Based on the third dependency relationship data, the target project is started.

[0013] Further, after the step of determining whether the third dependency relationship data of the specified version corresponding to the target project is stored in the preset remote service, the method further comprises:

[0014] If the third dependency relationship data is not stored in the remote service, dependency relationship loading code corresponding to the target project is obtained;

[0015] The dependency relationship loading code is executed to load fourth dependency relationship data corresponding to the specified version from a preset data source;

[0016] The fourth dependency relationship data is data verified;

[0017] If the fourth dependency relationship data passes the data verification, the target project is started based on the fourth dependency relationship data.

[0018] Further, the step of data verifying the fourth dependency relationship data specifically comprises:

[0019] The integrity of the fourth dependency relationship data is checked;

[0020] If the fourth dependency relationship data passes the integrity check, the consistency of the fourth dependency relationship data is checked;

[0021] If the fourth dependency relationship data passes the consistency check, it is determined that the fourth dependency relationship data passes the data verification, otherwise it is determined that the fourth dependency relationship data does not pass the data verification.

[0022] Further, after the step of starting the target project based on the fourth dependency relationship data, the method further comprises:

[0023] The fourth dependency relationship data is format encapsulated to obtain target dependency relationship data;

[0024] pushing the target dependency data to the remote service;

[0025] performing a first cache update process on the Redis cache based on the fourth dependency data, and setting a first cache expiration time corresponding to the fourth dependency data in the Redis cache;

[0026] performing a second cache update process on the local cache based on the fourth dependency data, and setting a second cache expiration time corresponding to the fourth dependency data in the local cache.

[0027] Further, the step of performing a first cache update process on the Redis cache based on the fourth dependency data specifically comprises:

[0028] determining whether expired dependency data corresponding to the target item is stored in the Redis cache;

[0029] If the Redis cache does not store the expired dependency data, determining a target data structure corresponding to the fourth dependency data;

[0030] storing the fourth dependency data into the Redis cache based on the target data structure;

[0031] If the Redis cache stores the expired dependency data, performing data replacement processing on the expired dependency data using the fourth dependency data.

[0032] Further, the step of performing permission verification on the user based on the user information and a preset permission level model specifically comprises:

[0033] calling the permission level model and obtaining a preset business operation permission table;

[0034] obtaining a target permission level corresponding to the user information based on the permission level model;

[0035] querying a specified permission level range corresponding to a business operation started by the local item from the business operation permission table;

[0036] determining whether the target permission level is within the specified permission level range;

[0037] If yes, determining that the user passes the permission verification, otherwise determining that the user does not pass the permission verification.

[0038] Further, after the step of judging whether the first dependency relationship data corresponding to the target item is stored in the preset local cache, the method further comprises:

[0039] If the first dependency relationship data is stored in the local cache, the first dependency relationship data is acquired from the local cache;

[0040] The target item is started based on the first dependency relationship data.

[0041] To solve the above technical problems, the embodiment of the application further provides a project starting device, which adopts the technical scheme as follows:

[0042] The first judging module is configured to judge whether a starting request for a target item triggered by a user is received, wherein the starting request carries user information of the user;

[0043] The first verifying module is configured to, if yes, extract the user information from the starting request and perform permission verification on the user based on the user information and a preset permission level model;

[0044] The second judging module is configured to, if the user passes the permission verification, judge whether first dependency relationship data corresponding to a specified version of the target item is stored in a preset local cache;

[0045] The third judging module is configured to, if the first dependency relationship data is not stored in the local cache, judge whether second dependency relationship data corresponding to the specified version of the target item is stored in a preset Redis cache;

[0046] The fourth judging module is configured to, if the second dependency relationship data is not stored in the Redis cache, judge whether third dependency relationship data corresponding to the specified version of the target item is stored in a preset remote service;

[0047] The first acquiring module is configured to, if the third dependency relationship data is stored in the remote service, acquire the third dependency relationship data from the remote service;

[0048] The first starting module is configured to start the target item based on the third dependency relationship data.

[0049] To solve the above technical problems, the embodiment of the application further provides a computer device, which adopts the technical scheme as follows:

[0050] Whether a starting request for a target item triggered by a user is received is judged, wherein the starting request carries user information of the user;

[0051] If yes, the user information is extracted from the start request, and the user is verified based on the user information and a preset permission level model;

[0052] If the user passes the permission verification, it is judged whether the first dependency relationship data of a specified version corresponding to the target project is stored in a preset local cache;

[0053] If the first dependency relationship data is not stored in the local cache, it is judged whether the second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache;

[0054] If the second dependency relationship data is not stored in the Redis cache, it is judged whether the third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service;

[0055] If the third dependency relationship data is stored in the remote service, the third dependency relationship data is acquired from the remote service;

[0056] The target project is started based on the third dependency relationship data.

[0057] To solve the above technical problems, the embodiment of the application also provides a computer readable storage medium, which adopts the technical scheme as follows:

[0058] It is judged whether a start request for a target project triggered by a user is received; wherein the start request carries user information of the user;

[0059] If yes, the user information is extracted from the start request, and the user is verified based on the user information and a preset permission level model;

[0060] If the user passes the permission verification, it is judged whether the first dependency relationship data of a specified version corresponding to the target project is stored in a preset local cache;

[0061] If the first dependency relationship data is not stored in the local cache, it is judged whether the second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache;

[0062] If the second dependency relationship data is not stored in the Redis cache, it is judged whether the third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service;

[0063] If the third dependency relationship data is stored in the remote service, the third dependency relationship data is acquired from the remote service;

[0064] perform a starting process on the target project based on the third dependency relationship data.

[0065] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0066] The present application first determines whether a starting request for a target project triggered by a user is received; wherein the starting request carries user information of the user; if so, the user information is extracted from the starting request, and the user is verified for permission based on the user information and a preset permission level model; if the user passes the permission verification, it is determined whether first dependency relationship data of a specified version corresponding to the target project is stored in a preset local cache; if the first dependency relationship data is not stored in the local cache, it is determined whether second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache; if the second dependency relationship data is not stored in the Redis cache, it is determined whether third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service; if the third dependency relationship data is stored in the remote service, the third dependency relationship data is obtained from the remote service; finally, a starting process is performed on the target project based on the third dependency relationship data. After receiving the starting request for the target project triggered by the user, and passing the permission verification of the user based on the user information and the preset permission level model, the present application intelligently uses the way of extracting dependency relationship data from the cache level corresponding to the local cache, the local cache or the remote service to obtain the dependency relationship data for starting the target project, so that it is not necessary to execute the dependency relationship loading code again when starting the target project, and the time spent for extracting the dependency relationship data from the cache level is extremely small, thereby greatly reducing the starting time of the target project and effectively improving the starting speed of the target project. BRIEF DESCRIPTION OF DRAWINGS

[0067] In order to more clearly illustrate the schemes in the present application, the drawings needed in the description of the embodiments of the present application will be briefly introduced as follows. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0068] Figure 1 is an exemplary system architecture diagram to which the present application can be applied;

[0069] Figure 2 a flowchart of one embodiment of the project starting method according to the present application;

[0070] Figure 3 is a structural schematic diagram of an embodiment of the project starting device according to the application;

[0071] Figure 4 is a structural schematic diagram of an embodiment of the computer device according to the application. DETAILED DESCRIPTION

[0072] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description herein is for describing particular embodiments only and is not intended to be limiting of the application; the use herein of terms such as "comprise" and "have" and any variations thereof are intended to cover a non-exclusive inclusion; the use herein of terms such as "first", "second" and the like are intended to distinguish between similar objects unless the context indicates otherwise.

[0073] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase that "an embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive or alternative embodiments. It is expressly understood that the embodiments described herein are merely examples from a whole class of comparable embodiments which those skilled in the art will readily appreciate.

[0074] In order to make the technical personnel in the art better understand the scheme of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings.

[0075] As shown in Figure 1 , the system architecture 100 can include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a communication link medium between the terminal devices 101, 102, 103 and the server 105. The network 104 can include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0076] A user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0077] The terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 (Moving Picture Experts Group Audio Layer III) players, MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop computers, desktop computers, and the like.

[0078] The server 105 can be a server providing various services, for example, a background server providing support for a page displayed on the terminal devices 101, 102, 103.

[0079] It should be noted that the project starting method provided by the embodiments of the present application is generally executed by a server / terminal device, and accordingly, the project starting apparatus is generally arranged in a server / terminal device.

[0080] It should be understood that Figure 1 The number of terminal devices, networks, and servers in

[0081] With reference to Figure 2 , a flow chart of one embodiment of the project starting method according to the present application is shown. The order of the steps in the flow chart can be changed according to different needs, and some steps can be omitted. The project starting method provided by the embodiments of the present application can be applied to any scenario requiring project starting, and thus the project starting method can be applied to products in these scenarios, for example, project starting related to equity packages in the field of finance and insurance. The project starting method includes the following steps:

[0082] Step S201: determining whether a starting request for a target project triggered by a user is received; wherein the starting request carries user information of the user.

[0083] In the present embodiment, the electronic device (for example, a server or a terminal device) on which the project starting method runs can be any electronic device capable of running the project starting method, and thus the electronic device can be any electronic device capable of running the project starting method. Figure 1The server / terminal device shown) can be obtained by wired connection or wireless connection. It should be noted that the above-mentioned wireless connection can include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other now known or future developed wireless connection. The present application can be applied to the start-up scenario of the local project of the equity system developed by the insurance enterprise. The above-mentioned user can be the operation and maintenance personnel related to the permission system. The above-mentioned equity system includes a large number of equity packages. Equity package is a marketing method, which is mainly a discount package built for the sale of a product or service. In addition, it also involves the definition of the privileges and discounts enjoyed by customers after purchase. The above-mentioned target project can refer to the local project in the equity system. The above-mentioned user information refers to the name information of the user.

[0084] Step S202, if yes, extract the user information from the start-up request, and perform permission verification on the user based on the user information and a preset permission level model.

[0085] In this embodiment, the user information can be extracted from the start-up request by information analysis on the start-up request. The specific implementation process of performing permission verification on the user based on the user information and a preset permission level model will be further described in detail in the subsequent specific embodiments, and will not be described here.

[0086] Step S203, if the user passes the permission verification, it is judged whether the first dependency relationship data of the specified version corresponding to the target project is stored in the preset local cache.

[0087] In the embodiment, the local cache refers to a local cache set in the electronic device. The local cache is the fastest but has limited capacity, and is suitable for a scenario of frequent access and small data amount. The dependency data refers to a dependency of an interest package corresponding to the target project. The specified version refers to the latest version. The local cache can be matched with data by obtaining the project name of the target project and using the project name and the specified version. If the first data result matched with the project name and the specified version exists in the local cache, it is determined that the first dependency data corresponding to the specified version of the target project is stored in the local cache, and the first data result is taken as the first dependency data. If the first data result matched with the project name and the specified version does not exist in the local cache, it is determined that the first dependency data corresponding to the specified version of the target project is not stored in the local cache. If the first dependency data corresponding to the specified version of the target project is not stored in the local cache, the dependency data stored in the local cache may be outdated. Alternatively, the dependency or the interest package information of the dependency data is changed, but is not updated in the local cache. The interest package information includes version information, and the version information can be used to determine whether the interest package information is updated.

[0088] In step S204, if the first dependency data is not stored in the local cache, it is determined whether second dependency data corresponding to the specified version of the target project is stored in the preset Redis cache.

[0089] In the embodiment, the Redis cache refers to a Redis cache set in the electronic device. The Redis cache is an open source Key-Value database written in ANSIC language, supports network, can be based on memory or persistent, is a log type, and provides APIs in multiple languages. The Redis cache serves as an intermediate layer, has the advantages of high-speed access and distributed storage, and is suitable for a scenario of large data amount and shared access. The Redis cache can be matched with data by obtaining the project name of the target project and using the project name and the specified version. If the second data result matched with the project name and the specified version exists in the Redis cache, it is determined that the second dependency data corresponding to the specified version of the target project is stored in the Redis cache, and the second data result is taken as the second dependency data. If the second data result matched with the project name and the specified version does not exist in the Redis cache, it is determined that the second dependency data corresponding to the specified version of the target project is not stored in the Redis cache. If the second dependency data corresponding to the specified version of the target project is not stored in the Redis cache, the dependency data stored in the Redis cache may be outdated. Alternatively, the dependency or the interest package information of the dependency data is changed, but is not updated in the Redis cache.

[0090] In step S205, if the second dependency data is not stored in the Redis cache, it is determined whether third dependency data corresponding to the specified version of the target project is stored in a preset remote service.

[0091] In the embodiment, the remote service is a data source of the dependency data of the target project, and is used for processing data updating and storing, but has the slowest access speed. The project name of the target project can be acquired, and the project name is used to perform data matching on the remote service with the specified version. If there is third data result matching the project name and the specified version in the remote service, it is determined that the third dependency data is stored in the remote service, and the third data result is used as the third dependency data. If there is no third data result matching the project name and the specified version in the remote service, it is determined that the third dependency data is not stored in the remote service. If the third dependency data corresponding to the specified version of the target project is not stored in the remote service, the dependency data stored in the remote service may be outdated. Alternatively, the dependency or the interest package information of the dependency data is changed, but the remote service is not updated in time.

[0092] In step S206, if the third dependency data is stored in the remote service, the third dependency data is acquired from the remote service.

[0093] In the embodiment, after it is detected that the third dependency data is stored in the remote service, the third dependency data is directly extracted from the remote service.

[0094] In step S207, the target project is started based on the third dependency data.

[0095] In the embodiment, the third dependency data acquired from the remote service is directly used to start the target project, so that the dependency dependency loading code does not need to be executed again. The time spent for extracting the third dependency data from the remote service is extremely small and can be ignored, and thus the starting speed of the target project can be greatly improved.

[0096] The application receives a starting request triggered by a user for a target project, and after passing the permission verification of the user based on the user information and a preset permission level model, the application intelligently extracts dependency relationship data from a cache level corresponding to a local cache, a local cache or a remote service to obtain the dependency relationship data for starting the target project, so that the dependency relationship loading code does not need to be executed again when the target project is started, and the time spent for extracting the dependency relationship data from the cache level is extremely small, thereby greatly reducing the starting time of the target project and effectively improving the starting speed of the target project.

[0097] In some optional implementations of the embodiment, after step S205, the electronic device can further perform the following steps:

[0098] If the third dependency relationship data is not stored in the remote service, the dependency relationship loading code corresponding to the target project is obtained.

[0099] In the embodiment, the dependency relationship loading code is a code for reading the latest version of the dependency relationship data of the target project from the database. The construction process of the dependency relationship loading code includes: determining the storage location of the dependency relationship data of the target project in advance, i.e., the database. The dependency relationship data of the target project can be stored in a relational database (such as a MySQL or Postgr eSQL database) or a non-relational database (such as a MongoDB database). Then, a suitable data model is designed according to the corresponding data source of the dependency relationship data of the target project. If the data is stored in the database, the database table structure, field type and index need to be defined. Subsequently, the code for accessing the data source, i.e., the dependency relationship loading code, is written. The code content includes a database access layer (DAO). Database access: using JDBC, an ORM framework (such as Hibernate or MyBatis) or other database access technologies to query the dependency relationship data corresponding to the target project in the database.

[0100] The dependency relationship loading code is executed to load fourth dependency relationship data corresponding to the specified version from a preset data source.

[0101] In the embodiment, the preset data source is specifically a database. By executing the dependency relationship loading code, a SQL query statement is executed, the dependency relationship data corresponding to the target project is obtained from the database, and the dependency relationship data is mapped to a Java object to obtain the fourth dependency relationship data.

[0102] The fourth dependency relationship data is verified.

[0103] In the embodiment, after the fourth dependency data corresponding to the specified version is loaded from the preset data source, the fourth dependency data is intelligently verified to ensure the integrity and consistency of the fourth dependency data. The specific implementation process of the data verification of the fourth dependency data will be further described in detail in subsequent embodiments, and will not be described in detail here.

[0104] If the fourth dependency data passes the data verification, the target project is started based on the fourth dependency data.

[0105] In the embodiment, if it is detected that the third dependency data corresponding to the target project is not stored in the remote service, a dependency loading code corresponding to the target project is intelligently executed to load fourth dependency data corresponding to the specified version from a preset data source, and then the target project is started based on the fourth dependency data, so that the smooth starting of the target project can be ensured.

[0106] If it is detected that the third dependency data corresponding to the target project of the specified version is not stored in the remote service, a dependency loading code corresponding to the target project is obtained, and the dependency loading code is executed to load fourth dependency data corresponding to the specified version from a preset data source. The fourth dependency data is subsequently verified. If the fourth dependency data passes the data verification, the target project is started based on the fourth dependency data. When it is detected that the first dependency data corresponding to the target project of the specified version is not stored in the local cache, the second dependency data corresponding to the target project of the specified version is not stored in the Redis cache, and the third dependency data corresponding to the target project of the specified version is not stored in the remote service, a dependency loading code corresponding to the target project is intelligently executed to load fourth dependency data corresponding to the specified version from a preset data source, and then the target project is started based on the fourth dependency data, so that the smooth starting of the target project can be effectively ensured, and the starting intelligence and stability of the target project are improved.

[0107] In some optional implementations, the data verification of the fourth dependency data includes the following steps:

[0108] The integrity of the fourth dependency data is checked.

[0109] In the embodiment, the integrity check refers to detecting whether all the required fields and records are contained in the fourth dependency data. The required fields and records can be set according to actual dependency check requirements. For example, it can be ensured that each entitlement package has a unique identifier, and each dependency clearly indicates the dependent entitlement package. In addition, if all the required fields and records are contained in the fourth dependency data, it is determined that the fourth dependency data passes the integrity check. If all the required fields and records are not contained in the fourth dependency data, it is determined that the fourth dependency data fails the integrity check, and further, it is determined that the fourth dependency data fails the data verification.

[0110] If the fourth dependency data passes the integrity check, consistency check is performed on the fourth dependency data.

[0111] In the embodiment, the consistency check refers to detecting whether there is a logical contradiction or inconsistency in the fourth dependency data. Specifically, it can be detected whether the dependency forms a circular dependency, whether the version number of the entitlement package meets the expected order, and the like. If there is no logical contradiction or inconsistency in the fourth dependency data, it is determined that the fourth dependency data passes the consistency check, otherwise, it is determined that the fourth dependency data fails the consistency check.

[0112] If the fourth dependency data passes the consistency check, it is determined that the fourth dependency data passes the data verification, otherwise, it is determined that the fourth dependency data fails the data verification.

[0113] In the embodiment, only when it is detected that the fourth dependency data passes both the integrity check and the consistency check, it is determined that the fourth dependency data passes the data verification, otherwise, it is determined that the fourth dependency data fails the data verification.

[0114] The application performs integrity check and consistency check on the fourth dependency data. Only when it is detected that the fourth dependency data passes both the integrity check and the consistency check, it is determined that the fourth dependency data passes the data verification, otherwise, it is determined that the fourth dependency data fails the data verification, which effectively improves the processing accuracy of the data verification of the fourth dependency data and ensures the accuracy of the generated data verification result.

[0115] In some optional implementation manners of the embodiment, after the step of performing data verification on the fourth dependency data, the electronic device can further perform the following steps:

[0116] The fourth dependency relationship data is subjected to a format packaging process to obtain target dependency relationship data.

[0117] In this embodiment, the format packaging process can include packaging the fourth dependency relationship data in a JSON, XML or other format.

[0118] The target dependency relationship data is pushed to the remote service.

[0119] In this embodiment, the target dependency relationship data can be pushed to the remote service using the HTTP (Hypertext Transfer Protocol) protocol. After receiving the target dependency relationship data, the remote service performs corresponding verification and processing on the target dependency relationship data, and then stores the target dependency relationship data in a corresponding database.

[0120] The Redis cache is subjected to a first cache update process based on the fourth dependency relationship data, and a first cache expiration time corresponding to the fourth dependency relationship data is set in the Redis cache.

[0121] In this embodiment, the value of the first cache expiration time can be set according to actual business processing requirements. By setting the first cache expiration time corresponding to the fourth dependency relationship data in the Redis cache, the expired data can be prevented from being cached for a long time, thereby improving the cache intelligence of the dependency relationship data in the Redis cache. The specific implementation process of the first cache update process based on the fourth dependency relationship data on the Redis cache will be described in further detail in subsequent embodiments.

[0122] The local cache is subjected to a second cache update process based on the fourth dependency relationship data, and a second cache expiration time corresponding to the fourth dependency relationship data is set in the local cache.

[0123] In the embodiment, the process of performing the second cache update processing on the local cache based on the fourth dependency data includes: judging whether the specified expired dependency data corresponding to the target project is stored in the local cache; if the specified expired dependency data is not stored in the local cache, storing the fourth dependency data in the local cache; and if the specified expired dependency data is stored in the local cache, performing data replacement processing on the specified expired dependency data using the fourth dependency data. The data replacement processing refers to replacing the specified expired dependency data in the local cache with the fourth dependency data. In addition, the value of the second cache expiration time can be set according to actual business processing requirements. By setting the second cache expiration time corresponding to the fourth dependency data in the local cache, the expired data can be avoided from being cached for a long time, thereby improving the cache intelligence of the dependency data in the local cache.

[0124] After detecting that the fourth dependency data passes the data verification, the application further performs format packaging processing on the fourth dependency data to obtain target dependency data, and pushes the target dependency data to the remote service. In addition, the application performs first cache update processing on the Redis cache based on the fourth dependency data, and sets a first cache expiration time corresponding to the fourth dependency data in the Redis cache. The application also performs second cache update processing on the local cache based on the fourth dependency data, and sets a second cache expiration time corresponding to the fourth dependency data in the local cache. In this way, the updated fourth dependency data obtained by executing the dependency loading code can be synchronized and updated to all cache levels, i.e., the remote service, the Redis cache, and the local cache, thereby effectively ensuring the data consistency of the dependency data in each cache level. In addition, when a subsequent start request for the target project is received, the fourth dependency data can be directly extracted from the various cache levels and used to start the target project, so that it is not necessary to execute the dependency dependency loading code again. The time spent on extracting the fourth dependency data from the cache level is extremely small and can be ignored, thereby greatly reducing the start time of the target project and effectively improving the start speed of the target project.

[0125] In some optional implementations, the first cache update processing on the Redis cache based on the fourth dependency data includes the following steps:

[0126] Judging whether expired dependency data corresponding to the target project is stored in the Redis cache.

[0127] In the embodiment, the project name of the target project is acquired, and data matching is performed on the Redis cache using the project name. If there is data result matched with the project name in the Redis cache, it is determined that the expired dependency relationship data is stored in the Redis cache, and the data result matched with the project name is the expired dependency relationship data. If there is no data result matched with the project name in the Redis cache, it is determined that the expired dependency relationship data is not stored in the Redis cache.

[0128] If the expired dependency relationship data is not stored in the Redis cache, the target data structure corresponding to the fourth dependency relationship data is determined.

[0129] In the embodiment, the target data structure can be any one of Hashes, Sets, Sorted Sets and the like.

[0130] The fourth dependency relationship data is stored in the Redis cache based on the target data structure.

[0131] In the embodiment, the fourth dependency relationship data is stored in the Redis cache using the target data structure, so as to be quickly queried and updated.

[0132] If the expired dependency relationship data is stored in the Redis cache, the expired dependency relationship data is replaced with the fourth dependency relationship data.

[0133] In the embodiment, the data replacement processing refers to replacing the expired dependency relationship data in the Redis cache with the fourth dependency relationship data.

[0134] The application determines whether the expired dependency relationship data corresponding to the target item is stored in the Redis cache; if the expired dependency relationship data is not stored in the Redis cache, a target data structure corresponding to the fourth dependency relationship data is determined; then the fourth dependency relationship data is stored in the Redis cache based on the target data structure; and if the expired dependency relationship data is stored in the Redis cache, the fourth dependency relationship data is used to perform data replacement processing on the expired dependency relationship data. When it is detected that the expired dependency relationship data is not stored in the Redis cache, the fourth dependency relationship data is intelligently stored in the Redis cache using the target data structure corresponding to the fourth dependency relationship data, thereby completing the first cache update processing of the Redis cache. In addition, when it is detected that the expired dependency relationship data is stored in the Redis cache, the fourth dependency relationship data is intelligently used to perform data replacement processing on the expired dependency relationship data, thereby completing the first cache update processing of the Redis cache, effectively improving the processing adaptability and processing intelligence of the first cache update processing of the Redis cache using the fourth dependency relationship data.

[0135] In some optional implementations of the embodiment, the permission verification of the user based on the user information and the preset permission level model in step S202 includes the following steps:

[0136] The permission level model is called, and a preset business operation permission table is obtained.

[0137] In the embodiment, the above-mentioned permission level model is a big data model pre-constructed to store a one-to-one mapping relationship between employee name information of an enterprise employee and a permission level. The above-mentioned business operation permission table is a data table pre-constructed to store a plurality of business operation identifiers and a permission level range corresponding to each business operation identifier. The business operation identifier has uniqueness, and one business operation corresponds to one business operation identifier.

[0138] The target permission level corresponding to the user information is obtained based on the permission level model.

[0139] In the embodiment, the permission level model can be queried using the above-mentioned user information to obtain the target permission level corresponding to the user information.

[0140] The specified permission level range corresponding to the business operation started by the local item is queried from the business operation permission table.

[0141] In the embodiment, the specified business operation identifier corresponding to the business operation initiated by the local project can be acquired, and then the specified business operation identifier is used to query the business operation permission table to obtain the specified permission level interval corresponding to the business operation initiated by the local project.

[0142] It is judged whether the target permission level is in the specified permission level range.

[0143] In the embodiment, the target permission level can be compared with two end point values included in the specified permission level range to obtain a corresponding numerical comparison result, and whether the target permission level is in the specified permission level range is identified according to the numerical comparison result.

[0144] If yes, it is determined that the user passes the permission verification, otherwise it is determined that the user fails the permission verification.

[0145] In the embodiment, if the target permission level is in the specified permission level range, it indicates that the user has the business operation permission to initiate the local project, and it is determined that the user passes the permission verification. If the target permission level is not in the specified permission level range, it indicates that the user does not have the business operation permission to initiate the local project, and it is determined that the user fails the permission verification.

[0146] The application calls the permission level model, acquires a preset business operation permission table, obtains a target permission level corresponding to the user information based on the permission level model, and queries a specified permission level range corresponding to a business operation initiated by a local project from the business operation permission table. It is subsequently judged whether the target permission level is in the specified permission level range. Only when it is detected that the target permission level is in the specified permission level range, it is determined that the user has the business operation permission to initiate the local project, and it is determined that the user passes the permission verification. The processing intelligence and processing accuracy of the permission verification of the user are effectively improved, and the accuracy of the obtained permission verification result of the user is ensured. In addition, only after it is determined that the user passes the permission verification, a response process for a start request of a target project triggered by the user is subsequently executed. The intelligent processing and standardized processing of the start request of the target project are effectively improved, and the response security of the start request of the target project is ensured.

[0147] In some optional implementation manners of the embodiment, after step S203, the electronic device can further execute the following steps:

[0148] If the first dependency relationship data is stored in the local cache, the first dependency relationship data is acquired from the local cache.

[0149] In the embodiment, if the first dependency relationship data of the specified version corresponding to the target project is stored in the local cache, the first dependency relationship data is directly extracted from the local cache.

[0150] The target project is started based on the first dependency relationship data.

[0151] In the embodiment, the starting of the target project is performed by directly using the first dependency relationship data obtained from the local cache, so that the time cost for extracting the first dependency relationship data from the local cache is extremely small and can be ignored, and thus the starting speed of the target project can be greatly accelerated.

[0152] When receiving a starting request of a target project triggered by a user and determining that the user passes the permission verification, the application intelligently determines whether the first dependency relationship data of the specified version corresponding to the target project is stored in the preset local cache. If it is detected that the first dependency relationship data of the specified version corresponding to the target project is stored in the local cache, the first dependency relationship data is directly extracted from the local cache and used for starting the target project, so that the time cost for extracting the first dependency relationship data from the local cache is extremely small and can be ignored, and thus the starting time of the target project can be greatly reduced, and the starting speed of the target project is effectively improved.

[0153] In some optional implementation manners of the embodiment, if the first dependency relationship data is not stored in the local cache, it is further intelligently determined whether the second dependency relationship data of the specified version corresponding to the target project is stored in the preset Redis cache. If it is detected that the second dependency relationship data is stored in the Redis cache, the second dependency relationship data is automatically extracted from the Redis cache and used for starting the target project, so that the time cost for extracting the second dependency relationship data from the Redis cache is extremely small and can be ignored, and thus the starting time of the target project can be greatly reduced, and the starting speed of the target project is effectively improved.

[0154] It should be understood that the size of the serial number of each step in the above embodiment does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiment of the application.

[0155] It is emphasized that, in order to further ensure the privacy and security of the third dependency data, the third dependency data can also be stored in a node of a block chain.

[0156] The block chain referred to in the present application is a new application mode of distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm and other computer technologies. The block chain is essentially a decentralized database, which is a series of data blocks associated using cryptographic methods, each data block containing a batch of network transaction information for verifying the validity (anti-fake) of the information and generating the next block. The block chain can include a block chain underlying platform, a platform product service layer, and an application service layer.

[0157] Embodiments of the present application can acquire and process related data based on artificial intelligence technology. Artificial intelligence (AI) is the use of digital computers or computer-controlled machines to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0158] Artificial intelligence basic technologies generally include technologies such as sensors, special artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction system, mechatronics, etc. Artificial intelligence software technology mainly includes computer vision technology, robot technology, biometric technology, speech processing technology, natural language processing technology, and machine learning / deep learning, etc.

[0159] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by computer readable instructions instructing related hardware, and the computer readable instructions can be stored in a computer readable storage medium. When the program is executed, it can include the processes of the above-mentioned embodiments of each method. The storage medium can be a non-volatile storage medium such as a magnetic disc, an optical disc, a read-only memory (ROM), or a random access memory (RAM).

[0160] It should be understood that, although each step in the flowchart of the accompanying drawings is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in sequence according to the direction of the arrow. Unless explicitly stated herein, the execution of these steps is not strictly limited in sequence, and they can be executed in other sequences. Moreover, at least part of the steps in the flowchart of the accompanying drawings can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence is not necessarily sequential, but can be alternately executed with at least part of other steps or sub-steps or stages of other steps.

[0161] Further referring to Figure 3 , as an implementation of the method shown in the above Figure 2 , the present application provides an embodiment of a project starting device, which corresponds to the method embodiment shown in Figure 2 , and the device can be specifically applied to various electronic devices.

[0162] As shown in Figure 3 , the project starting device 300 described in the embodiment includes:

[0163] A first judging module 301 is configured to judge whether a starting request for a target project triggered by a user is received; wherein the starting request carries user information of the user;

[0164] A first verifying module 302 is configured to, if yes, extract the user information from the starting request, and perform permission verification on the user based on the user information and a preset permission level model;

[0165] A second judging module 303 is configured to, if the user passes the permission verification, judge whether first dependency relationship data of a specified version corresponding to the target project is stored in a preset local cache;

[0166] A third judging module 304 is configured to, if the first dependency relationship data is not stored in the local cache, judge whether second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache;

[0167] A fourth judging module 305 is configured to, if the second dependency relationship data is not stored in the Redis cache, judge whether third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service;

[0168] A first obtaining module 306 is configured to, if the third dependency relationship data is stored in the remote service, obtain the third dependency relationship data from the remote service;

[0169] The first starting module 307 is configured to perform starting processing on the target project based on the third dependency relationship data.

[0170] In some optional implementation of the embodiment, the project starting apparatus further includes:

[0171] The second obtaining module is configured to obtain dependency relationship loading code corresponding to the target project if the third dependency relationship data is not stored in the remote service;

[0172] The loading module is configured to execute the dependency relationship loading code to load fourth dependency relationship data corresponding to the specified version from a preset data source;

[0173] The second verifying module is configured to perform data verification on the fourth dependency relationship data;

[0174] The second starting module is configured to perform starting processing on the target project based on the fourth dependency relationship data if the fourth dependency relationship data passes the data verification.

[0175] In some optional implementation of the embodiment, the second verifying module includes:

[0176] The first checking submodule is configured to perform integrity checking on the fourth dependency relationship data;

[0177] The second checking submodule is configured to perform consistency checking on the fourth dependency relationship data if the fourth dependency relationship data passes the integrity checking;

[0178] The first determining submodule is configured to determine that the fourth dependency relationship data passes the data verification if the fourth dependency relationship data passes the consistency checking, or determine that the fourth dependency relationship data does not pass the data verification.

[0179] In some optional implementation of the embodiment, the project starting apparatus further includes:

[0180] The packaging module is configured to perform format packaging processing on the fourth dependency relationship data to obtain target dependency relationship data;

[0181] The pushing module is configured to push the target dependency relationship data to the remote service;

[0182] The first updating module is configured to perform first cache updating processing on the Redis cache based on the fourth dependency relationship data, and set a first cache expiration time corresponding to the fourth dependency relationship data in the Redis cache;

[0183] The second updating module is configured to perform a second cache updating process on the local cache based on the fourth dependency data, and set a second cache expiration time corresponding to the fourth dependency data in the local cache.

[0184] In some optional implementations of the embodiment, the first updating module includes:

[0185] The first judging submodule is configured to judge whether expired dependency data corresponding to the target item is stored in the Redis cache.

[0186] The determining submodule is configured to determine a target data structure corresponding to the fourth dependency data if the Redis cache does not store the expired dependency data.

[0187] The storing submodule is configured to store the fourth dependency data into the Redis cache based on the target data structure.

[0188] The replacing submodule is configured to perform data replacement processing on the expired dependency data using the fourth dependency data if the Redis cache stores the expired dependency data.

[0189] In some optional implementations of the embodiment, the first verifying module 303 includes:

[0190] The calling submodule is configured to call the permission level model and obtain a preset business operation permission table.

[0191] The obtaining submodule is configured to obtain a target permission level corresponding to the user information based on the permission level model.

[0192] The querying submodule is configured to query a specified permission level range corresponding to a business operation started by the local item from the business operation permission table.

[0193] The second judging submodule is configured to judge whether the target permission level is in the specified permission level range.

[0194] The second determining submodule is configured to determine that the user passes the permission verification if yes, and otherwise, determine that the user does not pass the permission verification.

[0195] In some optional implementations of the embodiment, the item starting apparatus further includes:

[0196] The third obtaining module is configured to obtain the first dependency data from the local cache if the local cache stores the first dependency data.

[0197] The third starting module is configured to start the target item based on the first dependency data.

[0198] To solve the above technical problems, the embodiments of the present application further provide a computer device. For details, please refer to Figure 4 , Figure 4 The basic structure block diagram of the computer device is shown in FIG. 4.

[0199] The computer device 4 comprises a memory 41, a processor 42 and a network interface 43 which are connected to each other through a system bus. It should be noted that only the computer device 4 with components 41-43 is shown in the figure, but it should be understood that it is not required to implement all the shown components, and more or less components can be alternatively implemented. Among them, those skilled in the art can understand that the computer device herein is a device capable of automatically performing numerical calculation and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0200] The computer device can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing devices. The computer device can interact with the user through a keyboard, a mouse, a remote controller, a touchpad or a voice control device.

[0201] The memory 41 includes at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or a memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 4. Of course, the memory 41 can also include both an internal storage unit and an external storage device of the computer device 4. In this embodiment, the memory 41 is generally used to store an operating system and various application software installed on the computer device 4, such as computer readable instructions of the project starting method, etc. In addition, the memory 41 can also be used to temporarily store various data that have been output or will be output.

[0202] The processor 42 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run computer readable instructions or process data stored in the memory 41, such as computer readable instructions of the project starting method.

[0203] The network interface 43 can include a wireless network interface or a wired network interface, and is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0204] The present application also provides another embodiment, i.e., to provide a computer readable storage medium storing computer readable instructions, which can be executed by at least one processor to make the at least one processor perform the steps of the project starting method as described above.

[0205] Those skilled in the art can clearly understand the above-mentioned embodiment method can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes a plurality of instructions for making a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method described in each embodiment of the present application.

[0206] Obviously, the above-described embodiments are only some of the embodiments of the present application, not all the embodiments, and the drawings show the preferred embodiments of the present application, but do not limit the patent scope of the present application. The present application can be implemented in many different forms, and conversely, the purpose of providing these embodiments is to make the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions recorded in the foregoing specific embodiments, or make equivalent replacements to some of the technical features. Any equivalent structure made by using the content of the specification and drawings, directly or indirectly applied to other related technical fields, is also within the scope of the patent protection of the present application.

Claims

1. A project initiation method characterized by, The method comprises the following steps: determining whether a user triggers a start request for a target project; wherein the start request carries user information of the user; if yes, extracting the user information from the start request, and performing permission verification on the user based on the user information and a preset permission level model; if the user passes the permission verification, determining whether the first dependency relationship data of a specified version corresponding to the target project is stored in a preset local cache; if the first dependency relationship data is not stored in the local cache, determining whether the second dependency relationship data of a specified version corresponding to the target project is stored in a preset Redis cache; if the second dependency relationship data is not stored in the Redis cache, determining whether the third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service; if the third dependency relationship data is stored in the remote service, obtaining the third dependency relationship data from the remote service; performing start processing on the target project based on the third dependency relationship data; wherein, after the step of determining whether the third dependency relationship data of a specified version corresponding to the target project is stored in a preset remote service, the method further comprises: if the third dependency relationship data is not stored in the remote service, obtaining the dependency relationship loading code corresponding to the target project; executing the dependency relationship loading code to load the fourth dependency relationship data corresponding to the specified version from a preset data source; performing data verification on the fourth dependency relationship data; if the fourth dependency relationship data passes the data verification, performing start processing on the target project based on the fourth dependency relationship data; wherein, after the step of performing start processing on the target project based on the fourth dependency relationship data, the method further comprises: performing format packaging processing on the fourth dependency relationship data to obtain target dependency relationship data; pushing the target dependency relationship data to the remote service; performing first cache update processing on the Redis cache based on the fourth dependency relationship data, and setting a first cache expiration time corresponding to the fourth dependency relationship data in the Redis cache; performing second cache update processing on the local cache based on the fourth dependency relationship data, and setting a second cache expiration time corresponding to the fourth dependency relationship data in the local cache; wherein, the dependency relationship data refers to the interest package dependency relationship corresponding to the target project, and the specified version refers to the latest version.

2. The project initiation method of claim 1, wherein, The step of performing data verification on the fourth dependency relationship data comprises: performing integrity verification on the fourth dependency relationship data; if the fourth dependency relationship data passes the integrity verification, performing consistency verification on the fourth dependency relationship data; if the fourth dependency relationship data passes the consistency verification, it is determined that the fourth dependency relationship data passes the data verification, otherwise it is determined that the fourth dependency relationship data does not pass the data verification.

3. The project initiation method of claim 1, wherein, The first cache updating processing of the Redis cache based on the fourth dependency relationship data specifically comprises the following steps. It is judged whether the expired dependency relationship data corresponding to the target project is stored in the Redis cache. If the expired dependency relationship data is not stored in the Redis cache, a target data structure corresponding to the fourth dependency relationship data is determined. The fourth dependency relationship data is stored in the Redis cache based on the target data structure. If the expired dependency relationship data is stored in the Redis cache, data replacement processing is performed on the expired dependency relationship data using the fourth dependency relationship data.

4. The project initiation method of claim 1, wherein, The step of performing permission verification on the user based on the user information and a preset permission level model specifically comprises the following steps. The permission level model is called, and a preset business operation permission table is obtained. A target permission level corresponding to the user information is obtained based on the permission level model. A specified permission level range corresponding to the business operation started by the local project is queried from the business operation permission table. It is judged whether the target permission level is within the specified permission level range. If yes, it is determined that the user passes the permission verification, otherwise it is determined that the user fails the permission verification.

5. The project initiation method of claim 1, wherein, After the step of judging whether the first dependency relationship data of the specified version corresponding to the target project is stored in the preset local cache, the following steps are further included. If the first dependency relationship data is stored in the local cache, the first dependency relationship data is obtained from the local cache. The target project is started based on the first dependency relationship data.

6. A project initiation apparatus, comprising: It includes: The first judgment module is used to judge whether the user triggered starting request for the target project is received; wherein the starting request carries the user information of the user; The first verification module is used to extract the user information from the starting request if yes, and to perform permission verification on the user based on the user information and a preset permission level model; The second judgment module is used to judge whether the first dependency relationship data of the specified version corresponding to the target project is stored in the preset local cache if the user passes the permission verification; The third judgment module is used to judge whether the second dependency relationship data of the specified version corresponding to the target project is stored in the preset Redis cache if the local cache does not store the first dependency relationship data; The fourth judgment module is used to judge whether the third dependency relationship data of the specified version corresponding to the target project is stored in the preset remote service if the Redis cache does not store the second dependency relationship data; The first acquisition module is used to obtain the third dependency relationship data from the remote service if the remote service stores the third dependency relationship data; The first starting module is used to start the target project based on the third dependency relationship data; The project starting device further includes: The second obtaining module is configured to obtain dependency loading code corresponding to the target project if the third dependency data is not stored in the remote service. The loading module is configured to execute the dependency loading code to load fourth dependency data corresponding to the specified version from a preset data source. The second verifying module is configured to perform data verification on the fourth dependency data. The second starting module is configured to perform starting processing on the target project based on the fourth dependency data if the fourth dependency data passes the data verification. The project starting apparatus further includes: The packaging module is configured to perform format packaging processing on the fourth dependency data to obtain target dependency data. The pushing module is configured to push the target dependency data to the remote service. The first updating module is configured to perform first cache updating processing on the Redis cache based on the fourth dependency data, and set a first cache expiration time corresponding to the fourth dependency data in the Redis cache. The second updating module is configured to perform second cache updating processing on the local cache based on the fourth dependency data, and set a second cache expiration time corresponding to the fourth dependency data in the local cache. The dependency data refers to the interest package dependency relationship corresponding to the target project, and the specified version refers to the latest version.

7. A computer device comprising a memory and a processor, wherein the memory stores computer readable instructions, and the processor implements the steps of the project starting method according to any one of claims 1 to 5 when executing the computer readable instructions.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer readable instructions, and the computer readable instructions implement the steps of the project starting method according to any one of claims 1 to 5 when executed by the processor.

Images