Service application scheduling method and device, equipment and medium

Abstract

The invention discloses a service application scheduling method and device, equipment and a medium, and the method comprises the steps: determining a service type of a back-end service application to obtain a target service type when the back-end service application meets a preset capacity expansion condition; a deployment template corresponding to the target service type is obtained from a preset template library to obtain a target deployment template, and the preset template library comprises deployment templates of different service types; deploying a target number of application examples corresponding to the back-end service application based on the target deployment template; and if the differentiated deployment package corresponding to the back-end service application exists, differentiated deployment of the application instance is carried out based on the differentiated deployment package. Therefore, the stability and response speed of the service can be guaranteed, and service collapse caused by overhigh load is avoided.

Description

Technical Field

[0001] The present application relates to the technical field of service application scheduling, and in particular to a service application scheduling method, device, equipment and medium. Background Art

[0002] With the development of cloud computing technology, more and more industries are deploying their businesses under the cloud service architecture because of its flexible adjustment of resource usage and cost advantages. However, the volume of user requests usually fluctuates. When traffic may surge, how to ensure the stability and response speed of the service to avoid service crashes due to excessive load is a problem that needs to be solved. Summary of the invention

[0003] In view of this, the purpose of this application is to provide a service application scheduling method, device, equipment and medium, which can ensure the stability and response speed of the service to avoid service crash due to excessive load. The specific scheme is as follows:

[0004] In a first aspect, the present application discloses a service application scheduling method, comprising:

[0005] When the backend service application meets the preset expansion condition, determining the service type of the backend service application to obtain a target service type;

[0006] Acquire a deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types;

[0007] Deploy a target number of application instances corresponding to the backend service application based on the target deployment template;

[0008] If there is a differentiated deployment package corresponding to the backend service application, differentiated deployment of the application instance is performed based on the differentiated deployment package.

[0009] Optionally, after deploying a target number of application instances corresponding to the backend service application based on the target deployment template, the method further includes:

[0010] The regional address parameter of the application instance is adjusted to dispatch the access request of the region corresponding to the regional address parameter to the application instance, and the regional data center corresponding to the regional address parameter provides operating resources for the application instance.

[0011] Optionally, the service types include a service gateway class, a high-speed service engine class, and an asynchronous task application class, wherein the backend service application of the high-speed service engine class is a service application that uses the TCP protocol, and the backend service application of the asynchronous task application class is a service application that consumes tasks in a task queue, and the task is a task generated based on a request initiated by the requester.

[0012] Optionally, also include:

[0013] Identify current resource usage of the backend service application;

[0014] Based on the resource usage, it is determined whether the backend service application meets a preset expansion condition.

[0015] Optionally, the preset capacity expansion condition is that the current time reaches a preset time point, and the preset time point is a time point at which capacity expansion is required, determined based on historical data.

[0016] Optionally, also include:

[0017] When the backend service application meets the preset shrinking condition, a target application instance is determined from the application instances, and the target application instance is deleted.

[0018] Optionally, also include:

[0019] When a server running any application instance crashes, the crashed server is determined as a faulty node to prohibit the access request from being dispatched to the any application instance.

[0020] In a second aspect, the present application discloses a service application scheduling device, comprising:

[0021] A service type determination module, configured to determine the service type of the backend service application to obtain a target service type when the backend service application meets a preset expansion condition;

[0022] A deployment template acquisition module, used to acquire the deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types;

[0023] An application instance deployment module, used to deploy a target number of application instances corresponding to the backend service application based on the target deployment template;

[0024] The differentiated deployment module is used to perform differentiated deployment of the application instance based on the differentiated deployment package if there is a differentiated deployment package corresponding to the backend service application.

[0025] In a third aspect, the present application discloses a computer program product, which implements the aforementioned service application scheduling method when executed.

[0026] In a fourth aspect, the present application discloses an electronic device, including a memory and a processor, wherein:

[0027] The memory is used to store the computer program;

[0028] The processor is used to execute the computer program to implement the aforementioned service application scheduling method.

[0029] In a fifth aspect, the present application discloses a computer-readable storage medium for storing a computer program, wherein the computer program implements the aforementioned service application scheduling method when executed by a processor.

