CN110944048B - Service logic configuration method and device - Google Patents

Abstract

The application discloses a service logic configuration method and device, and relates to the technical field of internet. In the application, a user can select a plurality of target function nodes from a plurality of displayed function nodes. The server can obtain attribute configuration information of the target function node selected by the user and the sequence of the plurality of target function nodes, and further generates a service logic configuration file. Therefore, according to the technical scheme provided by the application, developers do not need to inquire an interface protocol, call codes do not need to be compiled according to the interface protocol to call the paas interface, and business logic codes do not need to be compiled according to information returned by the paas interface, so that the complexity of business logic configuration is reduced, and the development efficiency is improved.

Description

Service logic configuration method and device

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for configuring service logic.

Background

Currently, to enhance the user experience and increase the user's viscosity, application providers may set various activities in applications. For example, the application facilitator may set the lottery activity in the application. In this case, the developer needs to configure the business logic for implementing the lottery activity in the server.

In the related art, a developer may write a calling code to call a paas (platform as a service) interface to obtain resource information for constructing a service logic, and then write a code of the service logic according to the obtained resource information to obtain a service logic configuration file. Because different paas interfaces may need to be called to obtain different resource information, and the different paas interfaces correspond to different interface protocols, when calling a paas interface, a developer needs to query an interface parameter document to obtain an interface protocol of a to-be-called pass interface, and then writes a calling code according to the obtained interface protocol.

Therefore, in the related art, a developer needs to write codes to perform business logic configuration, and the efficiency is low. Moreover, since the developer needs to obtain the interface protocol by looking up the interface parameter document, and the interface parameter document is not easy to read, the difficulty in obtaining the interface protocol is high, and the development efficiency is further reduced.

Disclosure of Invention

The embodiment of the application provides a service logic configuration method, a service logic configuration device and a storage medium, which can be used for solving the problem of low service logic configuration efficiency in the related art. The technical scheme is as follows:

in one aspect, a method for configuring service logic is provided, where the method includes:

receiving a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes, each function node in the plurality of function nodes being an operation set for implementing a function;

acquiring the sequence of the target function nodes and acquiring the attribute configuration information of each target function node in the target function nodes;

and generating a service logic configuration file according to the target function nodes, the attribute configuration information of each target function node and the sequence of the target function nodes.

In another aspect, an apparatus for configuring service logic is provided, the apparatus including:

a receiving module, configured to receive a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes, where each function node in the plurality of function nodes is an operation set for implementing a function;

the acquisition module is used for acquiring attribute configuration information of each target function node in the target function nodes and acquiring the sequence of the target function nodes;

and the generating module is used for generating a service logic configuration file according to the target function nodes, the attribute configuration information of each target function node and the sequence of the target function nodes.

In another aspect, a service logic configuration apparatus is provided, the apparatus includes a processor and a memory, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the instruction, the program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the service logic configuration method.

In another aspect, a computer-readable storage medium is provided, in which a computer program is stored, which, when being executed by a processor, implements the steps of the service logic configuration method provided in the foregoing.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:

in the embodiment of the application, a user can select a plurality of target function nodes from a plurality of displayed function nodes. The server can obtain attribute configuration information of the target function node selected by the user and the sequence of the plurality of target function nodes, and further generates a service logic configuration file. Therefore, according to the technical scheme provided by the application, developers do not need to inquire an interface protocol, call codes do not need to be compiled according to the interface protocol to call the paas interface, and business logic codes do not need to be compiled according to information returned by the paas interface, so that the complexity of business logic configuration is reduced, and the development efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic illustration of an interface for a marketing campaign according to an embodiment of the present application;

fig. 2 is a flowchart of a service logic configuration method according to an embodiment of the present application;

FIG. 3 is a diagram of a configuration function interface provided by an embodiment of the present application;

FIG. 4 is a node variable reference relationship diagram provided in an embodiment of the present application;

FIG. 5 is a diagram of a test window displayed in a third functional area according to an embodiment of the present disclosure;

FIG. 6 is a schematic view of a flow control setting interface of business logic of a task redemption activity provided by an embodiment of the present application;

FIG. 7 is a flow chart of another business logic configuration provided by embodiments of the present application;

FIG. 8 is a flow chart illustrating implementation of business logic according to a business logic configuration file according to an embodiment of the present application;

FIG. 9 is a block diagram of a process for executing business logic according to an embodiment of the present disclosure;

fig. 10 is a block diagram illustrating a service logic configuration apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a server for performing service logic configuration according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Before explaining the embodiments of the present application in detail, an application scenario related to the embodiments of the present application will be described.

Currently, the variety of applications is increasing. To increase user stickiness, the application facilitator may set various marketing campaigns in the application to increase the frequency with which the user uses the application. For example, in some multimedia applications, a lottery activity may be set. Under the condition that the user account number meets a certain condition, the user can extract the prize.

As another example, as shown in FIG. 1, in some gaming applications, a mission draw activity may be set. That is, after a player completes a certain mission, the level of the completed mission receives a certain number of prizes corresponding to the mission, or performs a certain number of prize receiving operations. For example, if the player completed a mission that was a first level mission in the silver road, prize 1 may be awarded. Prize 2 may be awarded if the completed task is a first level task in the story road.

The business logic configuration method provided by the embodiment of the application can be used for business logic configuration of activities in the scene, so as to ensure normal implementation of the marketing activities. It should be noted that the foregoing is only two possible scenarios shown in the embodiment of the present application, and does not constitute a limitation on an application scenario of the service logic configuration method provided in the embodiment of the present application.

Next, a service logic configuration method provided in the embodiment of the present application is introduced.

