CN114637549A

CN114637549A - Data processing method, system and storage medium for service grid-based application

Info

Publication number: CN114637549A
Application number: CN202210163665.9A
Authority: CN
Inventors: 王夕宁; 曾宇星; 刘阳; 张岚
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-02-22
Filing date: 2022-02-22
Publication date: 2022-06-17

Abstract

The invention discloses a data processing method, a system and a storage medium of application based on a service grid. Wherein, the method comprises the following steps: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information. The invention solves the technical problem of configuring the application start into an intrusive mode, and achieves the technical effect of configuring the application start without the intrusive mode.

Description

Data processing method, system and storage medium for service grid-based application

Technical Field

The invention relates to the field of cloud computing and data processing, in particular to a data processing method, a data processing system and a storage medium for application based on a service grid.

Background

At present, when application self-starting is carried out, built-in identification information needs to be arranged in the application, and a server can identify the built-in application according to the identification information so as to carry out application starting.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the invention provides a data processing method, a system and a storage medium of an application based on a service grid, which are used for at least solving the technical problem that the configuration of application starting is intrusive.

According to an aspect of an embodiment of the present invention, there is provided a data processing method for a service grid-based application, including: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information.

Optionally, determining configuration information of the application based on the logic data, the method comprising: determining agent configuration information of the application based on the logic data, wherein the configuration information comprises agent configuration information which is used for representing the configuration of a service grid agent of the application.

Optionally, the configured service grid agent is configured to enable the port listener to listen to the port, enable the interceptor to intercept the call request when the call request of the port is listened to, and enable the executor to call the logic data based on the call request intercepted by the interceptor.

Optionally, the application is started based on the configuration information, and the method includes: the application is launched based on the logical data called by the executor.

Optionally, the application is launched based on the logical data invoked by the executor, the method comprising: based on the logical data registered in the services grid, called by the executor, an application is launched.

Optionally, the application is launched based on the logic data registered in the services grid called by the executor, the method comprising: in response to the executor successfully calling the logical data registered in the services grid, an application is launched based on the logical data.

Optionally, determining configuration information of the application based on the logic data, the method comprising: load configuration information is determined based on the logic data, wherein the configuration information includes load configuration information for configuring an execution logic component injected by the application at creation time.

Optionally, the configured execution logic component is configured to obtain logic data registered in the service grid, where the logic data registered in the service grid is called by an executor in a service grid agent of the application; and/or, the execution logic component for determining information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

Optionally, the method further comprises: acquiring a configuration range of the logic data, wherein the configuration range is a range of loads to which the logic data is applied.

Optionally, determining configuration information of the application based on the logic data, the method comprising: configuration information is determined based on the configuration scope and the logic data.

Optionally, the method further comprises: the logical data is defined by the client.

According to an aspect of the embodiments of the present invention, another data processing method for a service grid-based application is provided from a system side, including: acquiring logic data of an application to be started from a client by calling a first interface, wherein the first interface comprises a first parameter, the parameter value of the first parameter is logic data, the logic data is used for representing a logic function executed by the application in the starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; starting the application based on the configuration information to obtain a starting result; and outputting a starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and a parameter value of the second parameter is the starting result.

According to another aspect of the embodiments of the present invention, there is provided a data processing apparatus for a service grid-based application, including: the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring logic data of an application to be started, the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; the first determining unit is used for determining the configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; a first starting unit for starting the application based on the configuration information.

According to another aspect of the embodiments of the present invention, there is provided another data processing apparatus for a service grid-based application from a system side, including: the second obtaining unit is used for obtaining the logic data of the application to be started from the client by calling the first interface, wherein the first interface comprises a first parameter, the parameter value of the first parameter is the logic data, the logic data is used for representing the logic function executed by the application in the starting process, and the application is composed of a service grid; the second determining unit is used for determining the configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the second starting unit is used for starting the application based on the configuration information to obtain a starting result; and the output unit is used for outputting the starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and the parameter value of the second parameter is the starting result.

The embodiment of the invention also provides a computer readable storage medium. The computer readable storage medium comprises a stored program, wherein the program, when executed by a processor, controls an apparatus in which the computer readable storage medium is located to perform a data processing method of a service grid based application according to an embodiment of the present invention.

The embodiment of the invention also provides a processor. The processor is used for running a program, wherein the program executes the data processing method of the service grid-based application of the embodiment of the invention when running.

According to another aspect of the embodiments of the present invention, there is provided a data processing system for a service grid-based application, comprising: a processor; a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information.

In the embodiment of the invention, the logic data of the application to be started is obtained, wherein the logic data is used for representing the logic function executed in the starting process of the application, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is started based on the configuration information, namely, in the application, the logic of the application is not required to be changed, the configuration information is independently determined based on the logic data of the application, the application is controlled to be started based on the configuration information, and the method belongs to a mechanism for configuring the application starting in a non-invasive manner, so that the technical effect of configuring the application starting in a non-invasive manner is achieved, and the technical problem that the application starting is configured in an invasive manner is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a block diagram of a hardware structure of a computer terminal (or mobile device) for implementing a data processing method for a service grid-based application according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method for data processing of a service grid based application according to an embodiment of the present invention;

FIG. 3 is a flow chart of a method for data processing of a service grid-based application provided from the system side according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a system for a service grid-based application service custom launching configuration, according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of running a wasm plugin in a services grid proxy, in accordance with an embodiment of the present invention;

FIG. 6 is a schematic diagram of a services grid according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a data processing apparatus for serving grid based applications in accordance with an embodiment of the present invention;

FIG. 8 is a schematic diagram of a data processing apparatus for a service grid based application provided from the system side in accordance with an embodiment of the present invention;

