Micro services recommendation system for identifying code areas at risk

1. A system for identifying risky code in microservices, the system comprising:

one or more processors; and

a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to:

generate a graph of connected nodes comprising nodes which represent atomic parts of executable code in code segments in micro services of an application, an atomic part of executable code comprising a functionally irreducible portion of a computer program that contains executable instructions;

identify, by applying graph analysis over the graph, a node at any graphical level that represents an atomic part of executable code in code segments modified by a modification, and in a microservice in the application, and other connected nodes at any graph levels that represent other atomic parts of executable code in other code segments in other microservices in the application;

determine a segments similarity score based on comparing the modified atomic part of executable code in the code segments represented by the identified node, and in the microservice of the application, against another atomic part of executable code in other code segments represented by another node, and in another microservice of the application;

determine whether the segments similarity score satisfies a segments similarity threshold; and

output a recommendation to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice in the application, in response to a determination that the segments similarity score satisfies the segments similarity threshold.

2. The system of claim 1 , wherein identifying the modification to the code segments in the application comprises identifying the modification in an atomic part of executable code in the code segments in the microservice of the application.

3. The system of claim 1 , wherein comparing the code segments against the other code segments comprises comparing a copy of an atomic part of executable code in the code segments, which was created before the modification to the code segments, against another atomic part of executable code in the other code segments.

4. The system of claim 1 , wherein comparing the code segments against the other code segments comprises comparing an atomic part of executable code in the code segments, after the modification was made to the code segments, against another atomic part of executable code in the other code segments.

5. The system of claim 1 , wherein the plurality of instructions further causes the processor to:

output an option to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice of the application; and

make the modification to the other code segments in the other microservice of the application, in response to receiving a selection of the option to make the modification to the other code segments in the other microservice of the application.

6. The system of claim 5 , wherein making the modification to the other code segments in the other microservice of the application comprises making the modification, which was made to an atomic part of executable code in the code segments in the microservice of the application, to another atomic part of executable code in the other code segments in the other microservice of the application.

7. A computer-implemented method for identifying risky code in microservices, the computer-implemented method comprising:

generating a graph of connected nodes comprising nodes which represent atomic parts of executable code in code segments in microservices of an application, an atomic part of executable code comprising a functionally irreducible portion of a computer program that contains executable instructions;

identifying, by applying graph analysis over the graph, a node at any graph level that represents an atomic part of executable code in code segments modified by a modification, and in a microservice in the application, and other connected nodes at any graph levels that represent other atomic parts of executable code in other code segments in other microservices in the application;

determining a segments similarity score based on comparing the modified atomic part of executable code in the code segments represented by the identified node, and in the microservice of the application, against another atomic part of executable code in other code segments represented by another node, and in another microservice of the application;

determining whether the segments similarity score satisfies a segments similarity threshold; and

outputting a recommendation to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice in the application, in response to a determination that the segments similarity score satisfies the segments similarity threshold.

8. The computer-implemented method of claim 7 , wherein identifying the modification to the code segments in the application comprises identifying the modification in an atomic part of executable code in the code segments in the microservice of the application.

9. The computer-implemented method of claim 7 , wherein comparing the code segments against the other code segments comprises comparing a copy of an atomic part of executable code in the code segments, which was created before the modification to the code segments, against another atomic part of executable code in the other code segments.

10. The computer-implemented method of claim 7 , wherein comparing the code segments against the other code segments comprises comparing an atomic part of executable code in the code segments, after the modification was made to the code segments, against another atomic part of executable code in the other code segments.

11. The computer-implemented method of claim 7 , wherein the computer-implemented method further comprises:

outputting an option to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice of the application; and

making the modification to the other code segments in the other microservice of the application, in response to receiving a selection of the option to make the modification to the other code segments in the other microservice of the application.

12. The computer-implemented method of claim 11 , wherein making the modification to the other code segments in the other microservice of the application comprises making the modification, which was made to an atomic part of executable code in the code segments in the microservice of the application, to another atomic part of executable code in the other code segments in the other microservice of the application.

13. A computer program product for identifying risky code in microservices, the computer program product comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions to:

generate a graph of connected nodes comprising nodes which represent atomic parts of executable code in code segments in microservices of an application, an atomic part of executable code comprising a functionally irreducible portion of a computer program that contains executable instructions;

identify, by applying graph analysis over the graph, a node at any graph level that represents an atomic part of executable code in code segments modified by a modification, and in a microservice in the application, and other connected nodes at any graph levels that represent other atomic parts of executable code in other code segments in other microservices in the application;

determine a segments similarity score based on comparing the modified atomic part of executable code in the code segments represented by the identified node, and in the microservice of the application, against another atomic part of executable code in other code segments represented by another node, and in another microservice of the application;

determine whether the segments similarity score satisfies a segments similarity threshold; and

output a recommendation to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice in the application, in response to a determination that the segments similarity score satisfies the segments similarity threshold.

14. The computer program product of claim 13 , wherein identifying the modification to the code segments in the application comprises identifying the modification in an atomic part of executable code in the code segments in the microservice of the application.

15. The computer program product of claim 13 , wherein comparing the code segments against the other code segments comprises comparing a copy of an atomic part of executable code in the code segments, which was created before the modification to the code segments, against another atomic part of executable code in the other code segments.

16. The computer program product of claim 13 , wherein comparing the code segments against the other code segments comprises comparing an atomic part of executable code in the code segments, after the modification was made to the code segments, against another atomic part of executable code in the other code segments.

17. The computer program product of claim 13 , wherein the program code includes further instructions to:

output an option to make the modification, which was made to the code segments in the microservice of the application, to the other code segments in the other microservice of the application; and

make the modification to the other code segments in the other microservice of the application, in response to receiving a selection of the option to make the modification to the other code segments in the other microservice of the application, wherein making the modification to the other code segments in the other microservice of the application comprises making the modification, which was made to an atomic part of executable code in the code segments in the microservice of the application, to another atomic part of executable code in the other code segments in the other microservice of the application.