CN116633856A - Service processing method, device, equipment and storage medium - Google Patents
Service processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116633856A CN116633856A CN202310630102.0A CN202310630102A CN116633856A CN 116633856 A CN116633856 A CN 116633856A CN 202310630102 A CN202310630102 A CN 202310630102A CN 116633856 A CN116633856 A CN 116633856A
- Authority
- CN
- China
- Prior art keywords
- application
- target
- routing rule
- service
- equipment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 28
- 238000012545 processing Methods 0.000 claims abstract description 122
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000011084 recovery Methods 0.000 claims description 29
- 238000011144 upstream manufacturing Methods 0.000 claims description 24
- 239000000523 sample Substances 0.000 claims 1
- 238000012423 maintenance Methods 0.000 description 18
- 238000010586 diagram Methods 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 4
- 101100478633 Escherichia coli O157:H7 stcE gene Proteins 0.000 description 3
- 101150115529 tagA gene Proteins 0.000 description 3
- 101150047697 tagB gene Proteins 0.000 description 3
- 101150009385 tcpI gene Proteins 0.000 description 3
- 101100368725 Bacillus subtilis (strain 168) tagF gene Proteins 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 206010033799 Paralysis Diseases 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/30—Routing of multiclass traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/38—Flow based routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
The business processing method, the business processing device, the business processing equipment and the storage medium provided by the application can be used in the distributed field. The method comprises the following steps: the service server obtains a service processing request corresponding to a target service through a current application, then determines a downstream application to be called by the current application according to the target service, determines the equipment types of a plurality of target deployment equipment where the downstream application is located, determines the flow proportion of the downstream application in the plurality of target deployment equipment according to the equipment types of each target deployment equipment, and then calls the downstream application deployed in the plurality of target deployment equipment according to the flow proportion to perform service processing to obtain a service processing result. The application can realize the flow diversion of the service processing requests according to the equipment types, and can reduce the influence on the deployment equipment and improve the reliability of service processing when the number of the service processing requests is large.
Description
Technical Field
The present application relates to the distributed field, and in particular, to a service processing method, apparatus, device, and storage medium.
Background
With the popularization of distributed system architecture, more and more enterprises change application systems from single application to distributed application, and a plurality of systems coordinate to work, so that the complexity is increased.
The applications in the distributed application system can be called according to the calling sequence, and in general, the calling party can initiate a service processing request of a target service to a designated service server according to information such as an IP address of the service server, namely, only one link exists from a client to a plurality of service servers corresponding to the target service (calling relation exists between each service server), namely, traffic of the service processing request is routed according to one link.
However, when the number of service processing requests is large, the service processing pressure of the service server of the link is large in the above manner, and the reliability of service processing is low.
Disclosure of Invention
The application provides a service processing method, a device, equipment and a storage medium, which are used for solving the problems that the service processing pressure of a service server of a link is high and the reliability of service processing is low when the number of service processing requests is high.
In a first aspect, the present application provides a service processing method, applied to a service server, where the method includes:
acquiring a service processing request corresponding to a target service through a current application;
determining the downstream application to be called by the current application according to the target service;
Determining device types of a plurality of target deployment devices where the downstream application is located;
determining the flow proportion of the downstream application in the target deployment devices according to the device type of each target deployment device;
and calling downstream applications deployed in the target deployment devices to perform service processing according to the flow proportion to obtain a service processing result.
In a second aspect, the present application provides a service processing method, applied to an operation and maintenance server, where the method includes:
displaying a route rule creating interface;
creating a routing rule in the routing rule creating interface, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to the target application in each equipment type;
determining a service server corresponding to the routing rule;
and sending the routing rule to the service server.
In a third aspect, the present application provides a service processing apparatus, including:
the acquisition module is used for acquiring a service processing request corresponding to the target service through the current application;
the first determining module is used for determining the downstream application to be called by the current application according to the target service;
a second determining module, configured to determine device types of a plurality of target deployment devices where the downstream application is located;
A third determining module, configured to determine, according to a device type of each target deployment device, a traffic proportion of the downstream application in the plurality of target deployment devices;
and the processing module is used for calling downstream applications deployed in the target deployment devices to perform service processing according to the flow proportion to obtain service processing results.
In a fourth aspect, the present application provides a service processing apparatus, including:
the display module is used for displaying the interface for creating the routing rule;
the creating module is used for creating a routing rule in the routing rule creating interface, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to each equipment type by the target application;
the determining module is used for determining a service server corresponding to the routing rule;
and the sending module is used for sending the routing rule to the service server.
In a fifth aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the business processing method according to the first or second aspect.
In a sixth aspect, the present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a computer are adapted to carry out the business processing method according to the first or second aspect.
In a seventh aspect, the present application provides a computer program product comprising a computer program for implementing the business processing method of the first or second aspect when the computer program is executed by a computer.
The service server obtains a service processing request corresponding to a target service through a current application, then determines a downstream application to be called by the current application according to the target service, determines equipment types of a plurality of target deployment devices where the downstream application is located, determines flow proportions of the downstream application in the plurality of target deployment devices according to the equipment types of each target deployment device, and calls the downstream application deployed in the plurality of target deployment devices according to the flow proportions to perform service processing to obtain a service processing result. The application can realize the flow diversion of the service processing requests according to the equipment types, and can reduce the influence on the deployment equipment and improve the reliability of service processing when the number of the service processing requests is large.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram of an application scenario to which the present application is applicable;
FIG. 2 is a schematic diagram of a call between applications of an example of the present application;
fig. 3 is a flow chart of a service processing method according to a first embodiment of the present application;
fig. 4 is a flow chart of another service processing method according to the second embodiment of the present application;
fig. 5 is a schematic diagram illustrating a service server invoking a target device in a disaster recovery equipment room to perform service processing for a service processing request according to an example of the present application;
fig. 6 is a schematic diagram illustrating another service server according to an embodiment of the present application invoking a target device in a disaster recovery equipment room to perform service processing for a service processing request;
fig. 7 is a signaling flow chart of yet another service processing method according to the third embodiment of the present application;
FIG. 8 is a schematic diagram of an interface for creating routing rules according to an example of the present application;
fig. 9 is a schematic structural diagram of a service processing device according to a fourth embodiment of the present application;
fig. 10 is a schematic structural diagram of a service processing device according to a fifth embodiment of the present application;
Fig. 11 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
It should be noted that the service processing method, device, equipment and storage medium provided by the present application may be used in a distributed field, and may also be used in any field other than the distributed field, and the application fields of the service processing method, device, equipment and storage medium provided by the present application are not limited.
With the popularization of distributed system architecture, more and more enterprises change application systems from single application to distributed application, and a plurality of systems coordinate to work, so that the complexity is increased.
At present, applications in a distributed application system can be called according to a calling sequence, and in general, a calling party can initiate a service processing request of a target service to a designated service server according to information such as an IP address of the service server, that is, only one link exists from a client to a plurality of service servers corresponding to the target service (calling relation exists between each service server), that is, traffic of the service processing request is routed according to one link.
However, when the number of service processing requests is large, the above manner has a large service processing pressure on the service server of the link, which is easy to cause service paralysis.
Therefore, the application provides a service processing method, after a service server obtains a service processing request of a target service through a current application, the service processing method can call the downstream application deployed in a plurality of deployment devices to process the service according to the flow proportion of the downstream application to be called by the current application in the plurality of deployment devices to obtain a service processing result.
For a clearer description of the present application, the following description will be made with reference to terms related to embodiments of the present application:
an application may typically be formed by a plurality of components, each representing a different functional module (which may be referred to as a service in the present application), each including a plurality of micro-service applications, e.g., a functional module such as "deposit service", "credit card service", etc., in an application, and a plurality of micro-service applications in "deposit service" to provide services to users.
Gateway application: may be an application for communication between components, i.e. a call between components, which requires a call through a gateway application.
Non-gateway applications: refers to an application in a component, namely a common micro-service application.
For easy understanding, an application scenario to which the embodiment of the present application is applied is described below in conjunction with the example of fig. 1.
Fig. 1 is a schematic diagram of an application scenario to which the present application is applicable, please refer to fig. 1, including: the operation server 101, the service server a102, the service server B103, and the service server C104 can communicate with each other via the internet, among the operation server 101, the service server a102, the service server B103, and the service server C104.
In one possible implementation manner, the current application is deployed in the service server a102, the downstream application of the current application is deployed in the service server B103, and the downstream application of the current application is deployed in the service server C104, where a call relationship exists between the current application and the downstream application, for example, the call order of the application is that the current application and the downstream application, that is, the current application calls the downstream application.
The operation and maintenance server 101 may be used to establish routing rules for the target application. The operation and maintenance server 101 may send the routing rule to the service server where the preset application is located. Taking the current application as an example, if the downstream application is the target application, the current application may be a preset application. Then the operation and maintenance server 101 may send the routing rules to the traffic server 102.
It is understood that the number of service servers a102, B103, and C104 may be plural, which are not shown in the figure.
For a clearer description of calls between applications, please refer to fig. 2, and fig. 2 illustrates the calls between applications. The current application in the component 2 may receive the service processing request initiated by the caller in the component 1, and then route the flow of the service processing request to the downstream application a in different deployment devices according to different flow proportions according to the routing rule sent by the operation and maintenance platform, in fig. 2, x% flow corresponds to one link, y% flow corresponds to another link, taking the link corresponding to x% flow in fig. 2 as an example, after the x% flow of the service processing request is routed to the downstream application a, the downstream application a routes the x% flow of the service processing request to the downstream application a of the link, which is herein for convenience of description only examples of downstream applications a and a, in practical applications, the downstream application of a may also exist in the downstream application, which is not shown in the figure.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 3 is a flow chart of a service processing method according to a first embodiment of the present application, where the method may be executed by a service server, or may be executed by a service processing device disposed in the service server, and the device may be a chip, or may be a chip module, or may be an integrated development environment (integrated development environment, IDE), or the like, and referring to fig. 3, the method includes the following steps, taking the service server as an example:
s301, acquiring a service processing request corresponding to a target service through a current application.
The service server can obtain service processing requests corresponding to the target service through the current application, and the number of the service processing requests can be one or more.
In one possible implementation, the caller that initiates the business process request may be an application in an upstream component of the component in which the current application is located.
In another possible implementation, the caller that initiates the service processing request may be an upstream application of the current application, and it is understood that the upstream application of the current application belongs to the same component as the current application.
S302, determining a downstream application to be called by the current application according to the target service.
After the service processing request is obtained, the service server can determine the downstream application to be invoked by the current application according to the target service.
For example, the service server may obtain application information of a plurality of applications of the target service from a registry database, where the application information may include an identification of the applications and an identification of downstream applications of each application, and the registry database includes the plurality of applications of the plurality of services. After the service server obtains the application information of the multiple applications of the target service, the downstream application to be called by the current application can be determined in the multiple applications.
S303, determining device types of a plurality of target deployment devices where downstream applications are located.
After determining the downstream application to be invoked by the current application, the service server may determine device types of a plurality of target deployment devices where the downstream application is located.
In the embodiment of the application, one server is the minimum unit of application deployment, one physical unit comprises a plurality of servers, and one machine room can comprise a plurality of physical units.
The device type may be determined according to a preset tag in device information of the target deployment device, where the device types of the deployment devices including the same preset tag in the device information are the same, for example, the device types of the target deployment devices including tagA in the device information are the same, that is, the same type of device, and the device types of the target deployment devices including tagB in the device information are the same.
S304, determining the flow proportion of the downstream application in the plurality of target deployment devices according to the device type of each target deployment device.
In the embodiment of the application, the flow ratios corresponding to the target deployment devices of different device types are different, and after the device types of the plurality of target deployment devices where the downstream application is located are determined, the service server can determine the flow ratio of the downstream application in the plurality of target deployment devices according to the device type of each target deployment device.
S305, calling downstream applications deployed in a plurality of target deployment devices to conduct business processing according to the flow proportion, and obtaining business processing results.
The service server can call downstream applications deployed in the multiple target deployment devices to perform service processing according to the flow proportion, and a service processing result corresponding to the service processing request is obtained.
For example, the service server may route the traffic of the service processing request to the target deployment device including tagA in the device information according to the x% ratio, and may route the traffic of the service processing request to the target deployment device including tagB in the device information according to the y% ratio. Where the sum of x% and y% is 100%, for example, x may be 20 and y may be 80.
In this embodiment, the service server obtains a service processing request corresponding to a target service through a current application, then determines a downstream application to be invoked by the current application according to the target service, determines device types of a plurality of target deployment devices where the downstream application is located, determines a flow ratio of the downstream application in the plurality of target deployment devices according to the device type of each target deployment device, and invokes the downstream application deployed in the plurality of target deployment devices according to the flow ratio to perform service processing, thereby obtaining a service processing result. The application can realize the flow diversion of the service processing requests according to the equipment types, and can reduce the influence on the deployment equipment and improve the reliability of service processing when the number of the service processing requests is large.
Next, another service processing method provided by the present application is described through a second embodiment.
Fig. 4 is a flow chart of another service processing method provided in the second embodiment of the present application, where the method may be executed by a service server, or may be executed by a distributing device of a distributed application disposed in the service server, where the device may be a chip, or may be a chip module, or may be an IDE, and in the following, taking the service server as an example, referring to fig. 4, the method includes the following steps:
s401, acquiring a service processing request corresponding to a target service through a current application.
S402, determining a downstream application to be called by the current application according to the target service.
The specific description in S401 and S402 may refer to the above embodiments, and will not be repeated here.
S403, determining device types of a plurality of target deployment devices where the downstream application is located.
In one possible implementation, the service server may obtain device types for a plurality of deployed devices of the downstream application from a registry database. Specifically, the service server obtains device information of a plurality of deployment devices of the downstream application in a plurality of physical units from a registry database, and each device information can include the device type. For example, the device type may be determined by a preset tag, or may be determined in other manners. The service server then determines a device type for the plurality of target deployment devices from the device types for the plurality of deployment devices.
In one possible implementation, the service server may obtain device information of a plurality of deployment devices in the plurality of physical units of the downstream application from the registry database, then determine a target physical unit from the plurality of physical units according to the identification of the target physical unit in the target routing rule, and then determine the deployment device in the target physical unit as the target deployment device.
S404, at least one routing rule is obtained, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to the downstream application in each equipment type.
The service server may obtain at least one routing rule.
In one possible implementation, the service server may store at least one routing rule, the at least one routing rule being sent by the operation and maintenance server. The routing rule includes a plurality of device types and flow proportions corresponding to the downstream application in each device type, and the plurality of device types can be represented by different preset labels.
S405, determining a target routing rule in at least one routing rule.
The traffic server stores at least one routing rule from which the traffic server can determine the target routing rule.
In one possible implementation, the service server may determine the priority of at least one routing rule, in particular, each routing rule includes a value of priority, e.g., the value of priority is represented by a number, the smaller the value, the higher the priority. The traffic server may then determine the highest priority routing rule of the at least one routing rule as the determination target routing rule.
S406, according to the equipment type of each target deployment equipment, determining the flow proportion of the downstream application in the plurality of target deployment equipment in the target routing rule.
After determining the target routing rule, the service server may determine, based on the multiple device types in the target routing rule and the traffic proportion of the downstream application corresponding to each device type, the traffic proportion of the downstream application corresponding to the multiple target deployment devices according to the device type of each target deployment device.
For example, the target routing rule includes a device type 1 and a device type 2, where the traffic proportion corresponding to the device type 1 is 20%, the traffic proportion corresponding to the device type 2 is 80%, the number of target deployment devices is, for example, 10 (a, b, c, d, e, f, g, i, j, k), where 4 (d, e, f, g) devices are device types 1,6 (a, b, c, i, j, k) devices are device types 2, and then the service server may determine that the traffic proportion corresponding to the 4 (d, e, f, g) target deployment devices is 20%, and the traffic proportion corresponding to the 6 (a, b, c, i, j, k) target deployment devices is 80%.
S407, calling downstream applications deployed in the multiple target deployment devices to perform service processing according to the flow proportion, and obtaining a service processing result.
After the flow ratio is determined, the service server can call downstream applications deployed in the multiple target deployment devices to perform service processing, so as to obtain a service processing result.
Taking the example in S406 as an example, the service server may route 20% of the traffic of the service processing request to the 4 target deployment devices (d, e, f, g), while routing 80% of the traffic of the service processing request to the 6 target deployment devices (a, b, c, i, j, k).
In one possible implementation manner, if a failure occurs in a downstream application deployed by a first deployment device in the multiple target deployment devices during service processing, the service server may further call a target device in the disaster recovery equipment room to perform service processing for a service processing request, where each device in the disaster recovery equipment room includes at least one routing rule, and the configuration of the devices in the disaster recovery equipment room is the same as that of the multiple target deployment devices.
Fig. 5 is a schematic diagram of a service server invoking target equipment of a disaster recovery equipment room for performing service processing on a service processing request, and fig. 6 is a schematic diagram of another service server invoking target equipment of the disaster recovery equipment room for performing service processing on the service processing request, where equipment in the disaster recovery equipment room is identical to configuration of a plurality of target deployment equipment, if a downstream application deployed by a first deployment equipment fails, the service server may route traffic of the service processing request to an application of the target equipment of the disaster recovery equipment room, where the deployment of the target equipment in the disaster recovery equipment room is identical to that of the first deployment equipment in the room where the first deployment equipment is located, and the application deployed by the target equipment is identical to that deployed by the first deployment equipment.
As can be seen from the figure, the downstream application in fig. 5 is a gateway application, and then the traffic of the service processing request can be directly routed to the application in the target device in the disaster recovery equipment room. In fig. 6, if the downstream application is a non-gateway application, the service server needs to route the traffic of the service processing request to the gateway application in the disaster recovery equipment room, and then the gateway application routes the traffic of the service processing request to the application of the target device.
In this embodiment, the service server obtains a service processing request corresponding to a target service through a current application, then determines a downstream application to be invoked by the current application according to the target service, and determines device types of a plurality of target deployment devices where the downstream application is located. And then at least one routing rule is obtained, a target routing rule is determined in the at least one routing rule, the flow proportion of the downstream application in the plurality of target deployment devices is determined in the target routing rule according to the device type of each target deployment device, and then the downstream application deployed in the plurality of target deployment devices is called for service processing according to the flow proportion, so that a service processing result is obtained. The application can realize the flow diversion of the service processing requests according to the equipment types, and can reduce the influence on the deployment equipment and improve the reliability of service processing when the number of the service processing requests is large.
Next, another service processing method provided in the third embodiment of the present application is described. The interaction between the operation server and the service server is specifically described.
Fig. 7 is a signaling flow chart of another service processing method according to the third embodiment of the present application, and referring to fig. 7, the method includes the following steps:
s701, the operation and maintenance server displays a route rule creating interface.
The operation and maintenance manager can click on the newly built routing rule on the corresponding interface and jump to the page for creating the routing rule.
S702, the operation and maintenance server creates a routing rule in a routing rule creation interface.
And the operation and maintenance manager creates a routing rule through the operation and maintenance server in a routing rule creating interface, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to each equipment type by the target application.
S703, the operation server determines a service server corresponding to the routing rule.
In one possible implementation manner, the routing rule may further include a caller parameter, that is, the operation and maintenance server may determine, according to the caller parameter, a preset application for calling the target application, and then determine, as a service server corresponding to the routing rule, a deployment device in which the preset application is located, where the caller parameter includes an application type of the preset application.
If the type of the target application is a gateway application, the preset application is any one of an upstream application of the target application, an application in an upstream component of a component where the target application is located, and a designated application. That is, if the type of the target application is a gateway application, the routing rule may be sent to the deployment device where any one of the upstream application of the target application, the application in the upstream component of the component where the target application is located, and the designated application is located.
If the type of the target application is a non-gateway application, the preset application is an upstream application of the target application or a designated application. That is, if the type of the target application is a non-gateway application, the routing rule may be sent to the deployment device where any one of the upstream application of the target application and the designated application is located.
Specifically, the upstream application of the target application, the application in the upstream component of the component where the target application is located, and the designated application may be determined by a preset tag, where the upstream application of the target application, the application in the upstream component of the component where the target application is located, or the deployed device where the designated application is located is a device in the designated physical unit.
As shown in fig. 8, fig. 8 is an interface schematic diagram for creating a routing rule, where the application types of the preset application in the caller parameters may be components, applications or custom applications, and each application type includes a matching relationship, and a tag value, where the matching relationship is any one of equal, unequal, including and not including.
For the option that the application type is a component, the matching relationship may be equal to, and the tag value may be the name of the component.
For an option where the application type is an application, the matching relationship may be equal to, and the tag value may be the name of the application.
For the option that the application type is the custom application, the matching relationship may be any one of equal, unequal, including and not including, and the tag value may be a preset tag value, for example, tag1, that is, the application that is equal to, unequal, including or not including tag1 in the application information is the custom application.
For example, the application type in the routing rule is a component, and since the component is an upstream component of the component where the current application is located, the tag value may set the name 1 of the upstream component, and the matching relationship is equal, then all applications in the upstream component with the name 1 are preset.
For another example, the application type in the routing rule is an application, and since the application is an upstream application of the current application, the tag value may set the name 2 of the upstream application, and the matching relationship is equal to that, then the preset application is an application with the application name of name 2.
For another example, the application type in the routing rule is a custom application, and since the application is a specified application, the tag value may be a preset tag value, for example, tag1, and the matching relationship is unequal, for example, if the application information of a certain application includes tag2 and tag3, and both tag2 and tag3 are unequal to tag1, that is, tag1 does not exist in the application information, the application may be determined to be a preset application.
In fig. 8, the routing rule may also include a rule name, the availability status (available or unavailable) of the rule, and priority.
In one possible implementation, the routing rule may further include application information of the target application, where the application information includes a name of a component where the target application is located, an application name of the target application, and an identifier of a physical unit where the target application is located. The destination parameter in fig. 8 is application information of the target application, and the device type of the deployed device may be determined according to a preset tag in the device information of the deployed device where the target application is located.
Taking fig. 8 as an example, if the preset tag in the device information of the deployment device where the target application is located is tagA, the flow rate corresponding to the device is 80%, and if the preset tag in the device information of the deployment device where the target application is located is tagB, the flow rate corresponding to the device is 20%. The specific reference to the second embodiment may be referred to for the target application according to the flow ratio, which is not described herein again, and the downstream application in the second embodiment may be understood as the target application in the present embodiment.
It can be understood that when the operation and maintenance personnel creates the routing rule through the operation and maintenance server, the corresponding flow label can be set according to the performance, the computing capability and the like of the equipment where the target application is located, so that the equipment with better performance can process more service processing requests. Correspondingly, the tag value of the corresponding preset tag is also added to the equipment information of the equipment to which the target application belongs.
S704, the operation and maintenance server sends the routing rule to the service server corresponding to the routing rule.
And S705, the operation and maintenance server sends the routing rule to a server in the disaster recovery equipment room.
The operation and maintenance server can send the routing rule to the equipment in the disaster recovery equipment room (namely, all servers in the disaster recovery equipment room), wherein the disaster recovery equipment room is used as a standby equipment room when the deployment equipment of the target application fails in service processing, the equipment of the disaster recovery equipment room and the deployment equipment of the target application are identical in configuration, and it can be understood that the equipment mentioned in the application can be regarded as a server.
In this embodiment, the operation and maintenance server may create a routing rule, then determine a service server corresponding to the routing rule, and send the routing rule to the service server corresponding to the routing rule, so that the service server may perform call processing applied to the service processing request according to the routing rule. The application can realize the flow diversion of the service processing requests according to the equipment types, and can reduce the influence on the deployment equipment and improve the reliability of service processing when the number of the service processing requests is large.
Fig. 9 is a schematic structural diagram of a service processing device according to a fourth embodiment of the present application. Referring to fig. 9, the apparatus 90 includes: an acquisition module 901, a first determination module 902, a second determination module 903, a third determination module 904, and a processing module 905.
The acquiring module 901 is configured to acquire, by using a current application, a service processing request corresponding to a target service.
A first determining module 902, configured to determine, according to the target service, a downstream application to be invoked by the current application.
A second determining module 903, configured to determine device types of a plurality of target deployment devices where the downstream application is located.
A third determining module 904, configured to determine, according to the device type of each target deployment device, a traffic proportion of the downstream application in the multiple target deployment devices.
And the processing module 905 is used for calling downstream applications deployed in the multiple target deployment devices to perform service processing according to the flow proportion, so as to obtain a service processing result.
In one possible implementation, the third determining module 904 is specifically configured to:
at least one routing rule is obtained, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to the downstream application in each equipment type.
Among the at least one routing rule, a target routing rule is determined.
According to the device type of each target deployment device, in the target routing rule, the traffic proportion of the downstream application in a plurality of target deployment devices is determined.
In one possible implementation, the third determining module 904 is specifically configured to:
the priority of each routing rule is determined.
And determining the routing rule with the highest priority among the at least one routing rule as a target routing rule.
In one possible implementation, the second determining module 903 is specifically configured to:
the device types of the plurality of deployed devices of the downstream application are obtained from the registry database.
From among the device types of the plurality of deployed devices, a device type of the plurality of target deployed devices is determined.
In one possible implementation, the apparatus 90 further includes a calling module, where the calling module is specifically configured to:
And calling target equipment of the disaster recovery equipment room to perform service processing on the service processing request, wherein each equipment of the disaster recovery equipment room comprises at least one routing rule, and the equipment in the disaster recovery equipment room and the plurality of target deployment equipment are configured identically.
The device of the present embodiment may be used to execute the technical solutions of the foregoing method embodiments, and the specific implementation manner and the technical effects are similar, and are not repeated herein.
Fig. 10 is a schematic structural diagram of a service processing device according to a fifth embodiment of the present application. Referring to fig. 10, the apparatus 100 includes: a display module 1001, a creation module 1002, a determination module 1003, and a transmission module 1004.
A display module 1001, configured to display a create routing rule interface.
A creating module 1002, configured to create a routing rule in a routing rule creating interface, where the routing rule includes a plurality of device types and a traffic proportion corresponding to each device type by a target application.
A determining module 1003, configured to determine a service server corresponding to the routing rule.
A sending module 1004, configured to send the routing rule to the service server.
In one possible implementation, the determining module 1003 is specifically configured to:
and determining a preset application for calling the target application according to the calling party parameters, wherein the calling party parameters comprise the application type of the preset application.
And determining the deployment equipment where the preset application is located as a service server corresponding to the routing rule.
In one possible implementation manner, if the type of the target application is a gateway application, the preset application is any one of an upstream application of the target application, an application in an upstream component of a component where the target application is located, and a designated application.
If the type of the target application is a non-gateway application, the preset application is an upstream application of the target application or a designated application.
In one possible implementation, the sending module 1004 is further configured to:
and sending the routing rule to equipment in the disaster recovery equipment room, wherein the disaster recovery equipment room is used as a standby equipment room when the deployment equipment of the target application fails in service processing, and the equipment of the disaster recovery equipment room and the deployment equipment of the target application are identical in configuration.
Fig. 11 is a schematic structural diagram of an electronic device according to a sixth embodiment of the present application, and as shown in fig. 11, an electronic device 110 may include: at least one processor 1101 and a memory 1102.
A memory 1102 for storing programs. In particular, the program may include program code including computer-executable instructions.
The Memory 1102 may include random access Memory (Random Access Memory, RAM) and may also include Non-volatile Memory (Non-volatile Memory), such as at least one disk Memory.
The processor 1101 is configured to execute computer-executable instructions stored in the memory 1102 to implement the methods described in the foregoing method embodiments. The processor 1101 may be a central processing unit (Central Processing Unit, CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application.
Optionally, the electronic device 110 may further include: communication interface 1103. In a specific implementation, if the communication interface 1103, the memory 1102, and the processor 1101 are implemented independently, the communication interface 1103, the memory 1102, and the processor 1101 may be connected to each other and perform communication with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. Buses may be divided into address buses, data buses, control buses, etc., but do not represent only one bus or one type of bus.
Alternatively, in a specific implementation, if the communication interface 1103, the memory 1102, and the processor 1101 are implemented integrally on a single chip, the communication interface 1103, the memory 1102, and the processor 1101 may complete communication through internal interfaces.
The electronic device 110 may be a chip, a chip module, an IDE, a server, etc.
The electronic device of the present embodiment may be used to execute the technical solutions of the foregoing method embodiments, and the specific implementation manner and the technical effects are similar, and are not repeated herein.
A seventh embodiment of the present application provides a computer-readable storage medium, which may include: various media capable of storing computer execution instructions, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a RAM, a magnetic disk, or an optical disc, etc., specifically, the computer execution instructions are stored in the computer readable storage medium, and when the computer execution instructions are executed by a computer, the technical scheme shown in the foregoing method embodiment is executed, and specific implementation manner and technical effects are similar and are not repeated herein.
An eighth embodiment of the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a computer, the technical solution shown in the foregoing method embodiment is executed, and the specific implementation manner and the technical effect are similar, and are not repeated herein.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (13)
1. A service processing method, applied to a service server, the method comprising:
acquiring a service processing request corresponding to a target service through a current application;
determining the downstream application to be called by the current application according to the target service;
determining device types of a plurality of target deployment devices where the downstream application is located;
determining the flow proportion of the downstream application in the target deployment devices according to the device type of each target deployment device;
and calling downstream applications deployed in the target deployment devices to perform service processing according to the flow proportion to obtain a service processing result.
2. The method of claim 1, wherein the determining the traffic proportion of the downstream application in the plurality of target deployment devices according to the device type of each target deployment device comprises:
acquiring at least one routing rule, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to the downstream application in each equipment type;
Determining a target routing rule in the at least one routing rule;
and determining the flow proportion of the downstream application in the target deployment devices in the target routing rule according to the device type of each target deployment device.
3. The method of claim 2, wherein said determining a target routing rule among at least one routing rule comprises:
determining the priority of each routing rule;
and determining the routing rule with the highest priority among the at least one routing rule as the target routing rule.
4. A method according to claim 2 or 3, wherein said determining the device type of the plurality of deployed devices in which the downstream application is located comprises:
acquiring device types of a plurality of deployment devices of the downstream application from a registry database;
and determining the device types of the target deployment devices from the device types of the deployment devices.
5. The method of claim 4, wherein a failure occurs if a downstream application deployed by a first deployment device of the plurality of target deployment devices performs traffic processing;
the method further comprises the steps of:
And calling target equipment of the disaster recovery equipment room to perform service processing on the service processing request, wherein each equipment of the disaster recovery equipment room comprises at least one routing rule, and the equipment in the disaster recovery equipment room and the plurality of target deployment equipment are identical in configuration.
6. A service processing method, applied to an operation server, the method comprising:
displaying a route rule creating interface;
creating a routing rule in the routing rule creating interface, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to the target application in each equipment type;
determining a service server corresponding to the routing rule;
and sending the routing rule to the service server.
7. The method of claim 6, wherein the routing rule further comprises a caller parameter;
the determining the service server corresponding to the routing rule comprises the following steps:
determining a preset application for calling the target application according to the calling party parameters, wherein the calling party parameters comprise the application type of the preset application;
and determining the deployment equipment where the preset application is located as a service server corresponding to the routing rule.
8. The method of claim 7, wherein the step of determining the position of the probe is performed,
if the type of the target application is a gateway application, the preset application is any one of an upstream application of the target application, an application in an upstream component of a component where the target application is located, and a designated application;
and if the type of the target application is a non-gateway application, the preset application is an upstream application or a designated application of the target application.
9. The method according to any one of claims 6-8, further comprising:
and sending the routing rule to equipment in a disaster recovery equipment room, wherein the disaster recovery equipment room is used as a standby equipment room when the deployment equipment of the target application fails in service processing, and the equipment of the disaster recovery equipment room and the deployment equipment of the target application are identical in configuration.
10. A service processing apparatus, comprising:
the acquisition module is used for acquiring a service processing request corresponding to the target service through the current application;
the first determining module is used for determining the downstream application to be called by the current application according to the target service;
a second determining module, configured to determine device types of a plurality of target deployment devices where the downstream application is located;
A third determining module, configured to determine, according to a device type of each target deployment device, a traffic proportion of the downstream application in the plurality of target deployment devices;
and the processing module is used for calling downstream applications deployed in the target deployment devices to perform service processing according to the flow proportion to obtain service processing results.
11. A service processing apparatus, comprising:
the display module is used for displaying the interface for creating the routing rule;
the creating module is used for creating a routing rule in the routing rule creating interface, wherein the routing rule comprises a plurality of equipment types and flow proportions corresponding to each equipment type by the target application;
the determining module is used for determining a service server corresponding to the routing rule;
and the sending module is used for sending the routing rule to the service server.
12. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the business processing method of any one of claims 1-5 or the business processing method of any one of claims 6-9.
13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to implement the business processing method of any of claims 1-5 or the business processing method of any of claims 6-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310630102.0A CN116633856A (en) | 2023-05-30 | 2023-05-30 | Service processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310630102.0A CN116633856A (en) | 2023-05-30 | 2023-05-30 | Service processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116633856A true CN116633856A (en) | 2023-08-22 |
Family
ID=87636396
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310630102.0A Pending CN116633856A (en) | 2023-05-30 | 2023-05-30 | Service processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116633856A (en) |
-
2023
- 2023-05-30 CN CN202310630102.0A patent/CN116633856A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN109819023B (en) | Distributed transaction processing method and related product | |
| CN105488125A (en) | Page access method and apparatus | |
| CN110990110A (en) | Virtual machine creation method and device based on Sriov network card | |
| CN108664343B (en) | State calling method and device for micro-service | |
| CN113312675A (en) | Attribute checking method and device, electronic equipment and storage medium | |
| CN112783629A (en) | Service calling method and device, electronic equipment and storage medium | |
| CN112804099A (en) | Parameter batch configuration method and device, computer equipment and readable storage medium | |
| CN116633856A (en) | Service processing method, device, equipment and storage medium | |
| CN109614242B (en) | Computing capacity sharing method, device, equipment and medium | |
| CN111475226B (en) | Electronic device, micro-service calling method, and computer-readable storage medium | |
| CN115037653A (en) | Service flow monitoring method and device, electronic equipment and storage medium | |
| CN116647603A (en) | Distribution method, device, equipment and storage medium for distributed application | |
| CN111858079B (en) | Distributed lock migration method and device, electronic equipment and storage medium | |
| CN112328598B (en) | ID generation method, ID generation device, electronic equipment and storage medium | |
| CN113590352A (en) | Data calling method, device, equipment and readable storage medium | |
| CN110753082B (en) | Service calling method and terminal equipment | |
| CN114528074A (en) | Dynamic baffle implementation method, system and equipment based on micro-service architecture | |
| CN108920277B (en) | Service execution system, method and device and service isolation system | |
| KR20220007468A (en) | Transaction processing method of terminal connected to Hyperledger Fabric system through network | |
| CN116643787A (en) | Distribution method, device, equipment and storage medium for distributed application | |
| CN112261072A (en) | Service calling method, device, equipment and storage medium | |
| CN111553658B (en) | Platform user registration method and device, electronic equipment and storage medium | |
| CN117171235B (en) | Data analysis method based on industrial identification and related equipment | |
| CN107862480B (en) | Service management method, release management device, medium, and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |