CN115529346A

CN115529346A - Service changing method, device, equipment and storage medium

Info

Publication number: CN115529346A
Application number: CN202211110492.0A
Authority: CN
Inventors: 甄真; 徐志明
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-09-13
Filing date: 2022-09-13
Publication date: 2022-12-27

Abstract

The disclosure provides a service change method, a service change device, service change equipment and a storage medium, and relates to the technical field of computers, in particular to the technical field of cloud computing and cloud service. According to the scheme, when the service is changed, the service can be changed for the first time, so that part of instances in the service are changed, and the other part of the instances in the service are not changed. And when part of the instances are changed, only part of the access traffic of the user flows to the changed instances, the traffic flowing to the changed instances is detected to obtain a changed state evaluation index, so that whether the changed instances are abnormal or not is detected, and when no abnormality is detected, all instances in the service are changed into the changed instances, so that the service change is completed. Therefore, the stability of the service change can be improved, and the influence on the normal access of the user when the service is changed can be reduced.

Description

Service changing method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, particularly to the field of cloud computing and cloud service technologies, and in particular, to a service change method, apparatus, device, and storage medium.

Background

With the continuous development of services, the functions provided by applications become more complex and diversified, and therefore, the application versions are upgraded more and more frequently. The application version upgrade is accompanied by a change of the service corresponding to the application. The change of the service may include at least one of a code change and a data change. The functionality provided by an application may be implemented based on a plurality of services, each of which may have a plurality of instances corresponding to the service.

Therefore, when a change is made to a certain service, if all instances of the service are directly changed at the same time, normal access by a user is affected during the change, and when an abnormality occurs in the change, stability after the change of the service is affected.

Disclosure of Invention

The present disclosure provides a service change method, apparatus, device, and storage medium, which are capable of changing a part of instances when a service is changed, and then completely changing the service when it is determined that the changed instances are not abnormal, thereby improving stability when the service is changed, and reducing an influence on normal access of a user when the service is changed.

According to a first aspect of the present disclosure, there is provided a service change method, including:

changing the instances of the service to be changed to obtain at least one changed instance and at least one unchanged instance; marking a corresponding detection identifier for the flow flowing to the corresponding example according to the detection identifier of each example of the service to be changed in the example list; the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is a changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is an unchanged instance detection identifier; determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier; determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index; and changing the instances of the service to be changed so that all the instances in the service to be changed are changed instances.

According to a second aspect of the present disclosure, there is provided a service change apparatus including: the first change module is used for changing the instances of the service to be changed to obtain at least one changed instance and at least one unchanged instance; the anomaly detection module is used for marking a corresponding detection identifier for the flow which flows to the corresponding example according to the detection identifier of each example of the service to be changed in the example list; the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is a changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is an unchanged instance detection identifier; determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier; determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index; and the second changing module is used for changing the instances of the service to be changed so as to enable all the instances in the service to be changed.

According to a third aspect of the present disclosure, there is provided an electronic device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as provided in the first aspect.

According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method provided according to the first aspect.

According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the method provided according to the first aspect.

The method and the device can firstly change the service for the first time when the service is changed, so that part of the instances in the service are changed, and the other part of the instances in the service are not changed. Therefore, in the process of changing part of the instances, although the changed instances interrupt the traffic access, the other part of the unchanged instances are not interrupted, so that the access traffic of the user can be borne by the unchanged instances, and the influence on the normal access of the user when the service is changed is reduced. And when part of the instances are changed, only part of the access traffic of the users flows to the changed instances, so that only part of the users are affected when the instances are changed abnormally, and the influence of service change on the user access is reduced. In addition, only part of the instances in the service are changed during the initial change, so that the method can detect whether the changed instances are abnormal or not by detecting the flow of the changed instances to obtain the change state evaluation index, and change all the instances in the service to changed instances when no abnormality is detected, thereby completing the change of the service. Therefore, when the service is abnormal, the abnormality can be timely found and the service change is stopped, so that the influence on the user when the service change is abnormal is reduced.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a schematic flow chart of a service change method according to an embodiment of the disclosure;