fig. 9 is a block diagram of a computer terminal according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, some terms or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:

a service grid is often used to describe the micro-service network that makes up these applications and the interactions between the applications. As an infrastructure layer for handling inter-service communications. It is responsible for composing the complex service topology of modern cloud native applications to deliver requests reliably;

a service grid is typically comprised of a control plane and a data plane. In particular, the control plane is a set of services running in a dedicated namespace. These services perform a number of control management functions, including aggregating telemetry data, providing user-oriented Application Programming Interfaces (APIs), providing control data to data plane agents, and the like. They drive the behavior of the data plane, which is made up of a series of transparent proxies running alongside each service instance;

the extension logic is a section of custom logic executed by the application service in the starting process, and a user can customize extension according to an application scene;

proxy extension, which refers to the function of extending the data plane by writing a custom Filter (Filter) for a grid proxy (Envoy) proxy in a service grid;

the service grid agent configuration is that the data plane of the service grid is composed of a series of transparent agents running beside each service instance, and the service grid agent configuration refers to configuration data issued by a control surface to each service grid agent in order to enable the service grid to correctly agent service flow and realize service intercommunication and service management. The service grid configuration optimization means that the configuration data volume sent by the control plane to the service grid agent is reduced, and unnecessary pushing is reduced, so that the pushing efficiency of the service grid control plane is improved.

Example 1

There is also provided, in accordance with an embodiment of the present invention, an embodiment of a method for data processing for a service grid-based application, the steps illustrated in the flowchart of the figure being executable on a computer system, such as a set of computer-executable instructions, and although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be executed in an order different than that illustrated or described herein.

The method provided by the first embodiment of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Fig. 1 shows a hardware configuration block diagram of a computer terminal (or mobile device) for implementing a data processing method for a service grid-based application. As shown in fig. 1, the computer terminal 10 (or mobile device 10) may include one or more processors (shown as 102a, 102b, … …, 102n in the figure) which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, a memory 104 for storing data, and a transmission module 106 for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial BUS (USB) port (which may be included as one of the ports of the BUS), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

It should be noted that the one or more processors and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuit may be a single stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computer terminal 10 (or mobile device). As referred to in the embodiments of the application, the data processing circuit acts as a processor control (e.g. selection of a variable resistance termination path connected to the interface).

The memory 104 can be used for storing software programs and modules of application software, such as program instructions/data storage devices corresponding to the data processing method of the service grid-based application in the embodiment of the present invention, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the data processing method of the service grid-based application. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device 106 can be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the computer terminal 10 (or mobile device).

In the related technology, under typical timing scenarios such as internet of things, application monitoring, industrial internet and the like, a Data Source (Data Source, which represents who Data is generated by) usually generates timing Data continuously according to a certain period, one piece of timing Data is described by elements such as Metric, Tags, Timestamp, Fields and the like, the writing of the timing Data is characterized by continuous high-concurrency high-throughput writing, and writing of multiple reads is less, so that the Data is very suitable for being written by using a Log-Structured merge Tree (LSM-Tree for short) structure of a logarithmic structure, the LSM-Tree is a layered, ordered and disk-oriented Data structure, and the characteristic that the sequential writing of disk batches is far higher than the random writing performance is fully utilized.

Under the operating environment, the application provides a data processing method of the application based on the service grid as shown in fig. 2.

Fig. 2 is a flowchart of a data processing method of a service grid-based application according to an embodiment of the present invention.

As shown in fig. 2, the method may include the steps of:

step S202, logic data of the application to be started is obtained, wherein the logic data is used for representing the logic function executed by the application in the starting process, and the application is composed of a service grid.

In the technical solution provided by step S202 in the present invention, the logic data may be extension logic, and the logic function may be user-defined extension logic, where the extension logic may be a section of user-defined logic executed by the application service in the starting process.

In this embodiment, the logic data may be used to characterize the logic function performed by the application during the start-up process, for example, the user may customize the extension logic according to the application scenario.

In this embodiment, the logic data of the application to be started may be obtained, for example, a piece of custom logic executed by the application service during the starting process is obtained.

It should be noted that the logic data may be a Web Assembly (wsm) plug-in or an extensible scripting language (Lua) script that can be run in the service grid agent.

Step S204, determining the configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process.

In the technical solution provided by step S204 of the present invention, the configuration information may include the relevant configuration information of the interception setter and the relevant configuration information of the service grid agent injected when the application service is created.

It should be noted that the detailed information of the interception configuration may include, but is not limited to: a list of inbound ports whose traffic is to be redirected to the mesh agent; specifying a list of inbound ports to be excluded from redirection to the mesh agent; specifying a range of IP addresses to redirect to a mesh proxy; specifying a range of IP addresses to be excluded from redirection.

In this embodiment, the configuration information may be used to configure the load of the application during the boot process, such as workload boot configuration.

In this embodiment, the configuration information of the application may be determined based on the logic data, for example, the extended logic may be registered in the service grid through the extended logic register, and may be finally applied to the workload of the data plane, and the proxy configuration controller generates the workload initiation configuration and the proxy configuration including the extended logic by calling the extended logic register to obtain the corresponding extended logic information and obtaining the extended logic configuration range.

It should be noted that, in this embodiment, the extension logic configuration range may refer to a range in which extension logic is to be applied to data plane workloads, including a specified namespace or a specified specific certain workload, where a workload of each data plane has a namespace to which the extension logic belongs, and if the specification is a namespace, the extension logic configuration range means that the range of the data plane workload is all workloads under the entire namespace.

Step S206, the application is started based on the configuration information.

In the technical solution provided by step S206 of the present invention, the application may be started based on the configuration information, for example, after the workload starting configurator completes the relevant configuration information of the intercept setter and the service grid agent, the application is started.