[0030] It can be seen from the above scheme that the present application provides a service application scheduling method, including: when the back-end service application meets the preset expansion conditions, determining the service type of the back-end service application to obtain the target service type; obtaining the deployment template corresponding to the target service type from the preset template library to obtain the target deployment template, wherein the preset template library includes deployment templates of different service types; deploying a target number of application instances corresponding to the back-end service application based on the target deployment template; if there is a differentiated deployment package corresponding to the back-end service application, performing differentiated deployment of the application instance based on the differentiated deployment package.

[0031] It can be seen that the beneficial effects of the present application are: deployment templates for each service type are provided through a preset template library, and when expanding capacity, application instances are deployed based on the deployment templates corresponding to each service type, and differentiated deployment is provided, so that various types of back-end service applications in the business system can be expanded quickly, thereby ensuring the stability and response speed of the service, and avoiding service crashes due to excessive load.

[0032] Correspondingly, a service application scheduling device, equipment and readable storage medium provided by the present application also have the above-mentioned technical effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0034] Figure 1 A flow chart of a service application scheduling method provided in an embodiment of the present application;

[0035] Figure 2 A schematic diagram of service application scheduling of a charging service system provided in an embodiment of the present application;

[0036] Figure 3 A schematic diagram of the structure of a service application scheduling device provided in an embodiment of the present application;

[0037] Figure 4 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0039] See also Figure 1 As shown, the embodiment of the present application discloses a service application scheduling method, including:

[0040] Step S11: When the backend service application meets the preset expansion condition, the service type of the backend service application is determined to obtain the target service type.

[0041] Among them, the backend service application is a service application of a certain business system. Each backend service application can be understood as a service unit in the business system. Each backend service application works together to realize the functions of the business system to meet the business needs. For example, the charging business system may include charging pile management service applications, user management service applications, charging order management service applications, and payment management service applications, among which the charging pile management service application is used for monitoring, management, and scheduling of charging pile equipment; real-time collection of key data such as voltage, current, and temperature of charging piles, fault warning and remote diagnosis; providing real-time status information of charging piles, such as idle, charging, and fault. User management service application is used for user information registration, login, permission management, and personal information maintenance; provides user identity authentication and authorization functions to ensure the security and legitimacy of user access; manages and maintains user charging records and preference settings. Charging order management service application is used to process user charging requests and generate charging orders; track order status, such as charging start, charging end, payment status, etc.; provides order query and history record functions to facilitate users to understand their charging status at any time. Payment management service application: used to integrate multiple payment methods, such as Alipay, WeChat Pay, bank card payment, etc.; process user payment requests and complete the payment process; provide payment records and refund functions to ensure the accuracy and security of user payments. The business system can adopt a microservice architecture, that is, the backend service application is a microservice in the business system.

[0042] In an optional implementation, the current resource usage of the backend service application may be identified; and based on the resource usage, it may be determined whether the backend service application meets a preset expansion condition.

[0043] The resource usage may include but is not limited to CPU (Central Processing Unit) usage, memory usage, disk I / O (Input / Output), network bandwidth, and one or more of specific performance, such as response time, throughput, etc. When the resource usage reaches the preset resource shortage condition, it is determined that the preset expansion condition is met. For example, the CPU usage is higher than the preset threshold, the memory usage is higher than the preset threshold, etc.

[0044] In another optional implementation, the preset capacity expansion condition is that the current time reaches a preset time point, and the preset time point is a time point at which capacity expansion is required, determined based on historical data.

[0045] The historical data may be historical traffic data, which can reflect traffic fluctuations. The preset time points may include expansion time points determined based on daily traffic peaks and time points corresponding to promotional activity dates. For example, the daily charging business peak and the time points corresponding to the year-end promotion activities.

[0046] Of course, the embodiments of the present application can also comprehensively determine whether capacity expansion is needed based on a preset time point and the current resource usage of the back-end service application. For example, when the preset time point is reached, the current resource usage of the back-end service application is identified; based on the resource usage, it is determined whether the back-end service application meets the preset capacity expansion conditions.

[0047] In this embodiment, the service types may include a service gateway class, a high-speed service engine class, and an asynchronous task application class, wherein the backend service application of the high-speed service engine class is a service application that uses the TCP (Transmission Control Protocol) protocol, and the backend service application of the asynchronous task application class is a service application that consumes tasks in a task queue, and the task is a task generated based on a request initiated by the requester.

