WO2019209231A2 - System and method for creating recommendation of splitting and merging microservice - Google Patents
System and method for creating recommendation of splitting and merging microservice Download PDFInfo
- Publication number
- WO2019209231A2 WO2019209231A2 PCT/TR2019/050277 TR2019050277W WO2019209231A2 WO 2019209231 A2 WO2019209231 A2 WO 2019209231A2 TR 2019050277 W TR2019050277 W TR 2019050277W WO 2019209231 A2 WO2019209231 A2 WO 2019209231A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- microservice
- unit
- data
- splitting
- merging
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
Definitions
- the present invention relates to a system for observing microservices in systems running by microservice architecture by taking into consideration various parameters, and for creating recommendations intended for splitting or merging microservices accordingly.
- Microservice architecture -use of which becomes widespread increasingly today- consists of microservices which are atomic services with development processes, dependencies, sizes as small as possible. Big works are divided into small parts, load distribution is made and it is ensured that the system keeps up while transitions are being performed in systems having critical importance by means of microservices. Transactions of merging a microservice with other microservices or splitting it into several microservices is carried out by taking into consideration factors such as network security, risk management, user/role appraisal, performance, dependencies, resource consumption, the network being used, technologies being used, frequency of deployment, business model, function and rules, frequency of use, software standards, intra-team dynamics writing the application, usage calendar. However, it is required to review the microservice design after any update, modification or maintenance.
- test data can be stored in a server and/or sent to a data analysis server.
- the data analysis server analyses the test data and creates recommendations for splitting or merging microservices.
- the data analysis server can be located on the server as a module, on another server or it can be an independent server. Microservices are analysed by looking at their independent functionalities and functional responsibilities, in order to determine whether they should be split or merged.
- the data analysis server determines that microservice performs functions A and B and creates a recommendation for splitting the microservice into two for function A and function B. Similarly, the data analysis server determines that microservices A and B perform the same X function and creates a recommendation for merging microservice B with microservice A.
- An objective of the present invention is to realize a system for creating recommendations intended for splitting or merging microservices by carrying out analysis on various data about current microsystems in systems running by microservice architecture.
- Another objective of the present invention is to realize a system for creating simulation scenarios and ensuring that these scenarios are used for creating recommendation intended for splitting or merging microservices.
- Figure 1 is a schematic view of the inventive system.
- FIG. 2 is a flowchart of the inventive method.
- the system (1) for creating recommendation of splitting and merging microservice comprises:
- microservice monitoring unit (2) which is configured such that it will make observation on current microservices by connecting to the microservice servers (MSS);
- At least one data storage unit (3) which is in communication with the microservice monitoring unit (2) and stores the data about the microservices; at least one data processing unit (4) which enables to carry out various analyses on the stored data;
- At least one simulation unit (5) which is configured such that it will determine simulation will be used for recommendation of splitting and merging microservice, and will create the related recommendation when it is decided to use simulation;
- At least one recommendation unit (6) which is in communication with the data processing unit (4) and the simulation unit (5) and creates recommendations intended for splitting the monitored microservice into several microservice or merging them with other microservices;
- the microservice monitoring unit (2) included in the inventive system (1) is a unit which enables to monitor each microservice.
- the data storage unit (3) included in the inventive system (1) is in communication with the microservice monitoring unit (2) and it instantly stores the data about the microservices monitored by the microservice monitoring unit (2) by connecting to the microservice servers (MSS).
- the data stored in the data storage unit (3) may be data such as whether the service is reliable or not, the resource consumed (use of RAM-random access memory and CPU-central processing unit), size of data carried on network, frequency of call, number of call, from which subnetwork it is called and in which subnetwork it is located, error logs, database servers being connected to, microservices called in itself, ports opened, service performance, service technology, service dependencies, deployment frequency, which team do developments belong to, complexity of the service written, user and role authority, call calendar, response time of function on service, call number of function on service.
- the data processing unit (4) included in the inventive system (1) is in communication with the data storage unit (3) and clears the data not to be used among the data stored in the data storage unit (3). Then, it enables to extract interrelation of data by using various data decomposition and classification methods on the data cleared.
- the data decomposition and classification methods used can be methods such as a decision tree method which is a classification method wherein a tree structure is created to make a decision and probabilities are placed to the leaves of the tree; k-nearest neighbor method which is a classification method wherein proximity of a data -that is requested to be classified- to previous data -which have been placed to a coordinate system- is looked; logistic regression method which is a classification method wherein artificial neural networks, logistics models are created and which is used for probability calculations to estimate dependent variable values; ZeroR algorithm which places a new data to a class having the maximum data among the classes in the data set; OneR algorithm which is a more advanced than ZeroR algorithm and makes classification by creating frequency tables for classes; naive bayesian classification algorithm which is a method wherein test data are classified according to previously obtained probability values; C4.5 algorithm which is a decision tree method performing normalization; ID3 algorithm which divides the data in the decision tree into two parts in the largest way; C4.5 algorithm which is an advanced version of C4.5 algorithm and used by
- the simulation unit (5) included in the inventive system (1) is a unit which determines whether real data or a simulation structure will be used before a recommendation of splitting and merging microservice is created.
- the simulation unit (5) determines microservice features over a current system in the event of deciding that real data will be used.
- the simulation unit (5) creates a system simulation in the event of deciding that a simulation will be used for creating recommendation of splitting and merging microservice.
- results can be obtained such as microservices that should be merged or split in network density changes, change that will occur in use of processor when the microservices are merged, change that will occur in log amounts when the microservices are merged, difference that will occur in response time of microservice in the event that the microservice functions merge or split.
- the recommendation unit (6) included in the inventive system (1) is in communication with the data processing unit (4) and the simulation unit (5). It creates recommendations of splitting and merging microservice on the basis of the information that it receives from the data processing unit (4) and the simulation unit (5).
- the recommendation unit (6) takes into consideration factors such as network security, risk management, user/role appraisal, performance, dependencies, resource consumption, the network being used, technologies being used, frequency of deployment, business model, function and rules, frequency of use, software standards, intra-team dynamics writing the application, usage calendar while it creates recommendation.
- the reporting unit (7) included in the inventive system (1) creates a report in the event that a microservice does not have authority for split or merging autonomously.
- user information and the related microservice comprise two different functions; namely, login and password control.
- the login function is used very often and the function used for reporting may slow down the microservice and causes to receiving late reply upon being used at certain intervals. It may be enabled to split the service by considering the frequency of call of functions of services and the times for responding a call.
- the requested microservices are made high security microservices by interlaying security layers.
- Splitting and merging transaction is carried out in the related server by considering the security layer upon looking at the subnetwork wherein they are located.
- the inventive method (100) creating recommendation of splitting and merging microservice comprises steps of:
- microservice monitoring unit (2) saving the data about the microservices that it receives instantly by connecting to the microservice servers (MSS), to the data storage unit (3) (102),
- the data processing unit parsing the data recorded in the data storage unit (3) and classifying them by using classification methods (103),
- the simulation unit (5) determining whether real data or a system simulation will be used or not and creating the simulation in the event that a system simulation is used (104),
- the recommendation unit (6) creating recommendation of splitting and merging microservice by receiving information about the microservice from the data processing unit (4) and the simulation unit (5) (105),
- the data processing unit (4) giving splitting or merging instruction to the microservice servers (MSS) (106), in the event that the microservice has no authority for splitting or merging autonomously, the reporting unit (7) creating a report (107).
- MSS microservice servers
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computer Hardware Design (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Medicines That Contain Protein Lipid Enzymes And Other Medicines (AREA)
- Peptides Or Proteins (AREA)
- Devices For Executing Special Programs (AREA)
Abstract
The present invention relates to a system for observing microservices in systems running by microservice architecture by taking into consideration various parameters, and for creating recommendations intended for splitting or merging microservices accordingly.
Description
SYSTEM AND METHOD FOR CREATING RECOMMENDATION OF SPLITTING AND MERGING MICROSERVICE
Technical Field
The present invention relates to a system for observing microservices in systems running by microservice architecture by taking into consideration various parameters, and for creating recommendations intended for splitting or merging microservices accordingly.
Background of the Invention Microservice architecture -use of which becomes widespread increasingly today- consists of microservices which are atomic services with development processes, dependencies, sizes as small as possible. Big works are divided into small parts, load distribution is made and it is ensured that the system keeps up while transitions are being performed in systems having critical importance by means of microservices. Transactions of merging a microservice with other microservices or splitting it into several microservices is carried out by taking into consideration factors such as network security, risk management, user/role appraisal, performance, dependencies, resource consumption, the network being used, technologies being used, frequency of deployment, business model, function and rules, frequency of use, software standards, intra-team dynamics writing the application, usage calendar. However, it is required to review the microservice design after any update, modification or maintenance. Management of microservice becomes difficult as the number of microservices increases in the system. In view of difficulties being experienced about management of microservice in the state of the art, it is understood that there is need for a system that will create
recommendation as up-to-date about transactions of splitting and merging microservices.
The United States patent document no. US2017364434, an application in the state of the art, discloses a system which determines whether microservices can be split or not or they can be merged with another microservices or not by using test data about microservices and creates recommendation. In the said system, test data can be stored in a server and/or sent to a data analysis server. The data analysis server analyses the test data and creates recommendations for splitting or merging microservices. The data analysis server can be located on the server as a module, on another server or it can be an independent server. Microservices are analysed by looking at their independent functionalities and functional responsibilities, in order to determine whether they should be split or merged. For example, the data analysis server determines that microservice performs functions A and B and creates a recommendation for splitting the microservice into two for function A and function B. Similarly, the data analysis server determines that microservices A and B perform the same X function and creates a recommendation for merging microservice B with microservice A.
Summary of the Invention
An objective of the present invention is to realize a system for creating recommendations intended for splitting or merging microservices by carrying out analysis on various data about current microsystems in systems running by microservice architecture.
Another objective of the present invention is to realize a system for creating simulation scenarios and ensuring that these scenarios are used for creating recommendation intended for splitting or merging microservices.
Detailed Description of the Invention
“A System and Method for Creating Recommendation of Splitting and Merging Microservice” realized to fulfil the objectives of the present invention is shown in the figures attached, in which:
Figure 1 is a schematic view of the inventive system.
Figure 2 is a flowchart of the inventive method.
The components illustrated in the figure are individually numbered, where the numbers refer to the following:
1. System
2. Microservice monitoring unit
3. Data storage unit
4. Data processing unit
5. Simulation unit
6. Recommendation unit
7. Reporting unit MSS. Microservice server
100. Method
The system (1) for creating recommendation of splitting and merging microservice comprises:
at least one microservice monitoring unit (2) which is configured such that it will make observation on current microservices by connecting to the microservice servers (MSS);
at least one data storage unit (3) which is in communication with the microservice monitoring unit (2) and stores the data about the microservices;
at least one data processing unit (4) which enables to carry out various analyses on the stored data;
at least one simulation unit (5) which is configured such that it will determine simulation will be used for recommendation of splitting and merging microservice, and will create the related recommendation when it is decided to use simulation;
at least one recommendation unit (6) which is in communication with the data processing unit (4) and the simulation unit (5) and creates recommendations intended for splitting the monitored microservice into several microservice or merging them with other microservices;
at least one reporting unit (7) which is in communication with the recommendation unit (6) and configured such that it will report the created recommendation. The microservice monitoring unit (2) included in the inventive system (1) is a unit which enables to monitor each microservice.
The data storage unit (3) included in the inventive system (1) is in communication with the microservice monitoring unit (2) and it instantly stores the data about the microservices monitored by the microservice monitoring unit (2) by connecting to the microservice servers (MSS). The data stored in the data storage unit (3) may be data such as whether the service is reliable or not, the resource consumed (use of RAM-random access memory and CPU-central processing unit), size of data carried on network, frequency of call, number of call, from which subnetwork it is called and in which subnetwork it is located, error logs, database servers being connected to, microservices called in itself, ports opened, service performance, service technology, service dependencies, deployment frequency, which team do developments belong to, complexity of the service written, user and role authority, call calendar, response time of function on service, call number of function on service.
The data processing unit (4) included in the inventive system (1) is in communication with the data storage unit (3) and clears the data not to be used among the data stored in the data storage unit (3). Then, it enables to extract interrelation of data by using various data decomposition and classification methods on the data cleared. The data decomposition and classification methods used can be methods such as a decision tree method which is a classification method wherein a tree structure is created to make a decision and probabilities are placed to the leaves of the tree; k-nearest neighbor method which is a classification method wherein proximity of a data -that is requested to be classified- to previous data -which have been placed to a coordinate system- is looked; logistic regression method which is a classification method wherein artificial neural networks, logistics models are created and which is used for probability calculations to estimate dependent variable values; ZeroR algorithm which places a new data to a class having the maximum data among the classes in the data set; OneR algorithm which is a more advanced than ZeroR algorithm and makes classification by creating frequency tables for classes; naive bayesian classification algorithm which is a method wherein test data are classified according to previously obtained probability values; C4.5 algorithm which is a decision tree method performing normalization; ID3 algorithm which divides the data in the decision tree into two parts in the largest way; C4.5 algorithm which is an advanced version of C4.5 algorithm and used by large data sets; CART (classification®ression trees) algorithm which makes entropy calculations to determine branching in decision tree algorithm and determines classes; LDA (linear discriminant analysis) algorithm which performs linear transformation by using most distinctive attribute sets. The data processing unit (4) knows whether the microservice has authority of splitting or merging autonomously or not and gives splitting or merging instruction to the microservice servers (MSS) in the event that an authority is available.
The simulation unit (5) included in the inventive system (1) is a unit which determines whether real data or a simulation structure will be used before a recommendation of splitting and merging microservice is created. The simulation
unit (5) determines microservice features over a current system in the event of deciding that real data will be used. The simulation unit (5) creates a system simulation in the event of deciding that a simulation will be used for creating recommendation of splitting and merging microservice. With the system simulations created by the simulation unit (5), results can be obtained such as microservices that should be merged or split in network density changes, change that will occur in use of processor when the microservices are merged, change that will occur in log amounts when the microservices are merged, difference that will occur in response time of microservice in the event that the microservice functions merge or split.
The recommendation unit (6) included in the inventive system (1) is in communication with the data processing unit (4) and the simulation unit (5). It creates recommendations of splitting and merging microservice on the basis of the information that it receives from the data processing unit (4) and the simulation unit (5). The recommendation unit (6) takes into consideration factors such as network security, risk management, user/role appraisal, performance, dependencies, resource consumption, the network being used, technologies being used, frequency of deployment, business model, function and rules, frequency of use, software standards, intra-team dynamics writing the application, usage calendar while it creates recommendation.
The reporting unit (7) included in the inventive system (1) creates a report in the event that a microservice does not have authority for split or merging autonomously.
In one exemplary embodiment of the invention, in the event of determining that CPU consumption of services -that have many number of calls on the 1 of the month and the 15 of the month and wherein a large amount of information pass over the network- may be a lot on these dates; the service must be distributed on a different network and system on the related dates.
In another exemplary embodiment of the invention, user information and the related microservice comprise two different functions; namely, login and password control. The login function is used very often and the function used for reporting may slow down the microservice and causes to receiving late reply upon being used at certain intervals. It may be enabled to split the service by considering the frequency of call of functions of services and the times for responding a call.
In a further exemplary embodiment of the invention, it is ensured that the requested microservices are made high security microservices by interlaying security layers. Splitting and merging transaction is carried out in the related server by considering the security layer upon looking at the subnetwork wherein they are located.
The inventive method (100) creating recommendation of splitting and merging microservice comprises steps of:
setting up the microservice monitoring unit (2) for monitoring microservices
(101),
- the microservice monitoring unit (2) saving the data about the microservices that it receives instantly by connecting to the microservice servers (MSS), to the data storage unit (3) (102),
- the data processing unit (4) parsing the data recorded in the data storage unit (3) and classifying them by using classification methods (103),
- the simulation unit (5) determining whether real data or a system simulation will be used or not and creating the simulation in the event that a system simulation is used (104),
- the recommendation unit (6) creating recommendation of splitting and merging microservice by receiving information about the microservice from the data processing unit (4) and the simulation unit (5) (105),
in the event that the microservice has authority for splitting or merging autonomously, the data processing unit (4) giving splitting or merging instruction to the microservice servers (MSS) (106),
in the event that the microservice has no authority for splitting or merging autonomously, the reporting unit (7) creating a report (107).
Claims
1. A system (1) for creating recommendation of splitting and merging microservice; comprising
at least one microservice monitoring unit (2) which is configured such that it will make observation on current microservices by connecting to the microservice servers (MSS);
at least one data storage unit (3) which is in communication with the microservice monitoring unit (2) and stores the data about the microservices;
characterized by
at least one data processing unit (4) which enables to carry out various analyses on the stored data;
at least one simulation unit (5) which is configured such that it will determine simulation will be used for recommendation of splitting and merging microservice, and will create the related recommendation when it is decided to use simulation;
at least one recommendation unit (6) which is in communication with the data processing unit (4) and the simulation unit (5) and creates recommendations intended for splitting the monitored microservice into several microservice or merging them with other microservices;
at least one reporting unit (7) which is in communication with the recommendation unit (6) and configured such that it will report the created recommendation.
2. A system (1) according to Claim 1; characterized by the data processing unit (4) which is in communication with the data storage unit (3) and configured such that it will clear the data not to be used among the data stored in the data storage unit (3); will enable to extract interrelation of data by using methods such as a decision tree method that is a classification method wherein a tree structure is created to make a decision on cleared data and probabilities are
placed to the leaves of the tree; k-nearest neighbor method that is a classification method wherein proximity of a data -that is requested to be classified- to previous data -which have been placed to a coordinate system- is looked; logistic regression method that is a classification method wherein artificial neural networks, logistics models are created and that is used for probability calculations to estimate dependent variable values; and will give splitting or merging instruction to the microservice servers (MSS) in the event that the microservice has authority of splitting or merging autonomously.
3. A system (1) according to any of the preceding claims; characterized by the simulation unit (5) which is configured such that it will determine whether real data or a simulation structure will be used before a recommendation of splitting and merging microservice is created; determine microservice features over a current system in the event of deciding that real data will be used; create a system simulation in the event of deciding that a simulation will be used for creating recommendation of splitting and merging microservice; and with the system simulations created by it, enable to obtain results such as microservices that should be merged or split in network density changes, change that will occur in use of processor when the microservices are merged, change that will occur in log amounts when the microservices are merged, difference that will occur in response time of microservice in the event that the microservice functions merge or split.
4. A system (1) according to any of the preceding claims; characterized by the recommendation unit (6) which is in communication with the data processing unit (4) and the simulation unit (5); creates recommendations of splitting and merging microservice on the basis of the information that it receives from the data processing unit (4) and the simulation unit (5); and takes into consideration factors such as network security, risk management, user/role appraisal, performance, dependencies, resource consumption, the network being used, technologies being used, frequency of deployment, business model, function
and rules, frequency of use, software standards, intra-team dynamics writing the application, usage calendar while it creates recommendation.
5. A system (1) according to any of the preceding claims; characterized by the reporting unit (7) which is configured such that it will create a report in the event that a microservice does not have authority for splitting or merging autonomously.
6. A method (100) for creating recommendation of splitting and merging microservice; characterized by steps of
setting up the microservice monitoring unit (2) for monitoring microservices (101),
the microservice monitoring unit (2) saving the data about the microservices that it receives instantly by connecting to the microservice servers (MSS), to the data storage unit (3) (102),
the data processing unit (4) parsing the data recorded in the data storage unit (3) and classifying them by using classification methods (103), the simulation unit (5) determining whether real data or a system simulation will be used or not and creating the simulation in the event that a system simulation is used (104),
the recommendation unit (6) creating recommendation of splitting and merging microservice by receiving information about the microservice from the data processing unit (4) and the simulation unit (5) (105), in the event that the microservice has authority for splitting or merging autonomously, the data processing unit (4) giving splitting or merging instruction to the microservice servers (MSS) (106),
in the event that the microservice has no authority for splitting or merging autonomously, the reporting unit (7) creating a report (107).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP19792327.9A EP3785128A2 (en) | 2018-04-26 | 2019-04-25 | System and method for creating recommendation of splitting and merging microservice |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TR2018/05929 | 2018-04-26 | ||
| TR201805929 | 2018-04-26 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| WO2019209231A2 true WO2019209231A2 (en) | 2019-10-31 |
| WO2019209231A3 WO2019209231A3 (en) | 2020-01-23 |
Family
ID=68295284
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/TR2019/050277 WO2019209231A2 (en) | 2018-04-26 | 2019-04-25 | System and method for creating recommendation of splitting and merging microservice |
Country Status (2)
| Country | Link |
|---|---|
| EP (1) | EP3785128A2 (en) |
| WO (1) | WO2019209231A2 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113342472A (en) * | 2021-06-28 | 2021-09-03 | 平安消费金融有限公司 | Micro-service cluster creating method and device, electronic equipment and readable storage medium |
| US11640289B2 (en) | 2020-08-24 | 2023-05-02 | Rockwell Collins, Inc. | Microservices cloud-native architecture for ubiquitous simulation as a service |
| US11726778B2 (en) | 2021-09-29 | 2023-08-15 | International Business Machines Corporation | Translating clusters of a monolith application to microservices |
| US11768679B2 (en) | 2021-11-30 | 2023-09-26 | International Business Machines Corporation | Identifying microservices for a monolith application through static code analysis |
| US11847443B2 (en) | 2021-09-07 | 2023-12-19 | International Business Machines Corporation | Constraints-based refactoring of monolith applications through attributed graph embeddings |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114928633B (en) * | 2022-05-16 | 2024-04-16 | 江苏赞奇科技股份有限公司 | Efficient control method and system based on complex cloud application environment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3210350B1 (en) * | 2014-10-21 | 2020-05-20 | Twilio, Inc. | Method for providing a miro-services communication platform |
| CN104462026A (en) * | 2014-12-10 | 2015-03-25 | 中国科学院软件研究所 | System and method for providing cloud word stock service |
| US20170364434A1 (en) * | 2016-06-15 | 2017-12-21 | International Business Machines Corporation | Splitting and merging microservices |
-
2019
- 2019-04-25 WO PCT/TR2019/050277 patent/WO2019209231A2/en active Application Filing
- 2019-04-25 EP EP19792327.9A patent/EP3785128A2/en not_active Withdrawn
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11640289B2 (en) | 2020-08-24 | 2023-05-02 | Rockwell Collins, Inc. | Microservices cloud-native architecture for ubiquitous simulation as a service |
| CN113342472A (en) * | 2021-06-28 | 2021-09-03 | 平安消费金融有限公司 | Micro-service cluster creating method and device, electronic equipment and readable storage medium |
| US11847443B2 (en) | 2021-09-07 | 2023-12-19 | International Business Machines Corporation | Constraints-based refactoring of monolith applications through attributed graph embeddings |
| US11726778B2 (en) | 2021-09-29 | 2023-08-15 | International Business Machines Corporation | Translating clusters of a monolith application to microservices |
| US11768679B2 (en) | 2021-11-30 | 2023-09-26 | International Business Machines Corporation | Identifying microservices for a monolith application through static code analysis |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019209231A3 (en) | 2020-01-23 |
| EP3785128A2 (en) | 2021-03-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019209231A2 (en) | System and method for creating recommendation of splitting and merging microservice | |
| US20190236485A1 (en) | Orchestration system for distributed machine learning engines | |
| DE112018005462T5 (en) | ANOMALY DETECTION USING COGNITIVE COMPUTING | |
| CN109120428B (en) | Method and system for wind control analysis | |
| CN111597247A (en) | Data anomaly analysis method and device and storage medium | |
| Jeong et al. | Anomaly teletraffic intrusion detection systems on hadoop-based platforms: A survey of some problems and solutions | |
| Dehraj et al. | A review on architecture and models for autonomic software systems | |
| CN113626241B (en) | Abnormality processing method, device, equipment and storage medium for application program | |
| CN110457175B (en) | Service data processing method and device, electronic equipment and medium | |
| CN113590451B (en) | Root cause positioning method, operation and maintenance server and storage medium | |
| US20210201270A1 (en) | Machine learning-based change control systems | |
| CN112016094A (en) | Block chain service safety protection strategy management and control system and method | |
| CN111859047A (en) | Fault solving method and device | |
| CN113656808A (en) | Data security evaluation method, device, equipment and storage medium | |
| Wurzenberger et al. | Complex log file synthesis for rapid sandbox-benchmarking of security-and computer network analysis tools | |
| CN113392426A (en) | Method and system for enhancing data privacy of an industrial or electrical power system | |
| Cole | (Infra) structural discontinuity: Capital, labour, and technological change | |
| Jain et al. | Availability prediction of repairable fault-tolerant system with imperfect coverage, reboot, and common cause failure | |
| CN114327374A (en) | Business process generation method and device and computer equipment | |
| Abro et al. | Artificial intelligence enabled effective fault prediction techniques in cloud computing environment for improving resource optimization | |
| Trifonov et al. | Enabling technologies for safety critical communications | |
| Banica et al. | Empowering IT operations through artificial intelligence–a new business perspective | |
| Ji et al. | A new framework consisted of data preprocessing and classifier modelling for software defect prediction | |
| Mijumbi et al. | MAYOR: machine learning and analytics for automated operations and recovery | |
| CN114398676A (en) | Data security classification method, device, equipment and medium based on artificial intelligence |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19792327 Country of ref document: EP Kind code of ref document: A2 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2019792327 Country of ref document: EP |
|
| ENP | Entry into the national phase |
Ref document number: 2019792327 Country of ref document: EP Effective date: 20201126 |