fig. 2 is a second schematic flow chart of a service change method according to an embodiment of the disclosure;

fig. 3 is a third schematic flow chart of a service change method according to the embodiment of the disclosure;

fig. 4 is a fourth schematic flowchart of a service change method according to an embodiment of the disclosure;

fig. 5 is a schematic composition diagram of a service change apparatus according to an embodiment of the disclosure;

FIG. 6 illustrates a schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of embodiments of the present disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The service changing method and the service changing device provided by the disclosure are suitable for changing the service. The service changing method provided by the present disclosure may be executed by a service changing apparatus, and the service changing apparatus may be implemented by software and/or hardware, and is specifically configured in an electronic device, and the electronic device may be a device such as a server, a computer, a single chip or other computing devices, which is not limited herein.

First, a service change method provided by the present disclosure will be described in detail below.

To this end, the present disclosure provides a service change method, including: changing the instances of the service to be changed to obtain at least one changed instance and at least one unchanged instance; marking a corresponding detection identifier for the flow which flows to the corresponding example according to the detection identifier of each example of the service to be changed in the example list; the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is a changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is an unchanged instance detection identifier; determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier; determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index; and changing the instances of the service to be changed, so that all the instances in the service to be changed are changed instances.

The method and the device can firstly change the service for the first time when the service is changed, so that part of the instances in the service are changed, and the other part of the instances in the service are not changed. Therefore, in the process of changing a part of instances, although the changed instances interrupt the traffic access, the other part of the unchanged instances are not interrupted, so that the access traffic of the user can be accepted by the unchanged instances, thereby reducing the influence on the normal access of the user when the service is changed. And when part of the instances are changed, only part of the access traffic of the users flows to the changed instances, so that only part of the users are affected when the instances are changed abnormally, and the influence of service change on the user access is reduced. In addition, because only part of the instances in the service are changed during the initial change, the method can detect whether the changed instances are abnormal or not by detecting the flow of the instances with changed flow to obtain the change state evaluation index, and change all the instances in the service to the changed instances when no abnormality is detected, thereby completing the change of the service. Therefore, when the service is abnormal, the abnormality can be timely found and the service change is stopped, so that the influence on the user when the service change is abnormal is reduced.

Fig. 1 is a flowchart illustrating a service change method according to an embodiment of the present disclosure. As shown in fig. 1, the method may include the following S101-S105.

S101, changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance.

It should be noted that each service may have multiple instances corresponding to the service. An instance may be a plurality of resource allocation units having the same configuration and used to support a grouping function. Multiple instances corresponding to the same service may be isomorphic. Multiple instances corresponding to the same service may be used to assume access traffic.

The method for changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance may be to change the specified instance according to a preset instruction, or to create the changed instance according to a certain preset rule, or to change part of the instances after creating the instance, and is not limited herein as long as at least one changed instance and at least one unchanged instance can be in the service to be changed.

S102, marking corresponding detection identifications for the flow of the corresponding examples according to the detection identifications of the examples of the service to be changed in the example list.

The detection mark is a changed instance detection mark or an unchanged instance detection mark, the detection mark of the changed instance in each instance is a changed instance detection mark, and the detection mark of the unchanged instance in each instance is an unchanged instance detection mark.

It should be noted that the instance list may be used to store access addresses of instances corresponding to the service to be changed and detection identifiers corresponding to the instances. Thereby facilitating marking of the changed instance.

In this step, the traffic flowing to the corresponding instance is marked, which may be that the change instance detection flag is marked on the traffic of the instance whose detection flag is the change instance detection flag in the flow direction instance list. And marking the unchanged instance detection identifier on the traffic of the instance which is detected and identified as the unchanged instance detection identifier in the flow instance list.

S103, determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier.

For example, the change state evaluation index may include traffic processing performance index parameters such as a success rate, a failure rate, a response time, and the like, when the corresponding traffic (i.e., the traffic marked with the change instance detection identifier) is processed by the corresponding instance (i.e., the changed instance). Therefore, the traffic processing performance of the changed instance is evaluated according to the change state evaluation index, and whether the changed instance is abnormal or not is determined.