For example, the service grid agent includes a port listener, an interceptor, and an extended logic executor in the present application, where the port listener is a listener for a port accessed to the outside when the application service is started, and once a call to the port is found, the interceptor intercepts the request call and submits the request call to the extended logic executor that is called and registered by the extended logic executor to execute, and the state detector is configured to ensure that, before the application service is started ready, the extended logic executor in the service grid agent is executed completely and obtains a successful execution result, otherwise, retry is performed within a specified time period until the execution is completed.

Through the steps S202 to S206 in the present application, logic data of an application to be started is obtained, where the logic data is used to characterize a logic function executed by the application in the starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is started based on the configuration information, namely, in the application, the logic of the application is not required to be changed, the configuration information is independently determined based on the logic data of the application, the application is controlled to be started based on the configuration information, and the method belongs to a mechanism for configuring the application starting without intrusion, improves the efficiency of starting the application, solves the technical problem that the application starting is configured without intrusion, and achieves the technical effect of configuring the application starting without intrusion.

The above method of this embodiment is further described below.

As an optional implementation manner, in step S204, determining configuration information of the application based on the logic data, the method further includes: determining agent configuration information of the application based on the logic data, wherein the configuration information comprises agent configuration information which is used for representing the configuration of a service grid agent of the application.

In this embodiment, the agent configuration including the extension logic issues the agent configuration to the corresponding service grid agent according to the specified configuration range.

In this embodiment, an extended logical configuration scope may refer to a scope in which extended logic is to be applied to a data plane workload, including a specified namespace or a specified specific certain workload.

In this embodiment, the proxy configuration information of the application may be determined based on the logic data, for example, the proxy configuration controller generates the proxy configuration containing the extended logic by calling the extended logic registrar to obtain the corresponding extended logic information and obtaining the extended logic configuration range.

As an alternative embodiment, the service grid agent is configured to enable the port listener to listen to the port, enable the interceptor to intercept the call request when the call request of the port is listened to, and enable the executor to call the logic data based on the call request intercepted by the interceptor.

In this embodiment, the configured service grid agent may be configured to enable a port listener to listen to a port, enable an interceptor to intercept a call request when the call request of the port is intercepted, and enable an executor to call logic data based on the call request intercepted by the interceptor, for example, the service grid agent includes the port listener, the interceptor, and an extension logic executor in this application, where the port listener is to listen to a port accessed to the outside when the application service is started, and once a call to the port is found, the interceptor intercepts the request call and sends the request call to the extension logic executor to call the registered extension logic to execute the extension logic executor.

As an optional implementation manner, in step S206, the application is started based on the configuration information, and the method includes: the application is launched based on the logical data called by the executor.

In this embodiment, the application may be launched based on the logical data called by the executor, for example, the execution request may be made by the expansion logic executor calling the registered expansion logic, where the request may be a call of an external access port by an application service at the time of launching.

As an alternative embodiment, the application is launched based on the logical data invoked by the executor, the method comprising: the application is launched based on the logical data that has been registered in the services grid that is invoked by the executor.

In this embodiment, the extension logic may be registered into the services grid through an extension logic registry and may ultimately be applied in the workload of the data plane.

In this embodiment, the application may be started based on the logic data registered in the service grid called by the executor, for example, the extensible logic executor calls the registered extensible logic, the extensible logic finishes executing, and obtains a successful execution result, and starts the application.

As an alternative embodiment, the application is started based on the logic data registered in the service grid and called by the executor, and the method comprises the following steps: in response to the executor successfully calling the logical data registered in the services grid, an application is launched based on the logical data.

In this embodiment, the application may be launched based on the logical data in response to the executor successfully calling the logical data registered in the service grid, e.g., the status detector launches the application if the extended logical executor guarantees a successful execution result.

For example, the status detector may be used to ensure that the extended logic executor in the service grid agent completes execution and obtains a successful execution result before the application service is ready to start, otherwise, the execution will be retried within a specified time period until the execution is completed.

As an alternative implementation, step S204 determines the configuration information of the application based on the logic data, and the method includes: load configuration information is determined based on the logic data, wherein the configuration information includes load configuration information for configuring an execution logic component injected by the application at creation time.

In this embodiment, the load configuration information may be a workload launch configuration and the execution logic component may be an execution logic component injected at application service creation time.

In this embodiment, the load configuration information may be determined based on the logic data, for example, the proxy configuration controller may generate the workload initiation configuration and the proxy configuration including the extended logic by calling the extended logic register to obtain the corresponding extended logic information and obtaining the extended logic configuration range.

It is noted that the workload configuration injector may be an execution logic component injected by the service grid data plane workload at creation time for the application service before startup, including a workload startup configurator and an extension logic obtainer.

As an alternative embodiment, the execution logic component is configured to obtain the logic data registered in the service grid, and the logic data registered in the service grid is called by an executor in the service grid agent of the application; and/or, the execution logic component for determining information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

In this embodiment, the configured execution logic component may be used to obtain logic data that has been registered into the service grid, for example, the workload injector may be an execution logic component that the service grid data plane workload injects at the time of creation for the application service prior to startup, including an extended logic obtainer.

In this embodiment, the logic data registered in the service grid may be called by an executor in the service grid agent of the application, for example, the extension logic registrar may register the extension logic in the service grid and ultimately apply it in the workload of the data plane, and the extension logic executor calls the registered extension logic to execute a request for a call to the port listener.

In this embodiment, the execution logic component may be for determining information to configure the service grid agents and/or the intercept settings associated with the service grid agents, for example, the workload injector may be an execution logic component that the service grid data plane workload injects for application service creation prior to startup, including a workload startup configurator, wherein the workload startup configurator includes the relevant configuration information of the intercept settings and/or the relevant configuration information of the service network agents injected at application service creation.