Fig. 2 is a flowchart of a service logic configuration method according to an embodiment of the present application. The method can be applied to a configuration end, and the configuration end can be equipment which is integrated in a service node and can be used for interacting with a developer. Referring to fig. 2, the method comprises the steps of:

step 201: a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes is received, each function node of the plurality of function nodes being an operation set for implementing a function.

In the embodiment of the application, a configuration function interface can be displayed on the configuration end. A plurality of function node options can be displayed in the configuration function interface. Each function node option is used to identify a function node. Wherein each functional node is a set of operations for implementing a function. It should be noted that the plurality of functional nodes can be divided into four categories, namely logic nodes, judgment nodes, variable nodes and output nodes. The logical nodes may include data processing nodes such as array operation nodes, database nodes, and the like. The judgment nodes may include conditional judgment nodes, and the variable nodes may include, for example, parameter check nodes, variable nodes, and the like. The output node may be a node for outputting data.

The user can select a target function node option corresponding to a target function node required to be used for realizing the service logic from the plurality of function node options. The configuration end can receive a selection instruction triggered when a user selects a target function node option, and determines and acquires the target function node selected by the user according to the selection instruction. The user here refers to a developer configuring the business logic.

In addition, because multiple functional nodes are usually needed to implement the service logic, a user may sequentially select multiple target functional nodes according to the functions that can be implemented by each functional node and the logic of the service to be configured. That is, the user may trigger a selection instruction for selecting one target function node each time, and the configuration end may record a selection sequence in which the user sequentially selects a plurality of target function nodes.

In one possible implementation, the configuration function interface may include a first function area, a second function area, and a third function area. And a plurality of function node options can be displayed in the first function area. The second functional area is a service logic configuration area, and the third functional area is an attribute configuration area. In this case, the user may trigger a selection instruction for the target function node by dragging the target function node option to the second function area. That is, the user may sequentially perform a dragging operation on each target function node option displayed in the first function area, which is required for implementing the service logic, according to the logic of the service and the function that can be implemented by the function node, and drag the target function node option to the second function area, so as to implement selection of the target function node identified by the plurality of target function node options. The configuration end can obtain corresponding target function nodes according to the target function node options selected by the user, and meanwhile, the target function node options corresponding to the target function nodes selected by the user can be displayed in the second function area.

In another possible implementation manner, multiple function node options may be directly displayed in the configuration function interface, and a user may trigger a selection instruction for a function node identified by each function node option by sequentially clicking a selection mode. In this case, a completion option may also be displayed in the configuration function interface. After the user selects a plurality of target function nodes in sequence, the completion option can be clicked, thereby ending the selection of the target function nodes. The configuration end can obtain a plurality of target function nodes selected by a user, and meanwhile, the configuration end can cancel displaying function node options in the configuration function interface and jump to display the target function node options corresponding to the plurality of target function nodes selected by the user.

Optionally, the user may select each target function node according to no logic of the service. In this case, if three function areas are displayed in the configuration function interface, the user may click a plurality of target function node options in the first function area, and then drag the clicked target function node options into the second function area. Alternatively, the user may click on the confirm option after clicking on multiple target function node options to trigger a pick end instruction. After detecting the selection ending instruction, the configuration end may obtain a plurality of corresponding target function nodes according to the plurality of target function node options clicked by the user, and display the plurality of target function node options clicked by the user in the second function area. If a plurality of function node options are initially and directly displayed in the configuration function interface and the second function area does not exist, the user may not click a plurality of target function node options according to the logic of the service. After the user selects a plurality of target function nodes in sequence, the completion option can be clicked, thereby ending the selection of the target function nodes. And then, the configuration end can acquire a plurality of target function nodes selected by the user, cancel the display of the function node options in the configuration function interface, and jump to display the target function node options corresponding to the plurality of target function nodes selected by the user.

Step 202: the method comprises the steps of obtaining the sequence of a plurality of target function nodes and obtaining attribute configuration information of each target function node in the plurality of target function nodes.

As shown in step 201, in an implementation manner, a user may sequentially select a plurality of target function nodes according to the service logic and the functions that can be implemented by each function node. In this case, the configuration end may use the selection order of each target function node selected by the user as the sequence of each target function node, and then sequentially display each target function node option in the second function area or the skipped service logic configuration page according to the sequence of each target function node, and sequentially connect each function node option according to the sequence of each function node.

In another implementation, the user may select a plurality of target function nodes according to the service logic and the functions that can be realized by the function nodes. In this case, after the plurality of target function node options are displayed in the second function area or the service logic configuration interface, the user may adjust the display position of each target function node option according to the service logic and configure the connection line between each target function node option, so as to implement the configuration of the sequence of each target function node. The configuration end can determine the sequence of each target function node according to the connecting line between each function node option and/or the display position of each function node option.

After the multiple target function node options are displayed according to the sequence, the configuration end can receive a configuration instruction for configuring a first function node, wherein the first function node is any one of the multiple target function nodes; displaying a configuration option corresponding to the first functional node according to the configuration instruction; and acquiring attribute configuration information input in a configuration option corresponding to the first functional node, and taking the acquired attribute configuration information as the attribute configuration information of the first functional node.

The attribute configuration information of the functional node may include input parameters, transaction flags, and the like of the corresponding functional node. The input parameter may be a fixed value input by a user, or may be an output result of other functional nodes. The transaction flag may be used to indicate whether the corresponding functional node is in a transaction. A transaction is a program execution unit that contains a series of operations. In the embodiment of the present application, a part of operations included in one functional node may constitute one transaction, or a plurality of functional nodes may also constitute one transaction. The transaction marker may include a transaction start (begin transaction) and a transaction end (end transaction).