[0048] Among them, the backend service application of the service gateway class refers to the unified external entrance of the business system, which is a service component responsible for processing external requests, filtering and forwarding requests to the corresponding service applications. The backend service application of the high-speed service engine class uses the TCP protocol for communication. It is a backend service application deployed in the local area network in the business system. Multiple backend service applications of the high-speed service engine class collaborate to complete the corresponding business processing. The local area network can use the TCP protocol with higher communication efficiency for communication. For the backend service application of the asynchronous task application class, after initiating a certain request, the request is placed in the queue. The backend service application of the asynchronous task application class consumes the requests in the queue, such as report calculation.

[0049] The embodiment of the present application can classify various backend service applications in the business system, abstract the common template corresponding to each type of backend service application, and thus ensure rapid deployment.

[0050] In addition, the deployment template in this embodiment is optimized to ensure that user requests can be quickly responded to in high concurrency situations. For example, for the service gateway class, the WebApi (i.e., Web Application Programming Interface) site will be automatically registered, the firewall port exception will be enabled, and the site routing will be enabled. The back-end service application of the high-speed service engine class may include port exceptions. Among them, registering a WebApi site means deploying and configuring a WebApi service on the server so that it can be accessed through the Internet. WebApi is a framework for building HTTP (i.e., Hypertext Transfer Protocol) services, allowing developers to expose data and services to external devices or applications in the form of HTTP requests. By registering a WebApi site, a unified interface can be created for different clients (such as browsers, mobile applications, etc.) to access and operate data and services on the server through HTTP requests. It helps to achieve cross-platform and cross-device data sharing and function calls. Enabling firewall port exceptions means allowing traffic on a specific port to pass through the firewall without scanning or interception. A firewall is a network security device or software that monitors and controls data flows in and out of the network to prevent unauthorized access and data leakage. Enabling firewall port exceptions can ensure that specific network services (such as WebApi sites) can normally receive and process requests from external networks. This is especially important for web services that need to be publicly accessible, allowing legitimate request traffic to pass through the firewall while blocking potential malicious attacks. Enabling site routing refers to configuring a web server or application server to support URL (i.e. Uniform Resource Locator) routing. URL routing is a technology that maps specific URL patterns to specific processing functions or resources, allowing developers to dynamically select and execute corresponding code or operations based on the requested URL. By enabling site routing, you can create more flexible and maintainable web applications. For example, different pages can be presented or different functions can be performed based on different URL paths, providing a better user experience and higher application performance.

[0051] Step S12: Acquire a deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types.

[0052] The preset template library is a pre-built template library including deployment templates corresponding to each service type. Based on the service type identifier, the deployment template corresponding to the target service type can be obtained from the preset template library to obtain the target deployment template. In addition, the deployment template of any service type can be updated as the business develops.

[0053] Step S13: deploying a target number of application instances corresponding to the backend service application based on the target deployment template.

[0054] The target number can be preset or determined based on the resource usage and request volume of the current backend service application. The target number can be one or more.

[0055] Step S14: If there is a differentiated deployment package corresponding to the backend service application, differentiated deployment of the application instance is performed based on the differentiated deployment package.

[0056] That is, the embodiment of the present application abstracts the deployment template corresponding to the same service type, but if there are individual differences, differentiated deployment can be completed based on differentiated deployment packages.

[0057] In an optional implementation, after deploying the target number of application instances corresponding to the backend service application based on the target deployment template, it also includes: adjusting the regional address parameters of the application instance to schedule access requests from the area corresponding to the regional address parameters to the application instance, and the regional data center corresponding to the regional address parameters provides operating resources for the application instance.

[0058] Among them, a regional data center refers to an infrastructure that centrally stores, processes and manages data in a specific geographical area in a physical or virtual manner. It may include high-performance servers, storage devices, network devices and security devices, etc., to support the data needs of various business applications in the area. The embodiment of the present application can deploy application instances to corresponding regions, thereby improving the processing efficiency of access requests. The example of the present application can adjust the regional address parameters of the application instance and other parameters related to the regional data center based on the configuration file of the regional data center, thereby realizing regional deployment.

[0059] In an optional implementation, when the backend service application meets a preset scaling-down condition, a target application instance is determined from each of the application instances, and the target application instance is deleted.

[0060] The preset shrinking condition may be a preset shrinking time point, such as the end time point of a promotion activity, the end time of a daily peak, etc. It is also possible to determine whether the preset shrinking condition is met by monitoring the resource usage of the application.

[0061] In an optional implementation, when a server running any application instance crashes, the crashed server is determined as a faulty node to prohibit scheduling access requests to any application instance.