And S104, determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index.

For example, whether a changed instance of the service to be changed is abnormal may be determined based on a preset reference state evaluation index. For example, a reference state evaluation index is set based on an average state evaluation index in a case where the instance is normal, and when the state evaluation index is a failure rate or a response time, and the changed state evaluation index is greater than the reference state evaluation index, it is determined that the changed instance has an abnormality, and when the changed state evaluation index is smaller than the reference state evaluation index, it is determined that the changed instance has no abnormality. When the changed state evaluation index is equal to the reference state evaluation index, the abnormal state evaluation index can be set according to actual needs to determine that the changed example has an abnormal state or determine that the changed example has no abnormal state.

As another example, it may also be determined whether a changed instance in the service to be changed is abnormal based on the unchanged state evaluation index.

For example, before S104, an unchanged state evaluation index corresponding to the traffic marked with the unchanged instance detection identifier may also be determined. Then, when the modified state evaluation index and the unmodified state evaluation index are close (e.g., the absolute value of the difference between the two is smaller than a preset threshold value, etc.), it is determined that the modified instance has no abnormality.

Alternatively, whether the changed instance is abnormal may be determined according to the magnitude between the changed state evaluation index and the unchanged state evaluation index based on the specific parameter of the state evaluation index. For example, when the state evaluation index is a failure rate or a response time, and the changed state evaluation index is greater than the unchanged state evaluation index, it is determined that the changed instance has an abnormality, and when the changed state evaluation index is less than the unchanged state evaluation index, it is determined that the changed instance has no abnormality. When the modified state evaluation index is equal to the unmodified state evaluation index, the modified instance is determined to have an abnormality or the modified instance is determined to have no abnormality according to actual needs.

And S105, changing the instances of the service to be changed, so that all the instances in the service to be changed are changed instances.

The example of the service to be changed is changed, and the unchanged example may be changed or deleted in a manner that each example in the service to be changed is a changed example, which is not limited herein.

As an example, in the above method, S101 and S105 may be performed by a change controller. S102 may be performed by a Remote Procedure Call (RPC) module. The RPC module may also shunt traffic received by the service to be changed, so that the traffic flows to each instance of the service to be changed. The method may further maintain the instance list through a naming service (namegservice). The traffic flowing to each instance and the detection identification of each traffic marker are recorded and saved by a trace (trace) system. Then, information of each traffic is acquired from the tracking system through the evaluation service (metrics-server) and S103 and S104 are performed. Of course, the foregoing is merely an example, and in practical applications, the method steps may also be executed by other modules or units, and the steps may also be combined in other combinations, which is not limited herein.

Optionally, when the instance of the service to be changed is changed to obtain at least one changed instance and at least one unchanged instance, the pre-specified instance may be changed, and the other instances may not be changed.

For example, the detection identifier of each instance in the instance list may be preset (may be obtained in advance from the PaaS system, or may be preset by adding, and is not limited here), where the detection identifier of at least one instance of the service to be changed in the instance list is a changed instance detection identifier, and the detection identifier of at least one instance is an unchanged instance detection identifier.

At this time, changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance may include:

and changing the example of which the detection identifier in the service to be changed is the change example detection identifier according to the example list.

Therefore, the instance with the change instance detection identifier identified in the instance list can be changed first, so that the instance of the service to be changed can be changed conveniently, and at least one changed instance and at least one unchanged instance can be obtained. Moreover, since the changed instance is the instance with the changed instance detection identifier identified in the instance list, the instance list does not need to be updated, and the subsequent marking of the traffic flowing to the corresponding instance can be facilitated directly according to the detection identifier in the instance list, so that the traffic finally marked with the changed instance detection identifier is the traffic flowing to the changed instance.

Based on the above method, optionally, changing the instance of the service to be changed so that each instance in the service to be changed is a changed instance, may include:

and changing the unchanged examples in the service to be changed.