For example, the extension logic obtainer is used for obtaining user-defined registered extension logic executed by the application service in the starting process; the workload starting configurator comprises related configuration information of an interception configurator and related configuration information of a service grid agent injected in the process of creating the application service, wherein the detailed information of the interception configuration can include but is not limited to: a list of inbound ports whose traffic is to be redirected to the mesh agent; specifying a list of inbound ports to be excluded from redirection to the mesh agent; specifying an address range (Internet Protocol, IP for short) to redirect to a grid agent; specifying a range of IP addresses to be excluded from redirection.

As an optional implementation, the method further comprises: acquiring a configuration range of the logic data, wherein the configuration range is a range of loads to which the logic data is applied.

In this embodiment, the configuration scope may be an extended logical configuration scope, which in this application may be a scope in which extended logic is to be applied to a data plane workload, including a specified namespace or a specified specific certain workload.

It should be noted that the service grid control panel is responsible for managing and configuring the configuration injector of the service grid data plane workload and the configuration and lifecycle of the service grid data plane workload, wherein the lifecycle of the workload may be the start, stop, ready and upgrade of a workload container group, and the workload of each data plane has a name space to which it belongs, if it is specified as a name space. It means that the scope is all the workload under the entire namespace.

In this embodiment, the configured range of logical data may be obtained, such as obtaining a range of extended logic to be applied to the data plane workload.

As an alternative implementation, step S204 determines the configuration information of the application based on the logic data, and the method includes: configuration information is determined based on the configuration scope and the logic data.

In this embodiment, the configuration information may be determined based on the configuration scope and the logic data, for example, the proxy configuration controller may generate the workload starting configuration and the proxy configuration including the extended logic by calling the extended logic registrar to obtain the corresponding extended logic information and the extended logic configuration scope.

As an alternative embodiment, the logical data is defined by the client.

In this embodiment, the logic data may be defined by the client, for example, by a Web Assembly (wasm) plug-in or extensible scripting language (Lua) script running in the service grid proxy.

For example, Envoy is a high performance, programmable L3, L4, and L7 proxy, which is used as a proxy for the ASM data plane, and its connection and traffic processing core is a Network Filter (Network Filter), which once fused into a Filter Chain (Filter Chain) can implement advanced functions such as access control, data or protocol conversion, data enhancement, auditing, etc. By adding new filters, it is possible to extend the existing functionality set of Envoy. Currently, there are two ways to add new filters, static precompilation and dynamic runtime loading, respectively.

In the embodiment of the invention, the logic of the application is not required to be changed, the configuration information is independently determined based on the logic data of the application, and the application starting is controlled based on the configuration information, so that the method belongs to a mechanism for configuring the application starting in a non-invasive manner, the efficiency of the application starting is improved, the technical problem that the application starting is configured in an invasive manner is solved, and the technical effect of configuring the application starting in a non-invasive manner is achieved.

According to the embodiment of the invention, a method for processing data of the application is also provided from the system side.

Fig. 3 is a flowchart of a data processing method of a service grid-based application provided from a system side according to an embodiment of the present invention. As shown in fig. 3, the method may include the steps of:

step S302, logic data of the application to be started is obtained from the client by calling a first interface, wherein the first interface comprises a first parameter, a parameter value of the first parameter is logic data, the logic data is used for representing a logic function executed in the starting process of the application, and the application is composed of a service grid.

In the technical solution provided by step S302 of the present invention, the first interface may be a remote communication interface disposed on the system, or may also be a virtual button on a visual screen, which is not limited herein.

In this embodiment, the logic data of the application to be started may be obtained from the client by calling the first interface, for example, a piece of custom extension logic data executed during the starting process of the application to be started may be obtained from the client by calling the first interface.

Step S304, determining the configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process.

In the technical solution provided by step S304 of the present invention, the configuration information of the application may be determined based on the logic data, where the configuration information may include relevant configuration information of the intercept setter and relevant configuration information of the service grid agent injected when the application service is created, for example, by using the extended logic registrar, the extended logic may be registered in the service grid and may be finally applied to the workload of the data plane, and the agent configuration controller generates the workload start-up configuration and the agent configuration including the extended logic by calling the extended logic registrar to obtain corresponding extended logic information and obtain the extended logic configuration range.

And step S306, starting the application based on the configuration information to obtain a starting result.

In the technical solution provided by step S306 of the present invention, the application may be started based on the configuration information to obtain a starting result, for example, after the workload starting configurator completes the relevant configuration information of the interception setter and the service grid agent, the application is started.

For example, the service grid agent includes a port listener, an interceptor, and an extended logic executor in the application, where the port listener is configured to monitor an externally accessed port when an application service is started, and once a call to the port is found, the interceptor intercepts the request call and sends the request call to the extended logic executor to call and register the extended logic executor to execute the request call, and the state detector is configured to ensure that, before the application service is started ready, the extended logic executor in the service grid agent is executed completely and obtains a successful execution result, otherwise, retry is performed within a specified time period until the execution is completed.

And step S308, outputting a starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and a parameter value of the second parameter is the starting result.

In the technical solution provided by step S308 of the present invention, the second interface may be a remote communication interface disposed on the system, or may also be a virtual button on the visual screen, which is not limited herein.

In this embodiment, the start result may be output to the client by calling the second interface, for example, when the application starts successfully, the start result is output to the client by calling the second interface.

Example 2

Preferred embodiments of the above-described method of this embodiment are further described below.