In an implementation manner, if the configuration function interface includes the third function area, after the plurality of target function node options are displayed in the second function area according to the sequence, taking any one function node in the plurality of target function node options as an example, the function node is referred to as a first function node, and a user may perform a selection operation for the first function node option corresponding to the first function node to trigger a configuration instruction for configuring the first function node. After the configuration end receives a configuration instruction for configuring the first function node, one or more configuration options corresponding to the first function node may be displayed in the third function area, and the user may input attribute configuration information in the one or more configuration options. The configuration end can acquire attribute configuration information input by a user as attribute configuration information of the first function node.

For each target function node in the plurality of target function nodes, the configuration end can obtain the attribute configuration information configured for the corresponding target function node by the user by referring to the above manner. Wherein, according to different functions realized by the functional nodes, the attribute configuration information of each functional node may be different. Alternatively, for some functional nodes, configuration attribute configuration information may not be needed. Or, some functional nodes may have default attribute configuration information, and for such functional nodes, the configuration end may directly obtain the default attribute configuration information.

Fig. 3 is a configuration function interface diagram according to an embodiment of the present application. As shown in fig. 3, the left area of the configuration function interface is a first function area, the middle area is a second function area, and the right area is a third function area. Wherein, a plurality of function node options are displayed in the first function area. The plurality of functional node options may be classified into a logic control class, a basic class, a data processing class, an external platform class, a qualification control class, a Service class, and a FaaS (functional as a Service) extension class according to implementation functions. The logic control class includes a condition judgment node option for realizing condition judgment. The base class includes a parameter check node option, an output data node option, a string node option, and a variable node option. And the parameter check node is used for realizing parameter check. The output data node is used for outputting data, the character string node is used for processing character strings, and the variable node is used for defining variables and assigning values to the variables. The data processing class includes an array operation node option, a mapping value correspondence node option, a DB (database) node option, and a Remote Dictionary service (Remote Dictionary Server) node option. The external platform class includes an IDIP node option for acquiring application data from an IDIP server and an HTTP (Hyper Text Transfer Protocol) node option for acquiring application data from an HTTP server. The qualification control classes include a check qualification node option, a deduct qualification node option, an add qualification node option, and a credit node option. The service class includes a lottery delivery node option. The FaaS extension class includes a PHP (Hypertext Preprocessor) node option and a JS/LUA node option. The user can drag to the second functional area by selecting the functional node option required for realizing the service logic from the first functional area. Each target function node selected by the user is displayed in the second function area, and as shown in fig. 3, the target function nodes are sequentially arranged according to the sequence, and each function node is connected with the previous function node and the next function node through a connecting line. When the user performs a selection operation with respect to the function node 3 (black frame in fig. 3) displayed in the second function area, a configuration instruction for configuring the function node is triggered. After receiving the configuration instruction, the configuration end may display the configuration option corresponding to the function node in the third function area. As shown in fig. 3, the configuration options corresponding to the function node may include four configuration options of name, account, total qualification, and resource. The name can be a default name, the user can modify the name, and the user can input corresponding attribute configuration information in three configuration options of the account number, the total qualification and the resource. The configuration end may use the four attribute configuration information as the attribute configuration information of the third functional node.

Step 203: and generating a service logic configuration file according to the target function nodes, the attribute configuration information of each target function node and the sequence of the target function nodes.

After obtaining the plurality of target function nodes, the attribute configuration information of each target function node and the sequence of the plurality of target function nodes, the configuration end can verify the attribute configuration information of each target function node in the plurality of target function nodes, wherein the attribute configuration information comprises input parameters and/or transaction marks of the corresponding function nodes; if the attribute configuration information of each target function node passes the verification, generating a node variable reference relation graph according to the attribute configuration information of each target function node and the sequence of the plurality of target function nodes, wherein the node variable reference relation graph is used for indicating the dependency relation among the target function nodes; and generating a service logic configuration file according to the node variable reference relation graph, the plurality of target function nodes and the attribute configuration information of the plurality of target function nodes.

The configuration end can check whether each configuration option corresponding to each target function node corresponds to attribute configuration information, that is, whether attribute configuration information missed by a user exists is checked. In addition, the configuration end can also check whether the parameter of each target function node has errors or not, and whether the attribute configuration information in the plurality of target function nodes comprises the transaction mark is correct or not. For example, if the attribute configuration information in a certain functional node includes a transaction start flag, but no transaction end flag exists in other functional nodes after the functional node, it may be determined that the transaction flag in the functional node is in error. In addition, the configuration end can also judge whether the current business logic has endless loop according to the sequence of the target function nodes.

If the check is passed, the configuration of each functional node is correct. Then, the configuration end can determine the parallel processing attribute of each target function node according to the attribute configuration information of each target function node and the sequence of the plurality of target function nodes, wherein the parallel processing attribute is used for indicating the possibility of parallel execution of the corresponding target function node and any function node in the rest target function nodes; and generating the node variable reference relation graph according to the sequence of the target function nodes and the parallel processing attribute of each target function node.

The configuration end may first determine a starting node, that is, a first functional node, from the plurality of target functional nodes according to the sequence of the plurality of target functional nodes. Then, starting from the first functional node, the configuration end may determine which functional nodes the outputs of the respective functional nodes may be inputs, so as to obtain the dependency relationship between the respective nodes, which may actually indicate the data transfer relationship between the respective nodes. After the data transfer relationship between the nodes is determined, the nodes on which the nodes need to execute can be determined. Thus, for a plurality of nodes which need to depend on the output of the same node for execution and have no dependency relationship with each other, the plurality of nodes can be executed in parallel. That is, the plurality of nodes may be marked with a parallel processing attribute indicating that the plurality of nodes execute in parallel. And for other nodes which can not be executed in parallel, the parallel processing attribute for indicating that the corresponding node can not be executed in parallel can be marked. After the parallel processing attribute of each node is determined, a node variable reference relation graph is generated according to the parallel processing attribute of each node and the sequence of each node configured by a user. In the node variable reference relationship graph, the output of the previous node in the two connected nodes is the input of the next node.