[0062] That is, the embodiment of the present application can monitor the operation of the server and promptly identify the downed server as a faulty node to prohibit the dispatch of access requests to the server, thereby ensuring the smooth processing of the request. The heartbeat monitoring mechanism can be used to regularly check the server status to ensure that problems are discovered and handled in a timely manner.

[0063] In addition, when the downed server is identified as a faulty node, it can be determined whether the corresponding application instance needs to be expanded. If expansion is required, the application instance can be quickly deployed on a new server based on the service type of the application instance deployed on the downed server.

[0064] It can be seen that the embodiment of the present application provides deployment templates for each service type through a preset template library. When expanding capacity, application instances are deployed based on the deployment templates corresponding to each service type, and differentiated deployment is provided, so that various types of back-end service applications in the business system can be expanded quickly, thereby ensuring the stability and response speed of the service, and avoiding service crashes due to excessive load.

[0065] Below, the service application scheduling solution provided by this application is further explained by the service application scheduling process of the charging business system:

[0066] See also Figure 2 As shown, Figure 2 A schematic diagram of service application scheduling for a charging business system provided for this application. It includes three components: downtime alarm, cloud server resource evaluation, and capacity scheduling engine to realize service application scheduling of the charging business system, which can realize dynamic capacity management of back-end application services for high-concurrency charging business. Downtime alarm is used to detect the operation of the server and perform fault handling and alarm when the server is down. Cloud server resource evaluation is used to evaluate the use of cloud server resources, and then determine whether to expand or shrink capacity. The capacity scheduling engine is used for application deployment, firewall settings, WebApi site settings, configuration file deployment, business difference package deployment, process information registration, and server routing startup, deactivation, etc. Different regional data centers correspond to different configuration files. Deploying back-end service applications through the corresponding regional data centers requires configuration files corresponding to the regional data center. Different service types can also correspond to different configuration files. For example, the service gateway configuration file, high-speed service engine class configuration file, and asynchronous task configuration file of the Beijing charging data center, the service gateway configuration file, high-speed service engine class configuration file, and asynchronous task configuration file of the Shanghai charging data center. In addition, embodiments of the present application may also include application process deployment templates (i.e., deployment templates of application instances) corresponding to each service type, which may include service gateway application deployment templates, high-speed service engine application deployment templates, asynchronous task application deployment templates, WebApi site application deployment templates, and other types of application deployment templates.

[0067] Among them, the embodiment of the present application provides multiple types of back-end service application templates. When expanding capacity, the system quickly deploys corresponding templates according to the service type (such as service gateway class, high-speed service engine class, asynchronous task application, etc.) to improve resource utilization efficiency and deployment efficiency. Each template is optimized to ensure that user requests can be quickly responded to under high concurrency. For example, for the service gateway class, the WebApi site will be automatically registered, the firewall port exception will be opened, and the site routing will be enabled. In addition, custom configuration of cloud service areas is supported. Considering that the configuration parameters of different cloud service areas may be different, this solution supports setting custom parameters for each area. For example, for the Beijing Charging Data Center, its configuration center address is bj.configcenter.domain. After the back-end service application completes the expansion deployment, the system will automatically adjust the configuration center parameters of the application process to the corresponding regional address to ensure the optimal service performance of each area. In addition, differentiated deployment packages are supported. For the personalized needs of specific businesses, the embodiment of the present application supports the use of differentiated deployment packages. After basic deployment through the general application template, the system will automatically add and deploy differentiated deployment packages for specific business needs. For example, the settlement business may need to integrate the bank-enterprise docking SDK. After completing the general deployment of the basic service gateway application, the system automatically deploys the relevant SDK (Software Development Kit) program files to ensure business integrity. This can improve the flexibility and scalability of the business and facilitate the iteration and update of later functions.

[0068] In addition, the embodiment of the present application provides an alarm mechanism for server downtime, which can monitor the server status in real time. Once the server is found to be down unexpectedly, the original server is determined as a faulty node, and requests are prohibited from being dispatched to the faulty node. If capacity expansion is required, the system will quickly deploy the application process on the new server based on the type of backend service process deployed on the original server. This mechanism ensures the rapid recovery of the business after a failure occurs and improves the availability of the overall system. A heartbeat monitoring mechanism can be implemented to regularly check the server status to ensure that problems are discovered and handled in a timely manner.

