CN114296925A - File type identification system and method based on micro-service architecture - Google Patents
File type identification system and method based on micro-service architecture Download PDFInfo
- Publication number
- CN114296925A CN114296925A CN202111638356.4A CN202111638356A CN114296925A CN 114296925 A CN114296925 A CN 114296925A CN 202111638356 A CN202111638356 A CN 202111638356A CN 114296925 A CN114296925 A CN 114296925A
- Authority
- CN
- China
- Prior art keywords
- micro
- service
- management module
- file
- load
- 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 32
- 238000012544 monitoring process Methods 0.000 claims abstract description 28
- 230000000977 initiatory effect Effects 0.000 claims description 9
- 230000003247 decreasing effect Effects 0.000 claims description 6
- 230000007423 decrease Effects 0.000 claims description 5
- 230000004044 response Effects 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 72
- 238000010586 diagram Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Abstract
The application provides a file type identification system and method based on a micro-service architecture. The identification request module initiates a file identification request to the management module, and the management module responds to the file identification request, generates a file identification task and starts up the micro-service. The monitoring module acquires the load of the micro-service and sends the load to the management module. The management module preferentially allocates the file identification task to the micro-service with low load. The management module sets a load threshold value, and when the load capacity of all the micro-services exceeds the load threshold value, the management module dynamically starts one micro-service. And when the dynamically started micro service does not acquire the file identification task for n times continuously, the management module releases the micro service. According to the method and the system, file type identification is achieved in a micro-service architecture mode, the number of micro-services can be automatically adjusted according to the number of file identification tasks, and system resources are reasonably utilized.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a file type identification system and method based on a micro service architecture.
Background
In order to maintain network information security, in the processes of firewall, network behavior audit and the like, the type of a transmission file of network equipment needs to be identified, and then the transmission file passing through the equipment is filtered or intercepted according to the file type information.
The file type identification needs to load a file type identification feature library into a memory, and a file to be identified is compared with the file type identification feature library to obtain a file suffix. In the traditional file type identification method, a file type identification feature library is loaded in a fixed system resource to process a file type identification task.
However, the file type identification task does not always exist, that is, the timing for identifying the file type is uncertain, and the amount of the file type identification task is difficult to predict. When the file type identification tasks are few or no, system resources are wasted, and when the file type identification tasks are increased rapidly, reasonable capacity expansion cannot be achieved, so that congestion is caused.
Disclosure of Invention
The application provides a file type identification system and method based on a micro-service architecture, which aim to solve the problem of unbalanced system resource distribution when identifying file types.
In one aspect, the present application provides a file type identification system based on a micro service architecture, including: the system comprises an identification request module, a management module, a monitoring module and a plurality of micro services.
The identification request module is configured to initiate a file identification request to the management module. The file identification request is used for starting the management module to start to identify the file type.
The management module is configured to generate a document identification task in response to the document identification request. The file identification task comprises file information to be identified. And starting the monitoring module. And starting the micro service, and distributing the file identification task to the micro service.
The microservice is configured to process the file identification task, obtain a task processing result, and send the task processing result to the management module.
The monitoring module is configured to acquire a load amount of the micro service and send the load amount to the management module. The load is the number of the file identification tasks cached by the micro-service.
The management module is configured to increase or decrease the number of the micro-services according to the load amount of the micro-services.
In one implementation, at least one of the microservices is automatically launched upon receipt of the file identification request by the management module. And when the management module is started, at least one micro service is loaded according to configuration defaults, so that the micro service is prevented from being dynamically loaded when the file identification tasks are few.
In one implementation, in the step of processing the file identification task and obtaining a task processing result, the microservice is further configured to:
and loading the file type identification feature library into a system memory.
Initiating a registration message to the management module.
And initiating a task processing request to the management module to acquire the file identification task.
And inquiring the file type identification feature library to obtain a task processing result.
After the micro service sends the task processing result to the management module, the management module feeds the task processing result back to the identification request module, and the identification request module sends the processing result to other programs for subsequent processing, such as receiving or intercepting.
In one implementation, in the step of initiating a microservice and assigning the file identification task to the microservice, the management module is configured to:
and acquiring the registration message and loading the micro service into a micro service queue.
And acquiring the load of each micro service in the micro service queue from the monitoring module.
And preferentially distributing the file identification task to the micro-service with low load.
After the micro service acquires the file identification task, caching the file identification task in a task list of the micro service, and sequentially processing the file identification task. And each micro-service task list automatically records the number of the file identification tasks currently cached by the micro-service, namely the load capacity of the micro-service.
In one implementation, in the step of increasing or decreasing the number of the micro services according to the load amount of the micro services, the management module is configured to:
a load threshold is set.
If the load amount of all the micro services in the micro service queue exceeds the load threshold value.
Dynamically launching a new one of said microservices.
In one implementation, in the step of increasing or decreasing the number of the micro services according to the load amount of the micro services, the management module is further configured to:
and if the micro service is the idle micro service, releasing the idle micro service. The no-load micro service is the micro service which is not obtained the file identification task for n times continuously and is started dynamically.
In one implementation, the management module is configured to set a maximum boot number, and when the number of the microservices reaches the maximum boot number, no new microservices are booted.
The management module sets the maximum starting number, and prevents the system resources occupied by the equipment from continuously increasing when the equipment is attacked maliciously until the equipment cannot run due to resource exhaustion. If a large number of file identification tasks do exist currently, the maximum starting number can be manually configured to meet the task processing requirements.
On the other hand, the application also provides a file type identification method based on the micro-service architecture, which is applied to the file type identification system based on the micro-service architecture, and the system comprises an identification request module, a management module, a monitoring module and a plurality of micro-services. The method comprises the following steps:
the management module receives a file identification request initiated by the identification request module;
the management module responds to the file identification request to generate a file identification task; starting the monitoring module; starting the micro service, and distributing the file identification task to the micro service;
the management module receives the task processing result generated by the file identification task processed by the microservice;
the management module receives the load of the micro service acquired by the monitoring module; the load is the number of the file identification tasks cached by the micro-service;
the management module increases or decreases the number of the micro-services according to the load amount of the micro-services.
In one implementation, the initiating, by the management module, the microservice and the assigning the file identification task to the microservice includes:
loading the microservice to a microservice queue;
acquiring the load of each micro service in the micro service queue from the monitoring module;
and preferentially distributing the file identification task to the micro-service with low load.
In one implementation, the increasing or decreasing the number of the micro-services according to the load amount of the micro-services by the management module includes:
setting a load threshold;
if the load amount of all the micro services in the micro service queue exceeds the load threshold value;
dynamically starting a new one of the microservices;
if the micro service is the idle micro service, releasing the idle micro service; the no-load micro service is the micro service which is not obtained the file identification task for n times continuously and is started dynamically.
The file type identification system based on the micro-service architecture comprises an identification request module, a management module, a monitoring module and a plurality of micro-services. The identification request module is used for initiating a file identification request to the management module, and the management module responds to the file identification request, generates a file identification task and starts the micro-service at the same time. The monitoring module is used for acquiring the load of the micro service and sending the load to the management module. And the management module allocates the file identification tasks according to the load and preferentially allocates the file identification tasks to the micro-services with low load. And adjusting the number of the micro-services according to the load, setting a load threshold value by the management module, and dynamically starting one micro-service by the management module when the load of all the micro-services exceeds the load threshold value. And when the dynamically started micro service does not acquire the file identification task for n times, the management module releases the micro service.
According to the file type identification method and device, the file type identification is achieved in a micro-service architecture mode, namely the file type identification processing is carried out in a multi-process mode, and the processing efficiency is improved. And the number of the micro-services can be automatically adjusted according to the number of the file identification tasks, the micro-services are increased when the number of the tasks is large, and the micro-services are reduced when the number of the tasks is small or no file identification tasks exist, so that system resources are reasonably utilized.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a file type identification system based on a micro service architecture according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a microservice queue according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a workflow of a management module according to an embodiment of the present application;
fig. 4 is a schematic view of a working flow of a monitoring module according to an embodiment of the present application;
fig. 5 is a schematic view of a micro-service operation flow provided in an embodiment of the present application;
fig. 6 is a flowchart of a file type identification method based on a micro service architecture according to an embodiment of the present application;
FIG. 7 is a flowchart of a task allocation method for a management module according to an embodiment of the present application;
fig. 8 is a flowchart of a micro service management method according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following examples do not represent all embodiments consistent with the present application. But merely as exemplifications of systems and methods consistent with certain aspects of the application, as recited in the claims.
Microservice is a variation of the service-oriented architectural style that calls for a single application to be divided into a set of small services that are coordinated and interworked with each other. Each service runs in its own independent process, each built around a specific business.
In order to maintain the security of network information, it is usually necessary to identify the type of file transmitted by the network device, to determine whether the transmitted file is secure, and to perform corresponding processing. However, in the conventional file type identification method, a file type identification program is usually loaded on a fixed system resource, and when a file type identification task is increased suddenly, reasonable capacity expansion cannot be performed, so that the processing is slow, and when the file type identification task is reduced, system resource waste is caused. Based on this, the embodiment of the application provides a file type identification system and method based on a micro-service architecture, which automatically adjust the number of started micro-services according to the file type identification task quantity, and reasonably utilize system resources. The method and the device can be applied to services aiming at file type identification on network equipment such as firewall equipment, switches, routers and behavior auditing, and are not limited in the embodiment of the application.
The embodiment provides a file type identification system based on a micro-service architecture. Referring to fig. 1, the file type identification system based on the microservice architecture provided by this embodiment includes an identification request module, a management module, a listening module, and a plurality of microservices. The identification request module is configured to initiate a file identification request to the management module when the file type identification is required, generate a unique file identification request ID, and start the management module to start the file type identification. The management module is configured to respond to the file identification request and generate a corresponding file identification task according to the file identification request ID, wherein the file identification task comprises file information to be identified.
Referring to fig. 3, the management module starts the listening module and self-starts at least one of the micro-services, assigning the file identification task to the micro-service. And when the management module is started, at least one micro service is loaded according to configuration defaults, so that the micro service is prevented from being dynamically loaded when the file identification tasks are few.
Referring to fig. 5, after the micro service is started, the file type identification feature library is loaded into a system memory, then a registration message is initiated to the management module, and after receiving the registration message, the management module loads the micro service into a micro service queue. The microservice queue structure provided by the embodiment of the present application is shown in fig. 2. And when file identification is needed, the management module distributes the file identification task to the micro-service in the micro-service queue.
And after the micro service finishes registration, a task processing request is initiated to the management module at regular time, and after the management module receives the task processing request, the file identification task is distributed to the micro service. After the micro service acquires the file identification task, the file type identification feature library is inquired for the file information to be identified in the file identification task, and a task processing result, namely a file suffix, is acquired. And sending the task processing result to the management module, feeding the task processing result back to the identification request module by the management module, and sending the processing result to other programs by the identification request module for subsequent processing, such as receiving or intercepting.
After the micro service acquires the file identification task, caching the file identification task in a task list of the micro service, and sequentially processing the file identification task. And each micro-service task list automatically records the number of the file identification tasks currently cached by the micro-service, namely the load capacity of the micro-service. Referring to fig. 4, the monitoring module is configured to monitor the actions of the micro service, obtain monitoring information, where the monitoring information includes the registration information, the task processing request, the task processing result, the load amount of the micro service, and the like sent by the micro service, and send the monitoring information to the management module in real time.
When the file type identification task is distributed, the management module obtains the load of all the micro services in the micro service queue, compares the load, preferentially distributes the file type identification task to the micro service with the lowest load, and reasonably distributes system resources.
The management module manages the micro-services according to the number of the file identification tasks, firstly, the management module sets a load threshold, then, the load of all the micro-services is compared with the load threshold, if the load of all the micro-services exceeds the load threshold, the number of the file identification tasks is proved to be large, at the moment, the management module dynamically starts one micro-service to share the file identification tasks, and the processing efficiency is improved. And the load threshold is set according to the size of the memory space occupied by the file identification task and the size of the memory space occupied by the file type identification feature library loaded by the micro service. For example, if one of the file identification tasks occupies a maximum memory space of 2K, and the file type identification feature library loaded by each micro service occupies about 4M of the memory, the load threshold may be set to 512 of the number of the file identification tasks cached by each micro service.
The management module sets the maximum starting number of the micro-services, when the number of the micro-services reaches the maximum starting number, the management module does not start the micro-services any more, and prevents the system resources occupied by the equipment from continuously increasing when the equipment is attacked maliciously until the equipment is exhausted. The maximum starting number is set according to the memory size of the current system, for example, the maximum starting number may be set to 8 when the memory resource is 2G, and the maximum starting number may be set to 16 when the memory resource is 4G. If a large number of file identification tasks do exist currently, the maximum starting number can be manually configured to meet the task processing requirements.
If the dynamically started micro-service does not acquire the file identification task for n times continuously, namely the micro-service is the no-load micro-service, the fact that the number of the current file identification tasks is small or the file identification tasks do not exist is proved, the management module releases the no-load micro-service, and system resource occupation is reduced.
The embodiment also provides a file type identification method based on the micro-service architecture, and the method is applied to the file type identification system. Referring to fig. 6, the method steps include:
the management module receives a file identification request initiated by the identification request module;
the management module responds to the file identification request to generate a file identification task; starting the monitoring module; starting the micro service, and distributing the file identification task to the micro service;
referring to fig. 7, the specific steps of the management module assigning the file identification task to the microservice include: loading the microservice to a microservice queue; acquiring the load of each micro service in the micro service queue from the monitoring module; and preferentially distributing the file identification task to the micro-service with low load.
The management module receives the task processing result generated by the file identification task processed by the microservice;
the management module receives the load of the micro service acquired by the monitoring module; the load is the number of the file identification tasks cached by the micro-service;
the management module increases or decreases the number of the micro-services according to the load amount of the micro-services.
Referring to fig. 8, the specific steps of the management module managing the number of the micro services include: setting a load threshold; if the load amount of all the micro services in the micro service queue exceeds the load threshold value; dynamically starting a new one of the microservices; if the micro service is the idle micro service, releasing the idle micro service; the no-load micro service is the micro service which is not obtained the file identification task for n times continuously and is started dynamically.
The embodiment of the application provides a file type identification system and method based on a micro-service architecture. The identification request module is used for initiating a file identification request to the management module, and the management module responds to the file identification request, generates a file identification task and starts the micro-service at the same time. The monitoring module is used for acquiring the load of the micro service and sending the load to the management module. And the management module allocates the file identification tasks according to the load and preferentially allocates the file identification tasks to the micro-services with low load. And adjusting the number of the micro-services according to the load, setting a load threshold value by the management module, and dynamically starting one micro-service by the management module when the load of all the micro-services exceeds the load threshold value. And if the dynamically started micro service does not acquire the file identification task for n times, the management module releases the micro service.
According to the file type identification method and device, the file type identification is achieved in a micro-service architecture mode, namely the file type identification processing is carried out in a multi-process mode, and the processing efficiency is improved. And the number of the micro-services can be automatically adjusted according to the number of the file identification tasks, the micro-services are increased when the number of the tasks is large, and the micro-services are reduced when the number of the tasks is small or no file identification tasks exist, so that system resources are reasonably utilized.
The embodiments provided in the present application are only a few examples of the general concept of the present application, and do not limit the scope of the present application. Any other embodiments extended according to the scheme of the present application without inventive efforts will be within the scope of protection of the present application for a person skilled in the art.
Claims (10)
1. A file type identification system based on micro-service architecture is characterized by comprising: the system comprises an identification request module, a management module, a monitoring module and a plurality of micro services;
the identification request module is configured to initiate a file identification request to the management module; the file identification request is used for starting the management module to start to identify the file type;
the management module is configured to generate a file identification task in response to the file identification request; the file identification task comprises file information to be identified; starting the monitoring module; starting the micro service, and distributing the file identification task to the micro service;
the microservice is configured to process the file identification task, obtain a task processing result, and send the task processing result to the management module;
the monitoring module is configured to acquire the load of the micro service and send the load to the management module; the load is the number of the file identification tasks cached by the micro-service;
the management module is configured to increase or decrease the number of the micro-services according to the load amount of the micro-services.
2. The microservice-based architecture-based document type identification system of claim 1, wherein at least one of the microservices is automatically launched upon receipt of the document identification request by the management module.
3. The microservice-architecture-based file type identification system of claim 2, wherein in the step of processing the file identification task to obtain task processing results, the microservice is further configured to:
loading a file type identification feature library into a system memory;
initiating a registration message to the management module;
initiating a task processing request to the management module to acquire the file identification task;
and inquiring the file type identification feature library to obtain a task processing result.
4. The microservice-architecture-based file type identification system of claim 3, wherein in the step of initiating a microservice and assigning the file identification task to the microservice, the management module is configured to:
acquiring the registration message, and loading the micro service into a micro service queue;
acquiring the load of each micro service in the micro service queue from the monitoring module;
and preferentially distributing the file identification task to the micro-service with low load.
5. The microservice architecture-based file type identification system of claim 4, wherein in the step of increasing or decreasing the number of microservices according to the load amount of the microservices, the management module is configured to:
setting a load threshold;
if the load amount of all the micro services in the micro service queue exceeds the load threshold value;
dynamically launching a new one of said microservices.
6. The microservice architecture-based file type identification system of claim 5, wherein in the step of increasing or decreasing the number of microservices according to the load amount of the microservices, the management module is further configured to:
if the micro service is the idle micro service, releasing the idle micro service; the no-load micro service is the micro service which is not obtained the file identification task for n times continuously and is started dynamically.
7. The microservice architecture-based file type identification system of claim 5, wherein the management module is configured to set a maximum startup number, wherein when the number of microservices reaches the maximum startup number, new microservices are not started.
8. A file type identification method based on a micro-service architecture is applied to the file type identification system based on the micro-service architecture, which is disclosed by any one of claims 1 to 7, and comprises an identification request module, a management module, a monitoring module and a plurality of micro-services; characterized in that the method comprises:
the management module receives a file identification request initiated by the identification request module;
the management module responds to the file identification request to generate a file identification task; starting the monitoring module; starting the micro service, and distributing the file identification task to the micro service;
the management module receives the task processing result generated by the file identification task processed by the microservice;
the management module receives the load of the micro service acquired by the monitoring module; the load is the number of the file identification tasks cached by the micro-service;
the management module increases or decreases the number of the micro-services according to the load amount of the micro-services.
9. The file type identification method based on the microservice architecture as claimed in claim 8, wherein said management module starts the microservice and allocates the file identification task to the microservice, comprising:
loading the microservice to a microservice queue;
acquiring the load of each micro service in the micro service queue from the monitoring module;
and preferentially distributing the file identification task to the micro-service with low load.
10. The method of claim 9, wherein the increasing or decreasing the number of the micro services according to the loading amount of the micro services by the management module comprises:
setting a load threshold;
if the load amount of all the micro services in the micro service queue exceeds the load threshold value;
dynamically starting a new one of the microservices;
if the micro service is the idle micro service, releasing the idle micro service; the no-load micro service is the micro service which is not obtained the file identification task for n times continuously and is started dynamically.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111638356.4A CN114296925A (en) | 2021-12-29 | 2021-12-29 | File type identification system and method based on micro-service architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111638356.4A CN114296925A (en) | 2021-12-29 | 2021-12-29 | File type identification system and method based on micro-service architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114296925A true CN114296925A (en) | 2022-04-08 |
Family
ID=80970673
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111638356.4A Pending CN114296925A (en) | 2021-12-29 | 2021-12-29 | File type identification system and method based on micro-service architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114296925A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9716617B1 (en) * | 2016-06-14 | 2017-07-25 | ShieldX Networks, Inc. | Dynamic, load-based, auto-scaling network security microservices architecture |
| CN108418862A (en) * | 2018-01-31 | 2018-08-17 | 金蝶软件（中国）有限公司 | Micro services management method and system based on artificial intelligence service cloud platform |
| CN108712464A (en) * | 2018-04-13 | 2018-10-26 | 中国科学院信息工程研究所 | A kind of implementation method towards cluster micro services High Availabitity |
| CN112000448A (en) * | 2020-07-17 | 2020-11-27 | 北京计算机技术及应用研究所 | Micro-service architecture-based application management method |
| CN112202829A (en) * | 2019-07-08 | 2021-01-08 | 北京邮电大学 | Social robot scheduling system and scheduling method based on micro-service |
-
2021
- 2021-12-29 CN CN202111638356.4A patent/CN114296925A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9716617B1 (en) * | 2016-06-14 | 2017-07-25 | ShieldX Networks, Inc. | Dynamic, load-based, auto-scaling network security microservices architecture |
| CN108418862A (en) * | 2018-01-31 | 2018-08-17 | 金蝶软件（中国）有限公司 | Micro services management method and system based on artificial intelligence service cloud platform |
| CN108712464A (en) * | 2018-04-13 | 2018-10-26 | 中国科学院信息工程研究所 | A kind of implementation method towards cluster micro services High Availabitity |
| CN112202829A (en) * | 2019-07-08 | 2021-01-08 | 北京邮电大学 | Social robot scheduling system and scheduling method based on micro-service |
| CN112000448A (en) * | 2020-07-17 | 2020-11-27 | 北京计算机技术及应用研究所 | Micro-service architecture-based application management method |
Non-Patent Citations (3)
| Title |
|---|
| FANGZHOU WAN等: ""Chain-Oriented Load Balancing in Microservice System"", 《2020 WORLD CONFERENCE ON COMPUTING AND COMMUNICATION TECHNOLOGIES (WCCCT)》 * |
| 张开琦等: "基于动态权重的一致性哈希微服务负载均衡优化", 《计算机工程与科学》 * |
| 王孝宇: ""基于微服务架构的敏捷开发平台安全机制的设计与实现"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105335231B (en) | server thread dynamic allocation method and device | |
| CN114070822B (en) | Kubernetes Overlay IP address management method | |
| CN111431970B (en) | Resource allocation method, device, equipment and storage medium based on micro-service architecture | |
| US11438271B2 (en) | Method, electronic device and computer program product of load balancing | |
| CN114615340B (en) | Request processing method and device, computer equipment and storage device | |
| CN110764908A (en) | Load adjusting method and device, server and storage medium | |
| CN113900774B (en) | Virtual machine control method and device of cloud operating system and storage medium | |
| CN110489227B (en) | Resource allocation method, device, computer equipment and storage medium | |
| CN111586140A (en) | Data interaction method and server | |
| CN113626213A (en) | Event processing method, device and equipment and computer readable storage medium | |
| CN114296925A (en) | File type identification system and method based on micro-service architecture | |
| CN111294220B (en) | Nginx-based network isolation configuration method and device | |
| CN101018152A (en) | Software installation system and method | |
| CN114979286B (en) | Access control method, device, equipment and computer storage medium for container service | |
| JP2016506189A (en) | Resource allocation method and apparatus | |
| CN114172903A (en) | Node capacity expansion method, device, equipment and medium of slarm scheduling system | |
| CN115220993A (en) | Process monitoring method, device, vehicle and storage medium | |
| CN114924888A (en) | Resource allocation method, data processing method, device, equipment and storage medium | |
| CN114745377A (en) | Edge cloud cluster service system and implementation method | |
| CN112153093B (en) | Cluster-based task scheduling method, device, equipment and readable storage medium | |
| CN109257227B (en) | Coupling management method, device and system in data transmission | |
| CN111782364A (en) | Service calling method and device, electronic equipment and storage medium | |
| CN112328598A (en) | ID generation method, device, electronic equipment and storage medium | |
| CN112395063A (en) | Dynamic multithreading scheduling method and system | |
| CN113204434B (en) | Planned task execution method and device based on k8s and computer equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220408 |
|
| RJ01 | Rejection of invention patent application after publication |