In the related art, for application self-starting, a user needs to embed identification information into an application, and a server can identify the built-in application according to the identification information to start the application, which belongs to an invasive mechanism aiming at application starting, the application needs to be changed and is inflexible, and the technical problem that the application starting is configured to be invasive exists. The application provides a user-defined non-intrusive mechanism for configuring application service starting, and provides a method and a system for executing fusion based on port monitoring, interception and extended logic aiming at the extended logic registered by a user, supports the execution readiness of the extended configuration before the application service is started by detecting the state of a service grid agent in combination with the application starting and acquiring corresponding extended logic information and an extended logic configuration range by calling an extended logic register based on a mechanism for dynamically generating the workload starting configuration, dynamically generates the workload starting configuration and the agent configuration containing the extended logic, and sends the agent configuration to a corresponding agent according to a specified configuration range.

In the related art, a control method for self-starting of an application is provided, specifically, firstly, the identification information of a built-in application is reported; the identification information is used for identifying the built-in application, so that the server can identify the built-in application according to the identification information; receiving a self-starting attribute configured for the built-in application; and controlling the self-starting of the built-in application according to the self-starting attribute.

The defects of the scheme are as follows: firstly, a user needs to embed identification information into an application service, and compared with the application, the method belongs to an intrusive mechanism for configuring the application service starting, the application needs to be changed, and the mechanism is not flexible.

FIG. 4 is a diagram of a system for providing a customized launching configuration of an application service based on a service grid according to an embodiment of the present invention. As shown in FIG. 4, a system 400 for custom launching configuration of an application service based on a services grid can include: a service network control plane 401, an extension logic 402, an extension logic controller 403, an extension logic configuration scope 404, an agent configuration controller 405, a workload initiation configuration 406, an agent configuration 407 containing extension logic, a workload configuration injector 408, a workload initiation configurator 409, an extension logic obtainer 410, registered extension logic 411, a service grid data plane workload 412, an intercept setter 413, a service grid agent 414, a port listener 415, an interceptor 416, an extension logic executor 417, a state detector 418, and an application service 419.

The above-described components of the system are further described below.

The service grid control plane 401 is responsible for managing and configuring the service grid data plane workload configuration injector 408 and the configuration and lifecycle of the service grid data plane workload 412, wherein the lifecycle of the workload 412 refers to the starting, stopping, readiness, upgrading, etc. of a workload container group (Pod).

The extension logic 402 refers to a piece of customization logic executed by the application service 419 during the starting process in the present application, and a user can customize an extension according to an application scenario, and in the present application, it is usually expressed as a Web Assembly (wap) plug-in or a Lua script that can run in a service grid proxy.

FIG. 5 is a diagram illustrating the operation of a wasm plugin in a services grid proxy, in accordance with an embodiment of the present invention. As shown in fig. 5, after acquiring the update event (ondate event), the first native filter extension 501 is run, then the wasm plug-in the native filter extension 502 supporting the network group leader plug-in will run in the second network assembly virtual machine 505 in the proxy, and the network assembly plug-in may also select the first network assembly virtual machine 504 when running, and then the second native filter extension 503 is run.

Envoy is a high performance, programmable L3, L4, and L7 proxy that is used as a proxy for the ASM data plane. At the core of the connection and traffic processing of Envoy, a Network Filter (Network Filter) is capable of implementing advanced functions such as access control, data or protocol conversion, data enhancement, auditing and the like once fused into a Filter Chain (Filter Chain). By adding new filters, it is possible to extend the existing functionality set of Envoy. Currently, there are two ways to add new filters, static precompilation and dynamic runtime loading, respectively.

Static precompilation, integrating other filters into the source code of the Envoy, and compiling a new version of the Envoy. The disadvantage of this approach is that you need to maintain the invoy version and keep it in sync with the official release. Furthermore, since Envoy is implemented in C + +, newly developed filters must also be implemented in C + +.

And dynamic runtime loading, wherein a new filter is dynamically loaded into the Envoy agent at runtime.

It is apparent that the second approach greatly simplifies the process of extending Envoy. This solution relies on a new technology called Web Assembly (WASM), which is an efficient portable binary instruction format that provides an embeddable and isolatable execution environment.

Through extension logic registry 403, extension logic 402 can be registered into the services grid and ultimately can be applied to the data plane's workload.

Extended logical configuration scope 404 refers in this application to the scope of data plane workloads, including a specified namespace or a specified specific certain workload, to which each data plane workload belongs, and if the specification is a namespace, it means that the scope is all workloads under the entire namespace.

The agent configuration controller 405 generates a workload starting configuration 406 and an agent configuration 407 containing extension logic by calling the extension logic registrar 403 to obtain corresponding extension logic information and obtaining an extension logic configuration range 404.

The workload configuration injector 408 refers in this application to the execution logic components injected by the service grid data plane workload 412 when created for the application services 419 prior to startup, including the workload startup configurator 409 and the extension logic obtainer 410.

The extension logic obtainer 410 is for obtaining user-defined registered extension logic 411 executed by the application service 119 during startup.

Workload launch configurator 409 includes configuration information relating to intercept setter 413 and configuration information relating to service grid agent 414 injected at the time of application service 419 creation.

Wherein, the detailed information of the interception configuration comprises: a list of inbound ports whose traffic is to be redirected to the mesh agent 114; specifying a list of inbound ports to be excluded from redirection to the mesh agent; specifying a range of IP addresses to redirect to a mesh proxy; specifying a range of IP addresses to be excluded from redirection.

The service grid agent 414 includes a port listener 415, an interceptor 416, and an extension logic executor 417 in the present application, where the port listener 415 refers to a listening to a port accessed to the outside when the application service 419 is started, and once a call to the port is found, the interceptor 416 intercepts the request call and delivers the request call to the extension logic 411 called and registered by the extension logic executor 417 for execution.