[0069] In this example, dynamic capacity management scheduling is implemented. Before the whole network promotion or regional promotion activities, the system will formulate a dynamic capacity management scheduling plan and automatically evaluate the business applications with tight resources. According to the evaluation results, the system will complete the expansion deployment of the new server application process before the event and go online. After the event, the system will automatically shrink the relevant application processes to optimize resource usage and reduce costs. For example, before the Double Eleven promotion, the system automatically increases the processing capacity of the charging service to ensure that user requests can be processed in a timely manner. In addition, capacity management scheduling can also be performed regularly. In order to cope with the daily charging traffic peak, the system will regularly perform capacity management scheduling. For the identified application processes with tight resources, the system will automatically expand and deploy before the daily traffic peak to ensure efficient operation of the business. After the traffic peak, the system will automatically shrink to avoid resource waste and improve resource utilization efficiency. This embodiment adopts a planned task mechanism. The system analyzes the peak time period based on historical data, intelligently schedules resources, and avoids manual intervention.

[0070] It should be pointed out that with the popularity of electric vehicles and the development of charging infrastructure, high-concurrency charging services have gradually become an important part of the market. These services are usually deployed under the cloud service architecture to support the growing user demand. However, in order to ensure that the service level agreement (SLA) reaches 99.999%, the backend service faces multiple challenges, including but not limited to: Unexpected server downtime: Cloud servers may unexpectedly downtime during operation due to hardware failure, software crash or network problems, which will affect the high availability of the business and thus lead to a decline in user experience. Daily charging traffic peak: During a certain period of time every day (such as rush hour), the charging demand will increase significantly, and the backend service resources will be tight. If not handled properly, it may cause queuing and delays in user requests. Network-wide promotion or regional activities: During large-scale promotional activities, the charging traffic may increase several times. At this time, it is crucial to ensure the stability and response speed of the service to avoid service crashes due to excessive load. Idle resources during holidays: During long holidays, the demand for charging may decrease, resulting in the general idleness of cloud server resources, resulting in resource waste and unfavorable control of operating costs. Diversified business types: Different application process types have different deployment steps, and the traditional one-size-fits-all service deployment method is difficult to meet diverse needs.

[0071] The dynamic capacity management solution provided in the embodiment of the present application fully considers the various challenges of high-concurrency charging services in the cloud service environment. By supporting multiple service application templates, regional custom configurations, differentiated deployment packages, downtime alarm mechanisms, dynamic scheduling management and other functions, the high availability and flexibility of back-end services are achieved, the flexibility and high availability of back-end services are improved, and user needs are met to the greatest extent. This can not only improve user experience, but also effectively reduce operating costs, and has good market application prospects.

[0072] See also Figure 3 As shown, the embodiment of the present application discloses a service application scheduling device, including:

[0073] A service type determination module 11 is used to determine the service type of the backend service application to obtain a target service type when the backend service application meets a preset expansion condition;

[0074] A deployment template acquisition module 12, configured to acquire a deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types;

[0075] An application instance deployment module 13, configured to deploy a target number of application instances corresponding to the backend service application based on the target deployment template;

[0076] The differentiated deployment module 14 is configured to perform differentiated deployment of the application instance based on the differentiated deployment package if there is a differentiated deployment package corresponding to the backend service application.

[0077] The device also includes a regional configuration module for adjusting the regional address parameters of the application instance to schedule access requests of the area corresponding to the regional address parameters to the application instance, and the regional data center corresponding to the regional address parameters provides operating resources for the application instance.

[0078] Among them, the service types include service gateway class, high-speed service engine class and asynchronous task application class, among which the backend service application of the high-speed service engine class is a service application using the TCP protocol, and the backend service application of the asynchronous task application class is a service application that consumes tasks in the task queue, and the task is a task generated based on the request initiated by the requester.

[0079] In an optional implementation, the device further includes a preset expansion condition judgment module for identifying the current resource usage of the backend service application; and judging whether the backend service application meets the preset expansion condition based on the resource usage.

[0080] In an optional implementation, the preset capacity expansion condition is that the current time reaches a preset time point, and the preset time point is a time point at which capacity expansion is required, determined based on historical data.

[0081] The device also includes a shrinking module, which is used to determine a target application instance from each of the application instances and delete the target application instance when the backend service application meets a preset shrinking condition.