For example, when each unchanged instance in the service to be changed is changed, each unchanged instance may be changed in sequence, so as to reduce the influence on the normal access of the user traffic when the corresponding instance is changed each time. The method can also change all the unchanged examples at the same time or change a plurality of unchanged examples for a plurality of times, thereby improving the efficiency of changing the unchanged examples and improving the efficiency of final service change.

By adopting the method, the unchanged examples in the service to be changed can be changed conveniently when the changed examples are determined to be abnormal, so that all the examples of the service to be changed are changed. In addition, because some existing instances are changed, normal access of user traffic can not be influenced when unchanged instances are changed.

Optionally, the change of the instance of the service to be changed can be realized by creating a new instance of the service to be changed, so as to obtain at least one changed instance and at least one unchanged instance.

For example, the instance list in the method shown in fig. 1 may include original instances corresponding to services to be changed before the services are changed, and the detection identifier of each original instance is preset as an unchanged instance detection identifier (the detection identifier of each original instance may be set in the PaaS system and then obtained from the PaaS system, or the detection identifier of each original instance may be directly preset in the instance list, which is not limited herein).

At this time, changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance, as shown in fig. 2, may include:

s201, creating new instances corresponding to the number of the original instances, wherein the new instances are changed relative to the original instances.

S202, adding the new instances into the instance list, and marking the detection identification of each new instance as a change instance detection identification.

Therefore, the changed examples corresponding to the original examples of the service to be changed can be quickly obtained in a mode of creating new examples corresponding to the original examples. Thus, the traffic can be received stably by the original instance that has not been changed, and the traffic can be received by the new instance that has been created, so that the abnormality detection of the changed instance can be performed later. In addition, because the changed examples corresponding to the original example number are created at one time, the original examples can be directly deleted subsequently to complete the change of the service to be changed, so that the service change efficiency is improved, and the carrying capacity of the service to the user traffic is not applied.

and deleting each original example in the service to be changed, and deleting each original example and the corresponding detection identifier in the example list.

Therefore, when the changed examples are determined to be abnormal, the original examples can be directly deleted to efficiently and quickly complete the change of the service to be changed, so that the service change efficiency is improved.

Optionally, when the instance of the service to be changed is changed by creating a new instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance, the created new instance may also be an unchanged instance.

For example, the instance list in the method described in fig. 1 may include original instances corresponding to the service to be changed before the service is changed, detection identifiers of the original instances are preset, and a detection identifier of at least one of the original instances is a change instance detection identifier (the detection identifier of each original instance may be set in the PaaS system and then obtained from the PaaS system, or the detection identifier of each original instance may be directly preset in the instance list, which is not limited herein).

At this time, changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance, as shown in fig. 3, may include:

s301, at least one new instance is created, and the new instance is not changed relative to the original instance.

S302, adding the new instances into the instance list, and marking the detection identification of each new instance as an unchanged instance detection identification.

And S303, changing the example of which the detection identifier in the service to be changed is the change example detection identifier according to the example list.

In this way, the traffic received by the service to be changed can be shared by the created new instance which is not changed, so as to stabilize the access of the user traffic. And if the examples specified in the example list are changed, a part of the examples can be changed first, so that the changed examples are subjected to abnormality detection, and the change of other examples is performed when abnormality is detected in the subsequent process. Since some of the previously changed instances may have an abnormality, the traffic is shared by creating an unchanged new instance, so that the traffic number (i.e. the number of users) affected by the changed instances when the abnormality exists can be reduced, thereby reducing the impact on the users in the process of changing the service to be changed. It should be noted that, based on the effect of the created unchanged new instances, the larger the number of created new instances, the better, and the new instances can be set according to actual needs.

Based on the foregoing method, optionally, changing the instance of the service to be changed so that each instance of the service to be changed is a changed instance, as shown in fig. 4, the method may include:

s401, changing the unchanged original instance in the service to be changed.

S402, deleting each new instance in the service to be changed, and deleting each new instance and the corresponding detection identifier in the instance list.