The status detector 418 is used to ensure that the extended logic executors 417 in the service grid agent 414 are executed and obtain successful execution results before the application services 419 are ready to start, otherwise, they will retry within a specified time period until they are executed.

Fig. 6 is a schematic diagram of a service grid 600 according to an embodiment of the present invention, where the service grid 600 is mainly used for facilitating secure and reliable communication between multiple microservices, which means that an application is decomposed into multiple smaller services or instances and distributed to run on different clusters/machines.

As shown in FIG. 6, a microservice may include an application service instance A and an application service instance B, which form a functional application layer of a service grid 600. In one embodiment, application service instance A runs as a container/process 608 on a machine/workload container set 614(POD) and application service instance B runs as a container/process 610 on a machine/workload container set 616 (POD).

In one embodiment, application service instance a may be a commodity inquiry service and application service instance B may be a commodity ordering service.

As shown in FIG. 6, application service instance A and grid agent (sidecar)603 coexist in machine workload container 614, and application service instance B and grid agent 605 coexist in machine workload container 614. Mesh agent 603 and mesh agent 605 form a data plane layer (data plane) of service mesh 600. Where grid agent 603 and grid agent 605 are respectively in container/process 604, container/process 604 may receive request 612 for commodity query services, grid agent 606 is running, and grid agent 603 and application service instance a may communicate in both directions, and grid agent 605 and application service instance B may communicate in both directions. In addition, there may be two-way communication between the grid agent 603 and the grid agent 605.

In one embodiment, all traffic for application service instance A is routed through the grid proxy 603 to the appropriate destination and all network traffic for application service instance B is routed through the grid proxy 605 to the appropriate destination. It should be noted that the network traffic mentioned herein includes, but is not limited to, forms of hypertext Transfer Protocol (HTTP), Representational State Transfer (REST), high-performance, general-purpose open-source framework (GRPC), and data structure storage system (Redis) in open-source memory.

In one embodiment, the functionality of extending the data plane layer may be implemented by writing a custom Filter (Filter) for an agent (Envoy) in service grid 600, which may be configured to allow the service grid to properly proxy service traffic, implement service interworking and service governance. Grid agent 603 and grid agent 605 may be configured to perform at least one of the following functions: service discovery (service discovery), health checking (health checking), Routing (Routing), Load Balancing (Load Balancing), authentication and authorization (authentication and authorization), and observability (observability).

As shown in fig. 6, the services grid 600 also includes a control plane layer. Where the control plane layer may be a group of services running in a dedicated namespace, these services are hosted by the hosting control plane component 601 in the machine/workload container group (machine/Pod) 602. As shown in fig. 6, hosted control plane component 601 is in bidirectional communication with mesh agent 603 and mesh agent 605. The managed control plane component 601 is configured to perform some control management functions. For example, hosted control plane component 601 receives telemetry data transmitted by mesh agent 603 and mesh agent 605, which may be further aggregated. These services, hosting control plane component 601, may also provide user-oriented Application Programming Interfaces (APIs) to more easily manipulate network behavior, as well as provide configuration data to grid agents 603 and 605, and the like.

In the above embodiments of the present invention, a method and a system for self-defined start-up configuration of application services based on a service grid are provided by performing fusion based on port monitoring, interception and extended logic, and based on dynamically generating workload start-up configuration, aiming at the extended logic registered by a user, combining with state detection of a service grid agent when an application is started, supporting the ready execution of the extended configuration before the start of the application services, acquiring corresponding extended logic information and an extended logic configuration range by calling an extended logic register, dynamically generating workload start-up configuration and agent configuration including the extended logic, and issuing the agent configuration to a corresponding agent according to a specified configuration range, thereby realizing the user-defined non-intrusive configuration aiming at the start of the application services, and solving the technical problem that the configuration of application start-up is intrusive, the technical effect of configuring the application starting in a non-invasive manner is achieved.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 3

According to an embodiment of the present invention, there is also provided a data processing apparatus for a service grid-based application, for implementing the data processing method for a service grid-based application shown in fig. 2.

Fig. 7 is a schematic diagram of a data processing apparatus for an application according to an embodiment of the present invention. As shown in fig. 7, the data processing apparatus 700 of the application may include: a first acquiring unit 701, a first determining unit 702, and a first starting unit 703.

A first obtaining unit 701, configured to obtain logic data of an application to be started, where the logic data is used to represent a logic function executed by the application in a starting process, and the application is formed by a service grid;

a first determining unit 702, configured to determine configuration information of an application based on the logic data, where the configuration information is used to configure a load of the application during a starting process;

the first starting unit 703 starts the application based on the configuration information.

Optionally, the first determining unit 702 includes: the device comprises a first determination module and a second determination module. The first determining module is used for determining the agent configuration information of the application based on the logic data, wherein the configuration information comprises agent configuration information, and the agent configuration information is used for representing the configuration of the service grid agent of the application; a second determining module, configured to determine load configuration information based on the logic data, where the configuration information includes load configuration information used to configure an execution logic component injected by the application at the time of creation;

the configured service grid agent is used for enabling the port monitor to monitor the port, enabling the interceptor to intercept the calling request under the condition of monitoring the calling request of the port, and enabling the actuator to call the logic data based on the calling request intercepted by the interceptor; the configured execution logic component is used for acquiring logic data registered in the service grid, and the logic data registered in the service grid is called by an executor in a service grid agent of the application; and/or, the execution logic component for determining information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