Fig. 4 is a node variable reference relationship diagram according to an embodiment of the present application. As shown in fig. 4, a solid line between nodes is used to indicate a data transfer relationship between nodes, that is, a dependency relationship of nodes, and a solid line is used to indicate a precedence relationship of nodes configured by a user. According to the solid line connection among the nodes, the output of the starting node is the input of the parameter check node, and the output of the parameter check node can be used as the input of the PHP node and the input of the result storage node at the same time. The output of the PHP node is the input of the condition judgment node, and two different output results of the condition judgment node can be respectively used as the input of two different branch function nodes. Finally, the outputs of the two branch function nodes may serve as inputs to the end node.

As can be seen from the comparison in fig. 4, the sequence of each target function node configured by the user is only one sequence configured according to the logic sequence of the service, and it is not considered which target function nodes in the plurality of target function nodes can be processed in parallel. The configuration end can determine the data transfer relationship among the nodes according to the attribute configuration information of each node, and further determine which nodes in each node can be processed in parallel, that is, the node variable reference relationship graph can indicate not only the dependency relationship among the nodes, but also the logic sequence of the target function nodes when the service logic is implemented. The logical sequence of the target function nodes is actually the real execution sequence of the target function nodes, and the sequence of the target function nodes determined according to the user configuration is actually the possible sequence of each node which is not optimized.

Optionally, in some possible cases, when there is a node corresponding to the transaction flag in the target function nodes, the configuration side may further verify whether the nodes may constitute a transaction to execute.

After the node variable reference relationship graph is obtained, the configuration end can generate a service logic configuration file according to the node variable reference relationship graph, the target function nodes and the attribute configuration information of the target function nodes. The configuration end may generate a description of a specific function method required for execution according to the dependency relationship between the nodes indicated in the node variable reference relationship diagram, the target function nodes, and the attribute configuration information of the target function nodes, and generate an instruction code for implementing the service logic. And then, the configuration end can generate a service configuration file according to the instruction code.

It should be noted that, in the service logic, the implementation of some function nodes may require calling external platform data or accessing an external database. Therefore, when the service configuration file is generated, resource information required for realizing the service logic can be obtained, and the resource information comprises information such as a database and the like possibly used in the service logic realization process. The configuration end can generate a service configuration file according to the resource information and the instruction code. At this time, the service profile includes the instruction code and the resource information.

Optionally, in some possible scenarios, for example, some marketing campaigns may require limited time periods or durations, or limited users participating in the campaign, that is, the business logic corresponds to basic usage information such as valid usage periods and valid user groups. In this case, the configuration end may further obtain the basic usage information, and further generate a service configuration file according to the basic usage information and the instruction code. At this time, the service profile includes the instruction code and the basic usage information.

Optionally, the configuration end may also obtain the resource information and the basic usage information at the same time, and generate the service configuration file according to the resource information, the basic usage information, and the instruction code.

After the service logic configuration file is generated by the method, the user can also test the service logic. Taking the configuration function interface including three function areas as an example, the test window may be displayed in the third function area. The test window can display test parameter configuration items, and a user can input test parameter values in the test parameter configuration items and click a test button to trigger a test instruction. The configuration end can acquire the test parameter value input by the user after detecting the test instruction, and analyze the service logic configuration file. And executing the service logic according to the test parameter value input by the user, and displaying the test result in the test result window. It should be noted that, in the process that the configuration end executes the service logic according to the test parameter value, in the second functional area, the configuration end may further display an execution sequence of the plurality of target function nodes in a line connection manner.

Fig. 5 is a schematic diagram illustrating a test window displayed in a third functional area according to an embodiment of the present application. As shown in fig. 5, a user may configure test parameter values in test parameter configuration item 510. The user can select a test case through the configuration items in the test case selection window 530, and the test case is used as a test parameter value. The user may then click on test option 520 in fig. 5 to trigger the test instruction. After receiving the test instruction, the configuration end can obtain a test parameter value and test the service logic. Thereafter, the test results are displayed in a test results window 540.

Optionally, in this embodiment of the present application, after the business logic configuration file is generated, the configuration end may issue a service according to the business logic configuration file. The configuration end may provide a service by using the service logic configuration file as a service option of the current service node, or may provide an http service to the outside as a gateway, or may directly generate an html (Hyper Text Markup Language) page and send the html page to the management end, thereby becoming a management end page tool.

Optionally, when the configuration end issues the service according to the service logic configuration file, the configuration end may further perform flow control setting, account verification, and the like to ensure security.

Fig. 6 is a schematic view of a flow control setting interface of business logic of a task redemption activity provided in an embodiment of the present application. As shown in fig. 6, the user may enter a total flow threshold in the total flow limit configuration item. The redemption activity frequency is entered in the redemption activity profile. Outputting the frequency of generating the redemption results in the redemption result configuration items. In addition, after the activity configuration items are redeemed, options for switching whether account verification login is needed or not can be correspondingly displayed, so that whether account verification is needed or not for corresponding configuration is indicated.

For the business logic configuration method described above, the process shown in fig. 7 may be summarized, and the process may include configuration, compilation, and business logic configuration file generation. Wherein the configuration comprises configuration description, graphic position and attribute filling. The configuration description and the graph position refer to the process of acquiring the plurality of target function nodes and the sequence of the plurality of target function nodes according to the user configuration. The attribute filling refers to a process of acquiring attribute configuration information of each functional node. After configuration is finished, compiling can be carried out, and the compiling process comprises exception troubleshooting and performance optimization. The exception checking refers to the process of checking the attribute configuration information introduced above, and the performance optimization refers to the process of determining the parallel processing attributes of each target function node. After the compilation is finished, the configuration end can generate a service logic configuration file, and the service logic configuration file can comprise basic use information, resource information and instruction codes.