Therefore, on the basis that the previously created new instance shares the user traffic, when the changed instance is determined to be abnormal, the rest original instances which are not changed are changed, and then the new instance is deleted, so that under the condition that the final number of the instances is not changed, the traffic can be shared through the new instance in the service change process to reduce the influence on the user in the service change process.

In an exemplary embodiment, an embodiment of the present disclosure further provides a service changing apparatus, which may be used to implement the service changing method described in the foregoing embodiment.

Fig. 5 is a schematic composition diagram of a service change apparatus according to an embodiment of the present disclosure.

As shown in fig. 5, the apparatus may include:

a first changing module 501, configured to change an instance of a service to be changed to obtain at least one changed instance and at least one unchanged instance;

an anomaly detection module 502, configured to mark a corresponding detection identifier for a flow to a corresponding instance according to the detection identifier of each instance of the service to be changed in the instance list; the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is a changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is an unchanged instance detection identifier; determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier; determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index;

the second changing module 503 is configured to change the instances of the service to be changed, so that each instance in the service to be changed is a changed instance.

In some possible embodiments, the detection identifier of each instance in the instance list is preset, the detection identifier of at least one instance of the service to be changed in the instance list is a changed instance detection identifier, and the detection identifier of at least one instance is an unchanged instance detection identifier; the first changing module 501 is specifically configured to change, according to the instance list, an instance of which a detection identifier in the service to be changed is a change instance detection identifier.

In some possible embodiments, the second changing module 503 is specifically configured to change an unchanged instance in the service to be changed.

In some possible embodiments, the instance list includes original instances corresponding to the service to be changed before the service to be changed is changed, and the detection identifier of each original instance is preset as an unchanged instance detection identifier; a first changing module 501, configured to create new instances corresponding to the number of original instances, where the new instances are changed with respect to the original instances; and adding the new instances into the instance list, and marking the detection identifications of the new instances as changed instance detection identifications.

In some possible embodiments, the second changing module 503 is specifically configured to delete each original instance in the service to be changed, and delete each original instance and the corresponding detection identifier in the instance list.

In some possible embodiments, the instance list includes original instances corresponding to the service to be changed before the service to be changed is changed, detection identifiers of the original instances are preset, and a detection identifier of at least one instance in each original instance is a change instance detection identifier; a first change module 501, configured to create at least one new instance, where the new instance is unchanged from the original instance; adding the new instances into the instance list, and marking the detection identification of each new instance as an unchanged instance detection identification; and changing the example of which the detection identifier in the service to be changed is the change example detection identifier according to the example list.

In some possible embodiments, the second changing module 503 is specifically configured to change an unchanged original instance in the service to be changed; and deleting each new instance in the service to be changed, and deleting each new instance and the corresponding detection identifier in the instance list.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

In an exemplary embodiment, an electronic device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method according to the above embodiments.

In an exemplary embodiment, the readable storage medium may be a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method according to the above embodiment.

In an exemplary embodiment, the computer program product comprises a computer program which, when executed by a processor, implements the method according to the above embodiments.