Optionally, the first enabling unit 703 includes: a first starting module, wherein the first starting module may include: a first promoter unit, wherein the first promoter unit may comprise: a first starter module. The first starting module is used for starting the application based on the logic data called by the executor; a first sub-subunit for launching an application based on the logic data registered in the service grid, which is called by the executor; and the first starting submodule is used for responding to the executor successfully calling the logic data registered in the service grid and starting the application based on the logic data.

Optionally, the apparatus further comprises: a second obtaining module, wherein the second obtaining module may include: and a third determining module. The second obtaining module is used for obtaining a configuration range of the logic data, wherein the configuration range is a range of a load applied by the logic data; and the third determining module is used for determining the configuration information based on the configuration range and the logic data.

Wherein in the device the logical data is defined by the client.

In the embodiment of the present invention, the first obtaining unit 701 is configured to obtain logic data of an application to be started, where the logic data is used to characterize a logic function executed by the application in a starting process, and the application is formed by a service grid; a first determining unit 702, configured to determine configuration information of an application based on the logic data, where the configuration information is used to configure a load of the application during a starting process; the first starting unit 703 is configured to start the application based on the configuration information, that is, in the present application, the logic of the application itself does not need to be changed, but the configuration information is determined independently based on the logic data of the application itself, and the application start is controlled based on the configuration information.

It should be noted here that the first acquiring unit 701, the first determining unit 702, and the first starting unit 703 correspond to steps S202 to S206 in embodiment 1, and the three units are the same as the corresponding steps in the implementation example and the application scenario, but are not limited to the disclosure in the first embodiment. It should be noted that the above units as a part of the apparatus may operate in the computer terminal 10 provided in the first embodiment.

According to an embodiment of the present invention, there is also provided, from the system side, a data processing apparatus for a service grid-based application for implementing the data processing method for a service grid-based application shown in fig. 3.

Fig. 8 is a schematic diagram of a data processing apparatus of an application provided from the system side according to an embodiment of the present invention. As shown in fig. 8, the data processing apparatus 800 of the application may include: a second acquisition unit 801, a second determination unit 802, a second activation unit 803, and an output unit 804.

A second obtaining unit 801, configured to obtain logic data of an application to be started from a client by calling a first interface, where the first interface includes a first parameter, a parameter value of the first parameter is the logic data, the logic data is used to characterize a logic function executed by the application in a starting process, and the application is formed by a service grid;

a second determining unit 802, configured to determine configuration information of the application based on the logic data, where the configuration information is used to configure a load of the application during a starting process;

a second starting unit 803, configured to start an application based on the configuration information, and obtain a starting result;

the output unit 804 is configured to output the start result to the client by invoking a second interface, where the second interface includes a second parameter, and a parameter value of the second parameter is the start result.

It should be noted here that the second acquiring unit 801, the second determining unit 802, the second starting unit 803 and the output unit 804 described above correspond to steps S302 to S308 in embodiment 1, and the three units are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the first embodiment described above. It should be noted that the above units as a part of the apparatus may operate in the computer terminal 10 provided in the first embodiment.

Example 4

Embodiments of the present invention may provide a data processing system of an application, which may include a computer terminal, which may be any one computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of a plurality of network devices of a computer network.

In this embodiment, the computer terminal may execute the program code of the following steps in the data processing method for a service grid-based application according to the embodiment of the present invention: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information.

Alternatively, fig. 9 is a block diagram of a computer terminal according to an embodiment of the present invention. As shown in fig. 9, the computer terminal a may include: one or more processors 902 (only one shown), a memory 904, and a transmitting device 906.

The memory may be configured to store software programs and modules, such as program instructions/modules corresponding to the method and apparatus for processing data of a service grid-based application in the embodiment of the present invention, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the data processing method of the service grid-based application. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory remotely located from the processor, which may be connected to terminal a through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The processor can call the information and application program stored in the memory through the transmission device to execute the following steps: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed in the starting process of the application, and the application is formed by a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information.

Optionally, the processor may further execute the program code of the following steps: determining agent configuration information of the application based on the logic data, wherein the configuration information comprises agent configuration information used for representing the configuration of the service grid agent of the application.

Optionally, the processor may further execute the program code of the following steps: the configured service grid agent is used for enabling the port monitor to monitor the port, enabling the interceptor to intercept the calling request under the condition of monitoring the calling request of the port, and enabling the executor to call the logic data based on the calling request intercepted by the interceptor.

Optionally, the processor may further execute the program code of the following steps: the application is launched based on the logical data called by the executor.

Optionally, the processor may further execute the program code of the following steps: the application is launched based on the logical data that has been registered in the services grid that is invoked by the executor.

Optionally, the processor may further execute the program code of the following steps: in response to the executor successfully calling the logical data registered in the services grid, an application is launched based on the logical data.

Optionally, the processor may further execute the program code of the following steps: load configuration information is determined based on the logic data, wherein the configuration information includes load configuration information for configuring an execution logic component injected by the application at creation time.

Optionally, the processor may further execute the program code of the following steps: the configured execution logic component is used for acquiring logic data registered in the service grid, and the logic data registered in the service grid is called by an executor in a service grid agent of the application; and/or, the execution logic component for determining information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

Optionally, the processor may further execute the program code of the following steps: acquiring a configuration range of the logic data, wherein the configuration range is a range of loads to which the logic data is applied.

Optionally, the processor may further execute the program code of the following steps: configuration information is determined based on the configuration scope and the logic data.

Optionally, the processor may further execute the program code of the following steps: the logical data is defined by the client.

As an optional implementation manner, the processor may further call the information and the application program stored in the memory through the transmission device to perform the following steps: acquiring logic data of an application to be started from a client by calling a first interface, wherein the first interface comprises a first parameter, the parameter value of the first parameter is logic data, the logic data is used for representing a logic function executed by the application in the starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; starting the application based on the configuration information to obtain a starting result; and outputting a starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and a parameter value of the second parameter is the starting result.