In the embodiment of the application, a user can select a plurality of target function nodes from a plurality of displayed function nodes. The server can acquire attribute configuration information of the target function node selected by the user and the sequence of the plurality of target function nodes, and further generates a service logic configuration file. Therefore, according to the technical scheme provided by the application, developers do not need to inquire an interface protocol, call codes do not need to be compiled according to the interface protocol to call the paas interface, and business logic codes do not need to be compiled according to information returned by the paas interface, so that the complexity of business logic configuration is reduced, and the development efficiency is improved. In addition, because the user can select the functional node to be used from the plurality of functional nodes, different functional nodes can be selected for different service logics, that is, the plurality of functional nodes can realize high-degree multiplexing.

After generating the service logic configuration file, the configuration end may store the service configuration logic file in correspondence with the target service activity identifier. So that the client of the active user who subsequently participates in the activity can call the business logic configuration file to execute the corresponding business logic when participating in the activity.

Fig. 8 is a flowchart for invoking the generated service logic configuration file to implement service logic according to an embodiment of the present application. If the configuration end generates the service logic configuration file, and then uses the service logic configuration file as a service of the current service node, or the configuration end serves as a gateway to provide an http service to the outside, the method may be applied to the configuration end. Alternatively, if the configuration end configures the service logic configuration file into other service nodes, the method may be performed by other service nodes. For convenience of description, the current service node or other service nodes integrated with the configuration end are collectively referred to as service nodes, and the following process for implementing the service logic is described with this as an execution subject. Referring to fig. 8, the method includes the steps of:

step 801: and receiving a service request carrying a target service activity identifier, wherein the service request also carries a service parameter value.

The service node may receive a service request sent by a client corresponding to any user participating in an activity, where the service request carries a service parameter value and a target service activity identifier. Wherein the target business activity identifier can be used to uniquely identify a business activity. The service parameter value is a service parameter value required for realizing the service activity according to the service logic.

For example, assuming that the current business activity is a task redemption activity, the business parameter values may include user information, task level, task execution result, and other business parameter values. The user information may include a user identifier, a user rating, and the like of the user. Here, the user information refers to user information of a user participating in an activity.

According to different business activities, business parameter values are different, and the business parameter values are not limited in the embodiment of the application. After the service parameter value is obtained, the service node may also check the service parameter value.

Step 802: and acquiring a service logic configuration file according to the target service activity identifier.

After receiving the service request, the service node may obtain a target service activity identifier carried in the service request, and obtain a service logic configuration file according to the target service activity identifier.

The service node may store a mapping relationship between the service activity identifier and the logic configuration file, and based on this, the service node may obtain the service logic configuration file corresponding to the target service activity identifier from the mapping relationship.

Optionally, a mapping relationship between the service activity identifier and a storage path of the logic configuration file may be stored in the service node, and a file name of the service logic configuration file of each service activity may be the service activity identifier of the corresponding service activity. Based on this, the service node may obtain a storage path corresponding to the target service activity identifier from the mapping relationship, and obtain a service logic configuration file with a file name as the target service activity identifier according to the storage path.

Step 803: and sequentially executing part or all of the functional nodes in the plurality of target functional nodes according to the service logic configuration file and the service parameter value.

After the service logic configuration file is obtained, the service node can analyze the service logic configuration file to obtain attribute configuration information of each target function node in a plurality of target function nodes and a dependency relationship among the target function nodes; and sequentially executing part or all of the plurality of target function nodes according to the dependency relationship among the target function nodes, the attribute configuration information and the service parameter value of each target function node.

As can be known from the foregoing process of generating the service logic configuration file, the instruction code in the service logic configuration file is generated according to the functional nodes, the attribute configuration information of the functional nodes, and the dependency relationships between the nodes represented by the node variable reference relationship graph. Based on this, the service node may parse the service configuration logic file, thereby determining attribute configuration information of each target function node of the plurality of target function nodes and a dependency relationship between the nodes. It should be noted that the instruction codes in the service logic configuration file are determined according to the dependency relationships between the function nodes, and therefore, the execution sequence of the instruction codes in the service logic configuration file may indicate the dependency relationships between the function nodes.

For convenience of description, any one of the plurality of target function nodes is referred to as a second function node. And if the second function node is the first function node in the target function nodes, determining the input parameter value of the second function node according to the attribute configuration information and the service parameter value of the second function node. If the second function node is not the first function node in the target function nodes, determining an input parameter value of the second function node according to the attribute configuration information of the second function node and the execution result of the previous function node of the second function node; executing the second function node according to the attribute configuration information and the input parameter value of the second function node; and if the functional node behind the second functional node is determined to be two parallel branch functional nodes according to the dependency relationship between the target functional nodes, selecting one functional node from the two parallel branch functional nodes according to the execution result of the second functional node, taking the selected functional node as the second functional node, returning to the step of determining the input parameter value of the second functional node according to the attribute configuration information of the second functional node and the execution result of the previous functional node of the second functional node until no functional node exists behind the second functional node.

It should be noted that the service node may first execute the first function node. The input parameters included in the attribute configuration information of the functional node may include input variables. Where the input variable may be a system variable, such as time. In this case, the service node may obtain parameter values of system variables and assign values to these input variables. For the first functional node, the input variables further include a business scalar, and the service node may assign values to the business variables according to the business parameter values. Therefore, the service node may use the obtained parameter value of the system variable and the service parameter value as an input parameter value of the first function node, and execute the first function node according to the input parameter value.