[0082] The device also includes a fault processing module, which is used to determine the downed server as a fault node when the server running any application instance crashes, so as to prohibit the access request from being dispatched to the any application instance.

[0083] It can be seen that the embodiment of the present application provides deployment templates for each service type through a preset template library. When expanding capacity, application instances are deployed based on the deployment templates corresponding to each service type, and differentiated deployment is provided, so that various types of back-end service applications in the business system can be expanded quickly, thereby ensuring the stability and response speed of the service, and avoiding service crashes due to excessive load.

[0084] Furthermore, an embodiment of the present application discloses a computer program product, which, when executed, implements the service application scheduling method disclosed in the aforementioned embodiment.

[0085] For the specific process of the above-mentioned service application scheduling method, reference may be made to the corresponding contents disclosed in the above-mentioned embodiments, which will not be described in detail here.

[0086] See also Figure 4 As shown, an embodiment of the present application discloses an electronic device 20, including a processor 21 and a memory 22; wherein the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, and the service application scheduling method disclosed in the above embodiment.

[0087] For the specific process of the above-mentioned service application scheduling method, reference may be made to the corresponding contents disclosed in the above-mentioned embodiments, which will not be described in detail here.

[0088] Furthermore, the memory 22 as a carrier for storing resources may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the storage method may be temporary storage or permanent storage.

[0089] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25 and a communication bus 26; wherein the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input / output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0090] Furthermore, an embodiment of the present application also discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the service application scheduling method disclosed in the aforementioned embodiment.

[0091] For the specific process of the above-mentioned service application scheduling method, reference may be made to the corresponding contents disclosed in the above-mentioned embodiments, which will not be described in detail here.

[0092] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0093] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0094] The above is a detailed introduction to a service application scheduling method, device, equipment and medium provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A service application scheduling method, characterized in that: include: When the backend service application meets the preset expansion condition, determining the service type of the backend service application to obtain a target service type; Acquire a deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types; Deploy a target number of application instances corresponding to the backend service application based on the target deployment template; If there is a differentiated deployment package corresponding to the backend service application, differentiated deployment of the application instance is performed based on the differentiated deployment package.

2. The service application scheduling method according to claim 1, characterized in that: After deploying the target number of application instances corresponding to the backend service application based on the target deployment template, the method further includes: The regional address parameter of the application instance is adjusted to dispatch the access request of the region corresponding to the regional address parameter to the application instance, and the regional data center corresponding to the regional address parameter provides operating resources for the application instance.

3. The service application scheduling method according to claim 1, characterized in that: The service types include service gateway class, high-speed service engine class and asynchronous task application class, wherein the backend service application of the high-speed service engine class is a service application using the TCP protocol, and the backend service application of the asynchronous task application class is a service application that consumes tasks in a task queue, and the task is a task generated based on a request initiated by the requester.

4. The service application scheduling method according to claim 1, characterized in that: Also includes: Identify current resource usage of the backend service application; Based on the resource usage, it is determined whether the backend service application meets a preset expansion condition.

5. The service application scheduling method according to claim 1, characterized in that: The preset expansion condition is that the current time reaches a preset time point, and the preset time point is a time point at which expansion is required, determined based on historical data.

6. The service application scheduling method according to claim 1, characterized in that: Also includes: When the backend service application meets the preset shrinking condition, a target application instance is determined from the application instances, and the target application instance is deleted.

7. The service application scheduling method according to any one of claims 1 to 6, characterized in that: Also includes: When a server running any application instance crashes, the crashed server is determined as a faulty node to prohibit the access request from being dispatched to the any application instance.

8. A service application scheduling device, characterized in that: include: A service type determination module, configured to determine the service type of the backend service application to obtain a target service type when the backend service application meets a preset expansion condition; A deployment template acquisition module, used to acquire the deployment template corresponding to the target service type from a preset template library to obtain a target deployment template, wherein the preset template library includes deployment templates of different service types; An application instance deployment module, used to deploy a target number of application instances corresponding to the backend service application based on the target deployment template; The differentiated deployment module is used to perform differentiated deployment of the application instance based on the differentiated deployment package if there is a differentiated deployment package corresponding to the backend service application.

9. A computer program product, characterized in that When the computer program product is executed, the service application scheduling method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store the computer program; The processor is used to execute the computer program to implement the service application scheduling method according to any one of claims 1 to 7.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the service application scheduling method according to any one of claims 1 to 7 is implemented.

Images