CN116775478A - Service release method and device and electronic equipment - Google Patents
Service release method and device and electronic equipment Download PDFInfo
- Publication number
- CN116775478A CN116775478A CN202310736854.5A CN202310736854A CN116775478A CN 116775478 A CN116775478 A CN 116775478A CN 202310736854 A CN202310736854 A CN 202310736854A CN 116775478 A CN116775478 A CN 116775478A
- Authority
- CN
- China
- Prior art keywords
- service
- gray scale
- environment
- sufficiency
- distributed
- 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
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000003860 storage Methods 0.000 claims description 14
- 230000000903 blocking effect Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 5
- 238000012216 screening Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 11
- 238000012795 verification Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000009826 distribution Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the specification provides a service release method, a device and an electronic device, wherein in the service release method, after a server obtains a service characteristic value of a service to be released, according to the service characteristic value, at least two service scene cases of the service to be released are obtained, then according to an on-line environment log, a flow rate ratio of each service scene case of the service to be released in an on-line environment is obtained, and according to the flow rate ratio of each service scene case in the on-line environment and the gray environment log, gray scale sufficiency of the service to be released is obtained, gray scale sufficiency of the service to be released is compared with gray scale sufficiency of the service to be released to the on-line environment when the gray scale sufficiency is greater than or equal to the gray scale sufficiency.
Description
[ field of technology ]
The embodiment of the specification relates to the technical field of Internet, in particular to a service release method, a service release device and electronic equipment.
[ background Art ]
Project environments can be generally classified into development environments, testing environments, gray scale environments, and production environments. The gray scale environment refers to a pre-release environment of the service, the service needs to be verified in the gray scale environment before the service is released formally, and the data source is consistent with the production environment in the final debugging stage before the service is released formally, so that the stability of the whole system is not affected after the service is released formally. The production environment, which may also be referred to as an on-line environment, refers to an environment in which the service formally provides external services, that is, an actual use environment of the service.
The coverage rate of the traditional gray environment is only the coverage rate of the verification business rule, and whether the online large flow is already subjected to coverage verification in the gray environment cannot be accurately evaluated, so that the following situations exist: the service passes verification in a gray scale environment, but after the service is released on line, the service cannot be stably provided in a large flow scene, so that the on-line stability is caused.
[ application ]
The embodiment of the specification provides a service release method, a device and electronic equipment, which are used for effectively evaluating whether an on-line high-flow scene is coverage verified in a gray scale environment, ensuring that after the service is released on line, the service can be stably provided, and ensuring the stability of an on-line system.
In a first aspect, an embodiment of the present disclosure provides a service publishing method, including: acquiring a service characteristic value of a service to be released; acquiring at least two service scene cases of the service to be distributed according to the service characteristic value; according to the log of the online environment, obtaining the flow ratio of each service scenario case of the service to be distributed in the online environment; obtaining gray scale sufficiency of the service to be distributed according to the flow rate ratio of the on-line environment of each service scenario use case and the log of the gray scale environment; comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency reaching index value of the service to be distributed; and when the gray scale sufficiency is greater than or equal to the gray scale sufficiency to reach a standard value, releasing the service to be released to an online environment.
In the service publishing method, after the server obtains the service characteristic value of the service to be published, according to the service characteristic value, at least two service scene use cases of the service to be published are obtained, then according to the log of the online environment, the flow rate ratio of each service scene use case of the service to be published in the online environment is obtained, and according to the flow rate ratio of each service scene use case in the online environment and the log of the gray environment, the gray scale sufficiency degree of the service to be published is obtained, the gray scale sufficiency degree of the service to be published is compared with the gray scale sufficiency degree of the service to be published to the online environment when the gray scale sufficiency degree is larger than or equal to the gray scale sufficiency degree, and therefore, whether the gray scale sufficiency degree (namely the total flow rate) of the service to be published in the gray scale environment is measured can be achieved, whether the online large flow scene has been subjected to coverage verification in the gray scale environment can be effectively evaluated, the service can be stably provided after the service is published to the online is guaranteed, and the stability of an online system is ensured.
In one possible implementation manner, the obtaining, according to the log of the online environment, the traffic ratio of the online environment for each service scenario use case of the service to be distributed includes: screening and obtaining the flow number of each service scene use case in the online environment from the log of the online environment; acquiring the total flow number of the service to be distributed in the online environment; and determining the flow ratio of each service scenario case in an on-line environment according to the flow number of each service scenario case and the total flow number.
In one possible implementation manner, the obtaining the gray level sufficiency of the service to be distributed according to the flow ratio of the on-line environment of each service scenario use case and the log of the gray level environment includes: judging whether each service scene use case occurs in the gray environment according to the log of the gray environment; and calculating the sum of the flow rates of the service scene cases in the gray scale environment, and taking the sum of the flow rates as the gray scale sufficiency of the service to be distributed.
In one possible implementation manner, after comparing the gray scale sufficiency of the service to be issued with the gray scale sufficiency reaching a standard value of the service to be issued, the method further includes: and when the gray scale sufficiency is smaller than the gray scale sufficiency to reach a standard value, preventing the service to be distributed from being distributed to the online environment.
In one possible implementation manner, after the blocking the service to be distributed from being distributed to the online environment, the method further includes: increasing the flow rate of the online environment introduced into the gray scale environment; or, after waiting for a first preset time, re-executing the log according to the online environment to obtain the flow rate ratio of each service scenario use case of the service to be distributed in the online environment and the subsequent steps.
In a second aspect, embodiments of the present disclosure provide a service publishing device, including: the acquisition module is used for acquiring the service characteristic value of the service to be released; acquiring at least two service scene cases of the service to be distributed according to the service characteristic value; the flow rate ratio obtaining module is used for obtaining the flow rate ratio of each service scene use case of the service to be distributed in the online environment according to the log of the online environment; the gray scale sufficiency obtaining module is used for obtaining the gray scale sufficiency of the service to be distributed according to the flow rate ratio of the on-line environment of each service scene use case and the log of the gray scale environment; the comparison module is used for comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency reaching index value of the service to be distributed; and the release module is used for releasing the service to be released to an online environment when the gray scale sufficiency is greater than or equal to the gray scale sufficiency to the mark value.
In one possible implementation manner, the flow ratio obtaining module includes: the flow number obtaining submodule is used for screening and obtaining the flow number of each service scene use case in the online environment from the log of the online environment; acquiring the total flow number of the service to be distributed in the online environment; and the traffic ratio determining submodule is used for determining the traffic ratio of the on-line environment of each service scene use case according to the traffic number of each service scene use case and the total traffic number.
In one possible implementation manner, the gray scale sufficiency obtaining module includes: the judging submodule is used for judging whether each service scene use case occurs in the gray environment according to the log of the gray environment; and the calculating sub-module is used for calculating the sum of the flow rates of the service scene use cases in the gray scale environment, and taking the sum of the flow rates as the gray scale sufficiency of the service to be distributed.
In one possible implementation manner, the apparatus further includes: and the blocking module is used for blocking the service to be distributed from being distributed to the online environment when the gray scale sufficiency reaches a standard value after the gray scale sufficiency of the service to be distributed is compared with the gray scale sufficiency reaches the standard value by the comparison module.
In one possible implementation manner, the apparatus further includes: and the adding module is used for adding the flow of the online environment introduced into the gray environment after the blocking module blocks the service to be distributed from being distributed to the online environment.
In a third aspect, embodiments of the present disclosure provide an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method provided in the first aspect.
In a fourth aspect, the present description embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause a computer to perform the method provided in the first aspect.
It should be understood that the second to fourth aspects of the embodiments of the present disclosure are consistent with the technical solutions of the first aspect of the embodiments of the present disclosure, and the beneficial effects obtained by each aspect and the corresponding possible implementation manner are similar and are not repeated.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present description, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is an application scenario schematic diagram of a service publishing method according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a service publishing method according to an embodiment of the present disclosure;
fig. 3 (a) to 3 (b) are schematic diagrams illustrating the gray level sufficiency detection result provided in one embodiment of the present disclosure;
fig. 4 is a flowchart of a service publishing method according to another embodiment of the present disclosure;
fig. 5 is a flowchart of a service publishing method according to still another embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a service issuing device according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a service issuing device according to another embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
[ detailed description ] of the application
For a better understanding of the technical solutions of the present specification, embodiments of the present specification are described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are only some, but not all, of the embodiments of the present description. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present disclosure.
The terminology used in the embodiments of the description presented herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description presented herein. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Aiming at the problem that in the prior art, the coverage rate of the gray environment is only the coverage rate of the verification service rule, and whether the online high traffic is already subjected to coverage verification in the gray environment cannot be accurately evaluated, the embodiment of the specification provides a service release method which can measure whether the total traffic of the service to be released in the gray environment can reach the standard, so that the stability problem of the service to be released can be timely found in the gray environment.
Fig. 1 is an application scenario schematic diagram of a service publishing method according to an embodiment of the present disclosure, and in the following, description is given by referring to fig. 1, to the service publishing method according to an embodiment of the present disclosure.
Fig. 2 is a flowchart of a service distribution method according to an embodiment of the present disclosure, where the service distribution method may be executed by a server. As shown in fig. 2, the service publishing method may include:
step 202, obtaining the service characteristic value of the service to be issued.
Specifically, the service characteristic value is related to the service to be distributed, and the service characteristic values of different services are different. Assuming that the service to be issued is a payment service, the service characteristic value may include: payment channel, payment currency, user identification, vendor identification, and acquirement currency, etc.
Step 204, obtaining at least two service scenario cases of the service to be distributed according to the service characteristic value.
Specifically, after obtaining the service characteristic value of the service to be issued, the server may perform modeling according to the service characteristic value, so as to obtain at least two service scenario cases of the service to be issued.
Still taking payment service as an example, a service scenario case (hereinafter referred to as a service scenario case a) may be: payment channel-credit card payment, payment currency-renminbi, user identification-user a, seller identification-seller a and acquirement currency-renminbi; another service scenario case (hereinafter referred to as service scenario case B) may be: payment channel-balance payment, payment currency-Renminbi, user identification-user B, seller identification-seller B, and receipts currency-dollars.
And 206, obtaining the flow ratio of each service scenario use case of the service to be distributed in the online environment according to the log of the online environment.
Specifically, referring to fig. 1, the log of the online environment belongs to online data, and the log of the online environment may be obtained from a log aggregation platform and a monitoring platform. Then, as shown in fig. 1, in the step of gray level sufficiency calculation, the server may obtain, according to the log of the online environment, the traffic ratio of each service scenario use case of the service to be distributed in the online environment.
And step 208, obtaining the gray scale sufficiency of the service to be distributed according to the flow rate ratio of the online environment of each service scene use case and the log of the gray scale environment.
Specifically, with continued reference to fig. 1, in the procedure of gray scale sufficiency calculation, after the flow rate ratio of the online environment is obtained, gray scale sufficiency of the service to be distributed may be obtained according to the log of the gray scale environment and the flow rate ratio of each service scenario case in the online environment.
Likewise, the server may obtain logs of the greyscale environment from the log aggregation platform and the monitoring platform.
Step 210, comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency of the service to be distributed to the standard value.
The gray scale sufficiency value of the service to be issued can be set by itself according to system performance and/or implementation requirements, and the size of the gray scale sufficiency value is not limited in this embodiment.
And 212, when the gray scale sufficiency is greater than or equal to the gray scale sufficiency to a mark value, releasing the service to be released to an online environment.
In this embodiment, when the gray scale sufficiency is smaller than the gray scale sufficiency by a mark value, the server prevents the service to be distributed from being distributed to an online environment.
Specifically, referring to fig. 1, in the gray level distribution link, when the service to be distributed performs gray level distribution, the server may obtain the gray level sufficiency of the service to be distributed at the gray level stuck point, then compare the gray level sufficiency of the service to be distributed with the gray level sufficiency of the service to be distributed to the mark value, and if the gray level sufficiency of the service to be distributed is greater than or equal to the gray level sufficiency to the mark value, then distribute the service to be distributed to the online environment by the server; if the gray scale sufficiency of the service to be released is smaller than the gray scale sufficiency by the mark value, the server returns to 'unsatisfied', and the service to be released is prevented from being released to the online environment.
Further, in this embodiment, after the server prevents the service to be distributed from being distributed to the online environment, the flow of the online environment for introducing the gray environment can be further increased in the gray drainage link; or, after waiting for the first predetermined time period, the step 206 and the subsequent steps are re-executed, where the first predetermined time period may be set by the user during the implementation, and the length of the first predetermined time period is not limited in this embodiment.
In addition, in a specific implementation, when the gray scale sufficiency of the service to be distributed is greater than or equal to the above gray scale sufficiency, the server may display the page shown in fig. 3 (a), and when the gray scale sufficiency of the service to be distributed is less than the above gray scale sufficiency, the server may display the page shown in fig. 3 (b). Fig. 3 (a) to 3 (b) are schematic diagrams of the gray scale sufficiency detection results provided in one embodiment of the present disclosure.
In the service publishing method, after the server obtains the service characteristic value of the service to be published, according to the service characteristic value, at least two service scene use cases of the service to be published are obtained, then according to the log of the online environment, the flow rate ratio of each service scene use case of the service to be published in the online environment is obtained, and according to the flow rate ratio of each service scene use case in the online environment and the log of the gray environment, the gray scale sufficiency degree of the service to be published is obtained, the gray scale sufficiency degree of the service to be published is compared with the gray scale sufficiency degree of the service to be published to the online environment when the gray scale sufficiency degree is larger than or equal to the gray scale sufficiency degree, and therefore, whether the gray scale sufficiency degree (namely the total flow rate) of the service to be published in the gray scale environment is measured can be achieved, whether the online large flow scene has been subjected to coverage verification in the gray scale environment can be effectively evaluated, the service can be stably provided after the service is published to the online is guaranteed, and the stability of an online system is ensured.
Fig. 4 is a flowchart of a service publishing method according to another embodiment of the present disclosure, as shown in fig. 4, in the embodiment shown in fig. 2 of the present disclosure, step 206 may include:
step 402, screening and obtaining the number of traffic of each service scenario case in the online environment from the log of the online environment; and obtaining the total flow number of the service to be distributed in the online environment.
The log of the online environment may be a log of the online environment for a second predetermined period of time before the current time. The second predetermined time period may be set by the user during the implementation, for example, the second predetermined time period may be 7 days.
And step 404, determining the flow rate ratio of each service scenario case in the on-line environment according to the flow rate number of each service scenario case and the total flow rate number.
Specifically, the above flow rate ratio may be determined according to the formula (1).
Fig. 5 is a flowchart of a service publishing method according to still another embodiment of the present disclosure, as shown in fig. 5, in the embodiment shown in fig. 2 of the present disclosure, step 208 may include:
step 502, judging whether each service scenario use case occurs in the gray scale environment according to the log of the gray scale environment.
And step 504, calculating the sum of the flow rates of the service scene use cases generated in the gray scale environment, and taking the sum of the flow rates as gray scale sufficiency of the service to be distributed.
Specifically, the gray scale sufficiency of the traffic to be distributed can be calculated according to the formula (2).
Traffic duty ratio of gray scale sufficiency of service to be released = Σservice scenario case x whether or not in gray scale environment occurs (2)
In the formula (2), the value of the parameter "whether or not the gray environment occurs" is set to "1" when the service scene use case occurs in the gray environment, and the value of the parameter is set to "0" when the service scene use case does not occur in the gray environment.
Still taking the payment service as an example, as described above, the payment service includes a service scenario case a and a service scenario case B, and assuming that the traffic ratio of the service scenario case a is 25% and the traffic ratio of the service scenario case B is 50%, if the service scenario case a occurs in a gray scale environment and the service scenario case B does not occur in a gray scale environment, the gray scale sufficiency of the payment service=25% ×1+50% ×0=25%.
According to the service release method provided by the embodiment of the specification, the flow ratio of each service scene use case of the service to be released in the online environment can be counted, whether the online high-flow scene is subjected to coverage verification in the gray environment or not can be effectively evaluated, the blocking point of gray release can be performed, the service can be stably provided after the service is released on the line, and the stability of an online system is ensured.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Fig. 6 is a schematic structural diagram of a service issuing device according to an embodiment of the present disclosure, and as shown in fig. 6, the service issuing device may include: an acquisition module 61, a flow duty ratio acquisition module 62, a gray scale sufficiency acquisition module 63, a comparison module 64, and a distribution module 65;
an obtaining module 61, configured to obtain a service feature value of a service to be published; acquiring at least two service scene cases of the service to be issued according to the service characteristic values;
the flow rate duty ratio obtaining module 62 is configured to obtain, according to the log of the online environment, the flow rate duty ratio of each service scenario use case of the service to be distributed in the online environment;
the gray scale sufficiency obtaining module 63, configured to obtain the gray scale sufficiency of the service to be distributed according to the flow ratio of the online environment of each service scenario use case and the log of the gray scale environment;
the comparison module 64 is configured to compare the gray scale sufficiency of the service to be issued with the gray scale sufficiency reaching a standard value of the service to be issued;
and the issuing module 65 is configured to issue the service to be issued to the online environment when the gray scale sufficiency is greater than or equal to the gray scale sufficiency by a mark value.
The service issuing device provided in the embodiment shown in fig. 6 may be used to implement the technical solution of the method embodiment shown in fig. 2 in this specification, and the implementation principle and technical effects may be further referred to in the related description of the method embodiment.
Fig. 7 is a schematic structural diagram of a service issuing device according to another embodiment of the present disclosure, and in comparison with the service issuing device shown in fig. 6, in the service issuing device shown in fig. 7, the flow rate ratio obtaining module 62 may include: a traffic stripe number obtaining sub-module 621 and a traffic duty ratio determining sub-module 622;
the traffic number obtaining sub-module 621 is configured to screen and obtain the traffic number of each service scenario case in the online environment from the log of the online environment; acquiring the total flow number of the service to be distributed in the online environment;
the traffic ratio determining submodule 622 is configured to determine a traffic ratio of each service scenario case in the online environment according to the traffic number of each service scenario case and the total traffic number.
In this embodiment, the gray scale sufficiency obtaining module 63 may include: a judgment sub-module 631 and a calculation sub-module 632;
the judging sub-module 631 is configured to judge whether each service scenario use case occurs in the grayscale environment according to the log of the grayscale environment;
the calculation sub-module 632 is configured to calculate a sum of the traffic ratios of the traffic scenario cases generated in the gray scale environment, and take the sum of the traffic ratios as gray scale sufficiency of the traffic to be issued.
Further, the service issuing device may further include: a blocking module 66;
the blocking module 66 is configured to block the service to be issued from being issued to the online environment when the gray scale sufficiency is smaller than the gray scale sufficiency value after the comparing module 64 compares the gray scale sufficiency of the service to be issued with the gray scale sufficiency value of the service to be issued.
Further, the service issuing device may further include: an add module 67;
an adding module 67, configured to increase the flow of the on-line environment for introducing the gray environment after the blocking module 66 blocks the service to be distributed from being distributed to the on-line environment.
In addition, in this embodiment, the flow rate ratio obtaining module 62 may further re-execute the step of obtaining the flow rate ratio of each service scenario use case of the service to be distributed in the online environment according to the log of the online environment after waiting for the first predetermined time period.
The service issuing device provided in the embodiment shown in fig. 7 may be used to implement the technical solutions of the method embodiments shown in fig. 2 to 5 in this specification, and the implementation principle and technical effects may be further described with reference to the related descriptions in the method embodiments.
Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure, where, as shown in fig. 8, the electronic device may include at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to execute the service issuing method provided in the embodiments shown in fig. 2 to 5 of the present specification.
The electronic device may be a server, for example: the server for performing service release may be disposed at the cloud, and the form of the electronic device is not limited in this embodiment.
Fig. 8 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present description. The electronic device shown in fig. 8 is only an example and should not be construed as limiting the functionality and scope of use of the embodiments herein.
As shown in fig. 8, the electronic device is in the form of a general purpose computing device. Components of an electronic device may include, but are not limited to: one or more processors 410, a communication interface 420, a memory 430, and a communication bus 440 that connects the different components (including the memory 430, the communication interface 420, and the processor 410).
The communication bus 440 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, communication buses 440 may include industry standard architecture (industry standard architecture, ISA) buses, micro channel architecture (micro channel architecture, MCA) buses, enhanced ISA buses, video electronics standards association (video electronics standards association, VESA) local bus, and peripheral component interconnect (peripheral component interconnection, PCI) buses.
Electronic devices typically include a variety of computer system readable media. Such media can be any available media that can be accessed by the electronic device and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 430 may include computer system readable media in the form of volatile memory, such as random access memory (random access memory, RAM) and/or cache memory. Memory 430 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments shown in fig. 2-5 of the present description.
A program/utility having a set (at least one) of program modules may be stored in the memory 430, such program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules generally carry out the functions and/or methods of the embodiments described in fig. 2-5 of the present description.
The processor 410 executes various functional applications and data processing by running programs stored in the memory 430, for example, implementing the service distribution method provided in the embodiment shown in fig. 2 to 5 of the present specification.
Embodiments of the present disclosure provide a non-transitory computer readable storage medium storing computer instructions that cause a computer to execute the service issuing method provided by the embodiments shown in fig. 2 to 5 of the present disclosure.
The non-transitory computer readable storage media described above may employ any combination of one or more computer readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having 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 (erasable programmable read only memory, EPROM) or flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for the present specification may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (local area network, LAN) or a wide area network (wide area network, WAN), or may be connected to an external computer (e.g., connected via the internet using an internet service provider).
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present specification, the meaning of "plurality" means at least two, for example, two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present specification in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present specification.
Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.
It should be noted that, the terminals in the embodiments of the present disclosure may include, but are not limited to, a personal computer (personal computer, PC), a personal digital assistant (personal digital assistant, PDA), a wireless handheld device, a tablet computer (tablet computer), a mobile phone, an MP3 player, an MP4 player, and the like.
In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.
The foregoing description of the preferred embodiments is provided for the purpose of illustration only, and is not intended to limit the scope of the disclosure, since any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.
Claims (12)
1. A service publishing method, comprising:
acquiring a service characteristic value of a service to be released;
acquiring at least two service scene cases of the service to be distributed according to the service characteristic value;
according to the log of the online environment, obtaining the flow ratio of each service scenario case of the service to be distributed in the online environment;
obtaining gray scale sufficiency of the service to be distributed according to the flow rate ratio of the on-line environment of each service scenario use case and the log of the gray scale environment;
comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency reaching index value of the service to be distributed;
and when the gray scale sufficiency is greater than or equal to the gray scale sufficiency to reach a standard value, releasing the service to be released to an online environment.
2. The method of claim 1, wherein the obtaining the traffic ratio of the on-line environment for each service scenario case of the service to be distributed according to the log of the on-line environment comprises:
screening and obtaining the flow number of each service scene use case in the online environment from the log of the online environment; acquiring the total flow number of the service to be distributed in the online environment;
and determining the flow ratio of each service scenario case in an on-line environment according to the flow number of each service scenario case and the total flow number.
3. The method of claim 1, wherein the obtaining the gray scale sufficiency of the service to be distributed according to the traffic ratio of the on-line environment of each service scenario case and the log of the gray scale environment comprises:
judging whether each service scene use case occurs in the gray environment according to the log of the gray environment;
and calculating the sum of the flow rates of the service scene cases in the gray scale environment, and taking the sum of the flow rates as the gray scale sufficiency of the service to be distributed.
4. The method of claim 1, wherein the comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency of the service to be distributed by a scalar value further comprises:
and when the gray scale sufficiency is smaller than the gray scale sufficiency to reach a standard value, preventing the service to be distributed from being distributed to the online environment.
5. The method of claim 4, wherein the preventing the service to be published from being published to the online environment further comprises:
increasing the flow rate of the online environment introduced into the gray scale environment; or alternatively, the process may be performed,
and after waiting for a first preset time, re-executing the log according to the online environment to obtain the flow ratio of each service scenario use case of the service to be distributed in the online environment and the subsequent steps.
6. A service issuing apparatus comprising:
the acquisition module is used for acquiring the service characteristic value of the service to be released; acquiring at least two service scene cases of the service to be distributed according to the service characteristic value;
the flow rate ratio obtaining module is used for obtaining the flow rate ratio of each service scene use case of the service to be distributed in the online environment according to the log of the online environment;
the gray scale sufficiency obtaining module is used for obtaining the gray scale sufficiency of the service to be distributed according to the flow rate ratio of the on-line environment of each service scene use case and the log of the gray scale environment;
the comparison module is used for comparing the gray scale sufficiency of the service to be distributed with the gray scale sufficiency reaching index value of the service to be distributed;
and the release module is used for releasing the service to be released to an online environment when the gray scale sufficiency is greater than or equal to the gray scale sufficiency to the mark value.
7. The apparatus of claim 6, wherein the flow duty cycle obtaining module comprises:
the flow number obtaining submodule is used for screening and obtaining the flow number of each service scene use case in the online environment from the log of the online environment; acquiring the total flow number of the service to be distributed in the online environment;
and the traffic ratio determining submodule is used for determining the traffic ratio of the on-line environment of each service scene use case according to the traffic number of each service scene use case and the total traffic number.
8. The apparatus of claim 6, wherein the gray scale sufficiency obtaining module comprises:
the judging submodule is used for judging whether each service scene use case occurs in the gray environment according to the log of the gray environment;
and the calculating sub-module is used for calculating the sum of the flow rates of the service scene use cases in the gray scale environment, and taking the sum of the flow rates as the gray scale sufficiency of the service to be distributed.
9. The apparatus of claim 6, further comprising:
and the blocking module is used for blocking the service to be distributed from being distributed to the online environment when the gray scale sufficiency reaches a standard value after the gray scale sufficiency of the service to be distributed is compared with the gray scale sufficiency reaches the standard value by the comparison module.
10. The apparatus of claim 9, further comprising:
and the adding module is used for adding the flow of the online environment introduced into the gray environment after the blocking module blocks the service to be distributed from being distributed to the online environment.
11. An electronic device, comprising:
at least one processor; and
at least one memory communicatively coupled to the processor, wherein:
the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-5.
12. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310736854.5A CN116775478A (en) | 2023-06-20 | 2023-06-20 | Service release method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310736854.5A CN116775478A (en) | 2023-06-20 | 2023-06-20 | Service release method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116775478A true CN116775478A (en) | 2023-09-19 |
Family
ID=87992526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310736854.5A Pending CN116775478A (en) | 2023-06-20 | 2023-06-20 | Service release method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116775478A (en) |
-
2023
- 2023-06-20 CN CN202310736854.5A patent/CN116775478A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110633726A (en) | Room source identification method and device, storage medium and electronic equipment | |
| CN111400695B (en) | Equipment fingerprint generation method, device, equipment and medium | |
| CN111784320B (en) | Data association method and device and electronic equipment | |
| CN108062423B (en) | Information-pushing method and device | |
| CN109656803B (en) | Information pushing method and device and electronic equipment | |
| CN111367813B (en) | Automatic testing method and device for decision engine, server and storage medium | |
| CN116775478A (en) | Service release method and device and electronic equipment | |
| CN111400353A (en) | Rule calculation method, device, equipment and storage medium | |
| US20120331456A1 (en) | Comparing system engram with product engram to determine compatibility of product with system | |
| CN113688133B (en) | Data processing method, system, device, medium and equipment based on compliance calculation | |
| CN108628909B (en) | Information pushing method and device | |
| CN113365113A (en) | Target node identification method and device | |
| CN114428815A (en) | Data storage method and device, electronic equipment and computer readable medium | |
| CN114519568A (en) | Order examination method and device, electronic equipment and storage medium | |
| CN113129127A (en) | Early warning method and device | |
| CN114218283A (en) | Abnormality detection method, apparatus, device, and medium | |
| CN110674491A (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN111611345B (en) | Illegal object identification method and device and electronic equipment | |
| CN116108132B (en) | Method and device for auditing text of short message | |
| CN115687030A (en) | Monitoring alarm method and device and electronic equipment | |
| CN111930704B (en) | Service alarm equipment control method, device, equipment and computer readable medium | |
| CN116258576A (en) | Abnormal transaction identification method, device, equipment, storage medium and product | |
| CN116578987A (en) | Information security assessment method, system, medium and electronic equipment based on cloud computing | |
| CN112463200A (en) | Development kit processing method and device, electronic device and storage medium | |
| CN113421036A (en) | Information display method and device, electronic equipment and computer readable medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240226 Address after: Guohao Times City # 20-01, 128 Meizhi Road, Singapore Applicant after: Advanced Nova Technology (Singapore) Holdings Ltd. Country or region after: Singapore Address before: 51 Belarusian Bashar Road, Singapore, Lai Zanda 1 # 04-08 Applicant before: Alipay laboratories (Singapore) Ltd. Country or region before: Singapore |
|
| TA01 | Transfer of patent application right |