The embodiment of the invention provides a scheme for self-defining starting configuration of application service based on a service grid. The method comprises the steps that logic data of an application to be started are obtained, wherein the logic data are used for representing a logic function executed in the starting process of the application, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is started based on the configuration information, the technical problem that the configuration of the application starting is invasive is solved, and the technical effect of configuring the application starting in a non-invasive manner is achieved.

It can be understood by those skilled in the art that the structure shown in fig. 9 is only an illustration, and the computer terminal may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 9 is a diagram illustrating a structure of the electronic device. For example, the computer terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 9, or have a different configuration than shown in FIG. 9.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

The embodiment of the invention also provides a storage medium. Optionally, in this embodiment, the storage medium may be configured to store a program code executed by the data processing method of the service grid-based application provided in the first embodiment.

Optionally, in this embodiment, the storage medium may be located in any one of computer terminals in a computer terminal group in a computer network, or in any one of mobile terminals in a mobile terminal group.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed by the application in a starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; the application is launched based on the configuration information.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: determining agent configuration information of the application based on the logic data, wherein the configuration information comprises agent configuration information used for representing the configuration of the service grid agent of the application.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: the configured service grid agent is used for enabling the port monitor to monitor the port, enabling the interceptor to intercept the calling request under the condition of monitoring the calling request of the port, and enabling the executor to call the logic data based on the calling request intercepted by the interceptor.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: the application is launched based on the logical data called by the executor.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: the application is launched based on the logical data that has been registered in the services grid that is invoked by the executor.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: in response to the executor successfully calling the logical data registered in the services grid, the application is launched based on the logical data.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: load configuration information is determined based on the logic data, wherein the configuration information includes load configuration information for configuring an execution logic component injected by the application at creation time.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: the configured execution logic component is used for acquiring logic data registered in the service grid, and the logic data registered in the service grid is called by an executor in a service grid agent of the application; and/or, the execution logic component for determining information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: acquiring a configuration range of the logic data, wherein the configuration range is a range of loads to which the logic data is applied.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: configuration information is determined based on the configuration scope and the logic data.

Optionally, the computer readable storage medium is further arranged to store program code for performing the steps of: the logical data is defined by the client.

As an optional implementation manner, in this embodiment, the computer-readable storage medium is further configured to store program codes for performing the following steps: acquiring logic data of an application to be started from a client by calling a first interface, wherein the first interface comprises a first parameter, the parameter value of the first parameter is logic data, the logic data is used for representing a logic function executed by the application in the starting process, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; starting the application based on the configuration information to obtain a starting result; and outputting a starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and the parameter value of the second parameter is the starting result.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technical content can be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A data processing method for a service grid based application, comprising:

acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed in the starting process of the application, and the application is composed of a service grid;

determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process;

launching the application based on the configuration information.

2. The method of claim 1, wherein determining configuration information for the application based on the logic data comprises:

determining agent configuration information of the application based on the logic data, wherein the configuration information comprises the agent configuration information, and the agent configuration information is used for representing the configuration of a service grid agent of the application.

3. The method of claim 2, wherein the service grid agent is configured to cause a port listener to listen for a port, to cause an interceptor to intercept a call request for the port if the call request is intercepted, and to cause an executor to call the logical data based on the call request intercepted by the interceptor.

4. The method of claim 3, wherein launching the application based on the configuration information comprises:

launching the application based on the logical data called by the executor.

5. The method of claim 4, wherein launching the application based on the logical data called by the executor comprises:

launching the application based on the logical data called by the executor that is registered in a services grid.

6. The method of claim 5, wherein launching the application based on the logical data called by the executor that is registered in a services grid comprises:

responsive to the executor successfully invoking the logical data registered in the services grid, launching the application based on the logical data.

7. The method of claim 1, wherein determining configuration information for the application based on the logic data comprises:

determining load configuration information based on the logic data, wherein the configuration information includes the load configuration information for configuring an execution logic component injected by the application at creation time.

8. The method of claim 7, wherein the execution logic component is configured to obtain the logical data registered in a services grid, wherein the logical data registered in the services grid is invoked by an executor in a services grid agent of the application; and/or, the execution logic component is to determine information to configure the service grid agent and/or an intercept setter associated with the service grid agent.

9. The method of claim 1, further comprising:

acquiring a configuration range of the logic data, wherein the configuration range is a range of loads applied to the application by the logic data.

10. The method of claim 9, wherein determining configuration information for the application based on the logic data comprises:

determining the configuration information based on the configuration scope and the logic data.

11. The method according to any of claims 1 to 10, wherein the logical data is defined by a client.

12. A data processing method for a service grid based application, comprising:

acquiring logic data of an application to be started from a client by calling a first interface, wherein the first interface comprises a first parameter, a parameter value of the first parameter is the logic data, the logic data is used for representing a logic function executed in the starting process of the application, and the application is composed of a service grid;

starting the application based on the configuration information to obtain a starting result;

and outputting the starting result to the client by calling a second interface, wherein the second interface comprises a second parameter, and a parameter value of the second parameter is the starting result.

13. A computer-readable storage medium, comprising a stored program, wherein the program, when executed by a processor, controls an apparatus in which the computer-readable storage medium is located to perform the method of any of claims 1-11.

14. A data processing system for servicing grid-based applications, comprising:

a processor;

a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: acquiring logic data of an application to be started, wherein the logic data is used for representing a logic function executed in the starting process of the application, and the application is composed of a service grid; determining configuration information of the application based on the logic data, wherein the configuration information is used for configuring the load of the application in the starting process; launching the application based on the configuration information.