# US 2017/0364434 A1 · Splitting and merging microservices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0364434 A1
- Document ID: US20170364434A1
- Status: Published application
- Kind: A1
- Application number: 15/182,718
- Filed: 2016-06-15
- Published: 2017-12-21
- Earliest claimed: 2016-06-15
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Sudheesh S. Kairali; Suresh Kodati
- Web page: https://patentgrep.com/patent/US20170364434A1

## CPC

- G06F 11/3668: Testing of software
- G06F 11/3692: {for test results analysis}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method, executed by a computer, includes receiving test data corresponding to a first microservice and a second microservice, determining, using the test data, whether the first microservice can be split, determining, using the test data, whether the first and second microservices can be merged, responsive to determining that the first microservice can be split, issuing a recommendation to split the first microservice, and responsive to determining that the first and second microservices can be merged, issuing a recommendation to merge the first microservice and the second microservice. A computer system and computer program product corresponding to the above method are also disclosed herein.

## Claims

### Claim 1

A method, executed by a computer, the method comprising:
receiving test data corresponding to a first microservice and a second microservice;
determining, using the test data, whether the first microservice can be split;
determining, using the test data, whether the first and second microservices can be merged;
responsive to determining that the first microservice can be split, issuing a recommendation to split the first microservice; and
responsive to determining that the first and second microservices can be merged, issuing a recommendation to merge the first microservice and the second microservice.

### Claim 2 (depends on 1)

The method of claim 1, wherein determining whether the first microservice can be split comprises determining that the first microservice has multiple independent functionalities; and
wherein issuing a recommendation to split comprises issuing a recommendation to split the first microservice into a plurality of microservices, wherein each microservice of the plurality of microservices corresponds to one of the multiple independent functional responsibilities.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice and the second microservice share a functionality; and
wherein issuing a recommendation to merge comprises issuing a recommendation to remove the functionality from the second microservice and to merge the functionality into the first microservice.

### Claim 4 (depends on 1)

The method of claim 1, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during deployment of the first microservice.

### Claim 5 (depends on 1)

The method of claim 1, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice when scaling the first microservice.

### Claim 6 (depends on 1)

The method of claim 1, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during a backup operation of the first microservice.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during a restore operation of the first microservice.

### Claim 8

A computer system comprising:
one or more computer processors;
one or more computer readable storage media;
program instructions stored therein for execution by at least one of the one or more computer processors, the program instructions comprising instructions for:
receiving test data corresponding to a first microservice and a second microservice;
determining, using the test data, whether the first microservice can be split;
determining, using the test data, whether the first and second microservices can be merged;
responsive to determining that the first microservice can be split, issuing a recommendation to split the first microservice; and
responsive to determining that the first and second microservices can be merged, issuing a recommendation to merge the first microservice and the second microservice.

### Claim 9 (depends on 8)

The computer system of claim 8, wherein determining whether the first microservice can be split comprises determining that the first microservice has multiple independent functionalities; and
wherein issuing a recommendation to split comprises issuing a recommendation to split the first microservice into a plurality of microservices, wherein each microservice of the plurality of microservices corresponds to one of the multiple independent functional responsibilities.

### Claim 10 (depends on 8)

The computer system of claim 8, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice and the second microservice share a functionality; and
wherein issuing a recommendation to merge comprises issuing a recommendation to remove the functionality from the second microservice and to merge the functionality into the first microservice.

### Claim 11 (depends on 8)

The computer system of claim 8, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during deployment of the first microservice.

### Claim 12 (depends on 8)

The computer system of claim 8, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice when scaling the first microservice.

### Claim 13 (depends on 8)

The computer system of claim 8, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during a backup operation of the first microservice.

### Claim 14 (depends on 8)

The computer system of claim 8, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during a restore operation of the first microservice.

### Claim 15

A computer program product comprising:
a computer readable storage medium and program instructions stored on the computer readable storage medium, the program instructions comprising instructions for:
receiving test data corresponding to a first microservice and a second microservice;
determining, using the test data, whether the first microservice can be split;
determining, using the test data, whether the first and second microservices can be merged;
responsive to determining that the first microservice can be split, issuing a recommendation to split the first microservice; and
responsive to determining that the first and second microservices can be merged, issuing a recommendation to merge the first microservice and the second microservice.

### Claim 16 (depends on 15)

The computer program product of claim 15, wherein determining whether the first microservice can be split comprises determining that the first microservice has multiple independent functionalities; and
wherein issuing a recommendation to split comprises issuing a recommendation to split the first microservice into a plurality of microservices, wherein each microservice of the plurality of microservices corresponds to one of the multiple independent functional responsibilities.

### Claim 17 (depends on 15)

The computer program product of claim 15, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice and the second microservice share a functionality; and
wherein issuing a recommendation to merge comprises issuing a recommendation to remove the functionality from the second microservice and to merge the functionality into the first microservice.

### Claim 18 (depends on 15)

The computer program product of claim 15, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during deployment of the first microservice.

### Claim 19 (depends on 15)

The computer program product of claim 15, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice when scaling the first microservice.

### Claim 20 (depends on 15)

The computer program product of claim 15, wherein determining whether the first and second microservices can be merged comprises determining that the first microservice depends partially on the second microservice during a backup operation of the first microservice.