It should be noted that, in general, each input parameter and the corresponding input parameter value are organized by a certain rule, and therefore, the service node may analyze each input parameter and the corresponding output parameter value according to a built-in dynamic expression rule, thereby executing the function node.

For other functional nodes after the first functional node, the input variables of the functional node may include system variables and may also include business variables, and at the same time, the input variables of the functional node also include the output of the pre-functional node. Based on this, the service node may obtain an input parameter value according to an input variable included in the attribute configuration information of the function node, and then execute the function node according to the obtained input parameter value.

After the functional node is executed to obtain the execution result, according to the logical order of the target functional nodes, if it can be determined that the functional node after the functional node is two parallel branch functional nodes, the functional node to be executed next can be determined according to the execution result of the functional node. Here, the two parallel branch function nodes mean that the inputs of the two function nodes are both the outputs of the function node, but correspond to different outputs of the function node. For example, for a functional node of the condition judgment class, two parallel branch functional nodes exist after the functional node, wherein the service node may select different branch functional nodes to execute according to different execution results output by the functional node.

After determining the next function node to be executed, the service node may refer to the foregoing method to obtain the input parameter value of the function node, and then execute the corresponding function node until the last node is executed.

Optionally, when executing a functional node, if the functional node fails to execute and the functional node is a functional node in a transaction, the service node may further execute a transaction rollback operation.

Optionally, if a plurality of functional nodes apply to the parallel processing attribute indicating that they can execute in parallel, the service node may also execute in parallel on the plurality of functional nodes by starting the coroutine, so as to improve the execution performance.

Optionally, fig. 9 is a flowchart of a service logic execution provided in this embodiment. As shown in fig. 9, after the service logic configuration file and the service parameter value are obtained, initialization may be performed, and parameter verification may be performed on the service parameter value. Then, the service node may parse the service logic configuration file to obtain attribute configuration information of the first function node, perform parameter preprocessing according to the attribute configuration information of the first function node to obtain an input parameter value of the first function node, and execute the first function node. And performing transaction processing on the functional node, namely when the functional node is a node in a certain transaction, if the functional node fails to execute, rolling back the current transaction, otherwise, determining the functional node to be executed next according to the functional node. And after determining the next function node to be executed, returning to the process of obtaining the attribute configuration information of the next function node to be executed by performing configuration analysis according to the service logic configuration file. When each functional node is executed, whether the execution result of the functional node is cached or not can be judged, if the execution result is cached, the cache system is cached, and if the execution result is not cached, the cache system can be output to other databases to perform other calculations. And outputting the final execution result through the output node until the last node is executed, thereby finishing the service logic.

It should be noted that, in the example of fig. 9, the service node parses the attribute configuration information of the function node to be executed one by one according to the service logic configuration file. Optionally, in another possible implementation manner, as described above, the service node may also directly obtain the attribute configuration information of all the functional nodes by parsing according to the dependency relationship between the nodes. Later, when the node is executed, the parameter preprocessing can be directly carried out on the attribute configuration information. That is, the configuration analysis in fig. 9 may also be the configuration analysis of all functional nodes, so that after determining the next functional node, the parameter preprocessing may be directly performed.

In the embodiment of the application, a developer can select a plurality of target function nodes from a plurality of displayed function nodes. The server can acquire attribute configuration information of the target function node selected by the developer and the sequence of the plurality of target function nodes, and further generate a service logic configuration file. Therefore, according to the technical scheme provided by the application, developers do not need to inquire an interface protocol, call codes do not need to be compiled according to the interface protocol to call the paas interface, and business logic codes do not need to be compiled according to information returned by the paas interface, so that the complexity of business logic configuration is reduced, and the development efficiency is improved. In addition, since the developer can select the functional node to be used from the plurality of functional nodes, different functional nodes can be selected for different service logics, that is, the plurality of functional nodes can realize high-degree multiplexing.

After generating the service logic configuration file, when a service request of a user participating in an activity is received subsequently, the service logic configuration file can be directly called to execute corresponding service logic so as to realize the service activity. Since the service logic configuration file is generated according to the target function node selected from a plurality of function nodes provided by a developer at the configuration end, the service logic configuration file is easier to analyze and execute by a computer.

Next, a service logic configuration apparatus provided in this embodiment of the present application is described.

Fig. 10 is a block diagram of a service logic configuration apparatus 1000 according to an embodiment of the present application. Referring to fig. 10, the apparatus 1000 includes:

a receiving module 1001, configured to receive a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes, where each function node in the plurality of function nodes is an operation set for implementing a function;

an obtaining module 1002, configured to obtain a sequence of a plurality of target function nodes and obtain attribute configuration information of each target function node in the plurality of target function nodes;

the generating module 1003 is configured to generate a service logic configuration file according to the multiple target function nodes, the attribute configuration information of each target function node, and the sequence of the multiple target function nodes.

Optionally, the obtaining module 1002 is specifically configured to:

receiving a configuration instruction for configuring a first functional node, wherein the first functional node is any one of a plurality of target functional nodes;

displaying a configuration option corresponding to the first functional node according to the configuration instruction;

and acquiring attribute configuration information input in a configuration option corresponding to the first functional node, and taking the acquired attribute configuration information as the attribute configuration information of the first functional node.

Optionally, a plurality of target function nodes are obtained by sequential selection; the obtaining module 1002 is specifically configured to:

and acquiring a selection sequence when the plurality of target function nodes are selected in sequence, and taking the selection sequence as the sequence of the plurality of target function nodes.

Optionally, the generating module 1003 includes:

the checking submodule is used for checking attribute configuration information of each target function node in the plurality of target function nodes, and the attribute configuration information comprises input parameters and/or transaction marks of the corresponding function nodes;