FIG. 6 illustrates a schematic block diagram of an example electronic device 600 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 6, the device 600 comprises a computing unit 601, which may perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM) 602 or loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 601 performs the respective methods and processes described above, such as the service change method. For example, in some embodiments, the service change method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 600 via ROM 602 and/or communications unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the service change method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the service change method by any other suitable means (e.g. by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, causes the functions/acts specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present disclosure may be executed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A method of service change, comprising:

changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance;

marking a corresponding detection identifier for the flow flowing to the corresponding example according to the detection identifier of each example of the service to be changed in the example list; the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is the changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is the unchanged instance detection identifier;

determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier;

determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index;

and changing the instances of the service to be changed so that all the instances in the service to be changed are changed instances.

2. The method according to claim 1, wherein the detection flag of each instance in the instance list is preset, the detection flag of at least one instance of the service to be changed in the instance list is a changed instance detection flag, and the detection flag of at least one instance is an unchanged instance detection flag;

the changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance comprises:

and changing the example of which the detection identifier is the change example detection identifier in the service to be changed according to the example list.

3. The method according to claim 2, wherein the changing the instances of the service to be changed so that each instance of the service to be changed is a changed instance comprises:

and changing the unchanged examples in the service to be changed.

4. The method according to claim 1, wherein the instance list includes original instances corresponding to the service to be changed before the service to be changed is changed, and a detection flag of each original instance is preset as the unchanged instance detection flag; the changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance comprises:

creating a new instance corresponding to the number of original instances, the new instance having been changed with respect to the original instances;

and adding the new instances into the instance list, and marking the detection identification of each new instance as a change instance detection identification.

5. The method according to claim 4, wherein the changing the instances of the service to be changed so that each instance of the service to be changed is a changed instance comprises:

deleting each original instance in the service to be changed, and deleting each original instance and the corresponding detection identifier in the instance list.

6. The method according to claim 1, wherein the instance list includes original instances corresponding to the service to be changed before the service to be changed is changed, detection identifiers of the original instances are preset, and a detection identifier of at least one instance in the original instances is a change instance detection identifier; the changing the instance of the service to be changed to obtain at least one changed instance and at least one unchanged instance comprises:

creating at least one new instance, the new instance being unchanged from the original instance;

adding the new instances into the instance list, and marking the detection identification of each new instance as an unchanged instance detection identification;

7. The method according to claim 6, wherein the changing the instances of the service to be changed so that each instance of the service to be changed is a changed instance comprises:

changing the unchanged original instance in the service to be changed;

and deleting each new instance in the service to be changed, and deleting each new instance and the corresponding detection identifier in the instance list.

8. A service change apparatus, comprising:

the first change module is used for changing the instances of the service to be changed to obtain at least one changed instance and at least one unchanged instance;

the anomaly detection module is used for marking a corresponding detection identifier for the flow of the corresponding example according to the detection identifier of each example of the service to be changed in the example list; wherein, the detection identifier is a changed instance detection identifier or an unchanged instance detection identifier, the detection identifier of the changed instance in each instance is the changed instance detection identifier, and the detection identifier of the unchanged instance in each instance is the unchanged instance detection identifier; determining a change state evaluation index corresponding to the flow marked with the change instance detection identifier; determining that the changed examples in the service to be changed have no abnormity according to the change state evaluation index;

and the second changing module is used for changing the instances of the service to be changed so as to enable all the instances in the service to be changed instances.

9. The apparatus according to claim 8, wherein the detection flag of each instance in the instance list is preset, the detection flag of at least one instance of the service to be changed in the instance list is a changed instance detection flag, and the detection flag of at least one instance is an unchanged instance detection flag; the first changing module is specifically configured to change, according to the instance list, an instance of which a detection identifier in the service to be changed is a change instance detection identifier.

10. The apparatus according to claim 9, wherein the second changing module is specifically configured to change an unchanged instance in the service to be changed.

11. The apparatus according to claim 8, wherein the instance list includes original instances corresponding to the service to be changed before the service is changed, and a detection flag of each original instance is preset as the unchanged instance detection flag; the first changing module is specifically configured to create new instances corresponding to the number of the original instances, where the new instances are changed with respect to the original instances; and adding the new instances into the instance list, and marking the detection identification of each new instance as a change instance detection identification.

12. The apparatus according to claim 11, wherein the second change module is specifically configured to delete each original instance in the service to be changed, and delete each original instance and the corresponding detection identifier in the instance list.

13. The apparatus according to claim 8, wherein the instance list includes original instances corresponding to the service to be changed before the service is changed, detection identifiers of the original instances are preset, and a detection identifier of at least one instance in each original instance is a change instance detection identifier; the first changing module is specifically configured to create at least one new instance, where the new instance is unchanged from the original instance; adding the new examples into the example list, and marking the detection identification of each new example as an unchanged example detection identification; and changing the example of which the detection identifier is the change example detection identifier in the service to be changed according to the example list.

14. The apparatus according to claim 13, wherein the second changing module is specifically configured to change the unchanged original instance in the service to be changed; and deleting each new instance in the service to be changed, and deleting each new instance and the corresponding detection identifier in the instance list.

15. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.