the first generation submodule is used for generating a node variable reference relation graph according to the attribute configuration information of each target function node and the sequence of the target function nodes if the attribute configuration information of each target function node passes the verification, and the node variable reference relation graph is used for indicating the dependency relation among the target function nodes;

and the second generation submodule is used for generating a service logic configuration file according to the node variable reference relation graph, the plurality of target function nodes and the attribute configuration information of the plurality of target function nodes.

Optionally, the first generation submodule is specifically configured to:

determining the parallel processing attribute of each target function node according to the attribute configuration information of each target function node and the sequence of the plurality of target function nodes, wherein the parallel processing attribute is used for indicating the possibility of parallel execution of the corresponding target function node and any one of the rest target function nodes;

and generating a node variable reference relation graph according to the sequence of the target function nodes and the parallel processing attribute of each target function node.

Optionally, the apparatus further comprises:

the storage module is used for correspondingly storing the service logic configuration file and the target service activity identifier;

the receiving module is used for receiving a service request carrying a target service activity identifier, and the service request also carries a service parameter value;

the acquisition module is used for acquiring a service logic configuration file according to the target service activity identifier;

and the execution module is used for sequentially executing part or all of the functional nodes in the target functional nodes according to the service logic configuration file and the service parameter value.

Optionally, the execution module is specifically configured to:

analyzing the service logic configuration file to obtain attribute configuration information of each target function node in a plurality of target function nodes and a dependency relationship among the target function nodes;

and sequentially executing part or all of the plurality of target function nodes according to the dependency relationship among the target function nodes, the attribute configuration information and the service parameter value of each target function node.

Optionally, the execution module is specifically configured to:

if the second function node is the first function node in the target function nodes, determining an input parameter value of the second function node according to the attribute configuration information and the service parameter value of the second function node;

if the second function node is not the first function node in the target function nodes, determining an input parameter value of the second function node according to the attribute configuration information of the second function node and the execution result of the previous function node of the second function node;

executing the second function node according to the attribute configuration information and the input parameter value of the second function node;

and if the functional node behind the second functional node is determined to be two parallel branch functional nodes according to the dependency relationship between the target functional nodes, selecting one functional node from the two parallel branch functional nodes according to the execution result of the second functional node, taking the selected functional node as the second functional node, returning to the execution result of the previous functional node of the second functional node according to the attribute configuration information of the second functional node, and determining the input parameter value of the second functional node until no functional node exists behind the second functional node.

In summary, in the embodiment of the present application, a developer may select a plurality of target function nodes from a plurality of displayed function nodes. The server can acquire attribute configuration information of the target function node selected by the developer and the sequence of the plurality of target function nodes, and further generate a service logic configuration file. Therefore, according to the technical scheme provided by the application, developers do not need to inquire an interface protocol, call codes do not need to be compiled according to the interface protocol to call the paas interface, and business logic codes do not need to be compiled according to information returned by the paas interface, so that the complexity of business logic configuration is reduced, and the development efficiency is improved. In addition, since the developer can select a functional node to be used from the plurality of functional nodes, different functional nodes can be selected for different service logics, that is, the plurality of functional nodes can realize high-degree multiplexing.

It should be noted that: in the service logic configuration apparatus provided in the foregoing embodiment, when configuring the service logic, only the division of each functional module is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the service logic configuration apparatus provided in the foregoing embodiment and the service logic configuration method embodiment belong to the same concept, and specific implementation processes thereof are described in the method embodiment and are not described herein again.

FIG. 11 is a schematic diagram illustrating a server architecture for business logic configuration in accordance with an illustrative embodiment. The functions of the service node in the embodiments shown in fig. 2-9 described above can be implemented by the server shown in fig. 11. The server may be a server in a cluster of background servers. Specifically, the method comprises the following steps:

the server 1100 includes a Central Processing Unit (CPU) 1101, a system Memory 1104 including a Random Access Memory (RAM) 1102 and a Read-Only Memory (ROM) 1103, and a system bus 1105 connecting the system Memory 1104 and the CPU 1101. The server 1100 also includes a basic Input/Output system (I/O system) 1106, which facilitates transfer of information between devices within the computer, and a mass storage device 1107 for storing an operating system 1113, application programs 1114, and other program modules 1115.

The basic input/output system 1106 includes a display 1108 for displaying information and an input device 1109 such as a mouse, keyboard, etc. for user input of information. Wherein the display 1108 and the input device 1109 are connected to the central processing unit 1101 through an input output controller 1110 connected to the system bus 1105. The basic input/output system 1106 may also include an input/output controller 1110 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 1110 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 1107 is connected to the central processing unit 1101 through a mass storage controller (not shown) that is connected to the system bus 1105. The mass storage device 1107 and its associated computer-readable media provide non-volatile storage for the server 1100. That is, the mass storage device 1107 may include a computer-readable medium (not shown) such as a hard disk or CD-ROM (Compact disk Read-Only Memory) drive.

Without loss of generality, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state Memory technology, CD-ROM, DVD (Digital Versatile disk), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 1104 and mass storage device 1107 described above may be collectively referred to as memory.

According to various embodiments of the application, the server 1100 may also operate as a remote computer connected to a network through a network, such as the Internet. That is, the server 1100 may connect to the network 1112 through the network interface unit 1111 that is coupled to the system bus 1105, or may connect to other types of networks or remote computer systems (not shown) using the network interface unit 1111.

The memory further includes one or more programs, and the one or more programs are stored in the memory and configured to be executed by the CPU. The one or more programs include instructions for performing the business logic configuration methods provided by the embodiments of the present application.

Embodiments of the present application further provide a non-transitory computer-readable storage medium, where instructions in the storage medium, when executed by a processor of a server, enable the server to perform the service logic configuration method provided in the embodiments shown in fig. 2 to 9.

Embodiments of the present application further provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the service logic configuration method provided in the embodiments shown in fig. 2 to 9.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (9)

1. A method for configuring service logic, the method comprising:

receiving a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes, wherein each function node in the plurality of function nodes is an operation set for realizing a function, and the selection instruction is triggered when a user selects a target function node option from a plurality of function node options displayed on a configuration function interface;

acquiring the sequence of the target function nodes and acquiring attribute configuration information of each target function node in the target function nodes, wherein the attribute configuration information comprises input parameters of the corresponding function node, and the input parameters comprise fixed values configured by the user or output results of other function nodes;

verifying attribute configuration information of each target function node in the plurality of target function nodes;

if the attribute configuration information of each target function node passes the verification, generating a node variable reference relation graph according to the attribute configuration information of each target function node and the sequence of the target function nodes, wherein the node variable reference relation graph is used for indicating the dependency relation among the target function nodes;

generating an instruction code for realizing service logic according to the node variable reference relation graph, the target function nodes and the attribute configuration information of the target function nodes, and generating a service logic configuration file according to the instruction code, wherein the service logic configuration file comprises the instruction code.

2. The method of claim 1, wherein obtaining attribute configuration information for each of the plurality of target function nodes comprises:

receiving a configuration instruction for configuring a first functional node, wherein the first functional node is any one of the target functional nodes;

displaying a configuration option corresponding to the first functional node according to the configuration instruction;

and acquiring attribute configuration information input in a configuration option corresponding to the first functional node, and taking the acquired attribute configuration information as the attribute configuration information of the first functional node.

3. The method of claim 1, wherein the plurality of target function nodes are selected in sequence;

the obtaining of the sequence of the target function nodes includes:

and acquiring a selection sequence when the target function nodes are sequentially selected, and taking the selection sequence as the sequence of the target function nodes.

4. The method according to claim 1, wherein the generating a node variable reference relationship graph according to the attribute configuration information of each target function node and the precedence order of the plurality of target function nodes comprises:

determining the parallel processing attribute of each target function node according to the attribute configuration information of each target function node and the sequence of the target function nodes, wherein the parallel processing attribute is used for indicating the possibility of parallel execution of the corresponding target function node and any one of the rest target function nodes;

and generating the node variable reference relation graph according to the sequence of the target function nodes and the parallel processing attribute of each target function node.

5. The method according to any of claims 1-4, wherein after generating the service logic profile, further comprising:

correspondingly storing the service logic configuration file and a target service activity identifier;

the method further comprises the following steps:

receiving a service request carrying the target service activity identifier, wherein the service request also carries a service parameter value;

acquiring the service logic configuration file according to the target service activity identifier;

and sequentially executing part or all of the target function nodes according to the service logic configuration file and the service parameter value.

6. The method of claim 5, wherein said executing some or all of the plurality of target functional nodes in sequence according to the service logic profile and the service parameter value comprises:

analyzing the service logic configuration file to obtain attribute configuration information of each target function node in the target function nodes and a dependency relationship among the target function nodes;

and sequentially executing part or all of the target function nodes according to the dependency relationship among the target function nodes, the attribute configuration information of each target function node and the service parameter value.

7. The method according to claim 6, wherein the sequentially executing some or all of the target function nodes according to the dependency relationship among the target function nodes, the attribute configuration information of each target function node, and the service parameter value comprises:

if the second function node is the first function node in the target function nodes, determining an input parameter value of the second function node according to the attribute configuration information of the second function node and the service parameter value;

if the second functional node is not the first functional node in the target functional nodes, determining an input parameter value of the second functional node according to the attribute configuration information of the second functional node and the execution result of the previous functional node of the second functional node;

executing the second functional node according to the attribute configuration information and the input parameter value of the second functional node;

and if the functional node behind the second functional node is determined to be two parallel branch functional nodes according to the dependency relationship between the target functional nodes, selecting one functional node from the two parallel branch functional nodes according to the execution result of the second functional node, taking the selected functional node as the second functional node, returning the attribute configuration information of the second functional node and the execution result of the previous functional node of the second functional node, and determining the input parameter value of the second functional node until no functional node exists behind the second functional node.

8. An apparatus for configuring service logic, the apparatus comprising:

a receiving module, configured to receive a selection instruction for selecting a plurality of target function nodes from a plurality of function nodes, where each function node in the plurality of function nodes is an operation set for implementing a function, and the selection instruction is triggered when a user selects a target function node option from a plurality of function node options displayed in a configuration function interface;

an obtaining module, configured to obtain a sequence of the target function nodes and obtain attribute configuration information of each target function node in the target function nodes, where the attribute configuration information includes input parameters of a corresponding function node, and the input parameters include fixed values configured by the user or output results of other function nodes;

the generating module is used for generating a service logic configuration file according to the target function nodes, the attribute configuration information of each target function node and the sequence of the target function nodes;

wherein the generating module comprises:

the checking submodule is used for checking the attribute configuration information of each target function node in the plurality of target function nodes;

the first generation submodule is used for generating a node variable reference relation graph according to the attribute configuration information of each target function node and the sequence of the target function nodes if the attribute configuration information of each target function node passes the verification, and the node variable reference relation graph is used for indicating the dependency relation among the target function nodes;

and the second generation submodule is used for generating an instruction code for realizing service logic according to the node variable reference relationship diagram, the target function nodes and the attribute configuration information of the target function nodes, and generating the service logic configuration file according to the instruction code, wherein the service logic configuration file comprises the instruction code.

9. A computer-readable storage medium, having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the business logic configuration method of any one of claims 1 to 7.

Images