Claims:We claim:
1. A method for migrating monolithic enterprise applications to a microservice architecture, the method comprising:
receiving, by an application migration server (101), metadata information (201) associated with a monolithic application of an enterprise, from one or more users related with the monolithic application;
obtaining, by the application migration server (101), artefacts (203) associated with the monolithic application, from a repository of the monolithic application;
generating, by the application migration server (101), a master data (205) for the monolithic application based on the metadata information (201) and the artefacts (203), wherein the master data (205) lists a plurality of modules associated with the monolithic application;
classifying, by the application migration server (101), the plurality of modules into one of first level degree modules, second level degree modules, and third level degree modules, based on modularity of source code and bundling of the monolithic application, obtained from the master data (205); and
performing, by the application migration server (101), migration of one or more modules of the plurality of modules, classified as the first level degree modules, to the microservice architecture.

2. The method as claimed in claim 1, wherein the metadata information (201) comprises requirement details being addressed by the monolithic application, an industry vertical, and domains details associated with the monolithic application.

3. The method as claimed in claim 1, wherein the master data (205) comprises enterprise framework and components detail of the monolithic application, list of modules, and sub-modules of the monolithic application and dependencies between each module, business functionalities and third-party solutions associated with the monolithic application.

4. The method as claimed in claim 1, wherein the artefacts (203) comprises source code of the monolithic application, business logic, architecture documents, and a requirement document associated with the monolithic application.

5. The method as claimed in claim 1, wherein the first level degree modules are capable of being automatically migrated to the microservice architecture.

6. The method as claimed in claim 1, wherein the second level degree modules require one or more corrections in framework to comply with the microservice architecture.

7. The method as claimed in claim 1, wherein the third level degree modules are to be discarded and rewritten based on the microservice architecture.

8. The method as claimed in claim 1 further comprising providing recommendation on at least one of, open source tools required for migration of the monolithic application, security recommendations and report on vulnerability of the source code, one or more metrics for the plurality of modules, one or more changes required in artefacts (203), architectural diagrams and test cases associated with the first level degree modules for migrating to the microservice architecture.

9. The method as claimed in claim 8, wherein the one or more metrics comprises a roadmap for migrating the first level degree modules to the microservice architecture, technical debt indicating correction needed for the second level degree modules based on industry standard productivity, evaluation on applicability of the plurality of modules to be stored on a server, and evaluating changes required for test cases of the plurality of modules.

10. The method as claimed in claim 1 further comprising providing details of refactoring needed to comply with the microservice architecture for the one or more modules.

11. The method as claimed in claim 1, wherein the migration of the one or more modules comprises classifying the plurality of modules into a plurality of domains, based on the master data (205) and type of solutions provided by the plurality of modules.

12. An application migration server (101) for migrating enterprise applications to microservice architecture, comprising:
a processor (115); and
a memory (113) communicatively coupled to the processor (115), wherein the memory (113) stores processor instructions, which, on execution, causes the processor (115) to:
receive metadata information (201) associated with a monolithic application of an enterprise, from one or more users related with the monolithic application;
obtain artefacts (203) associated with the monolithic application, from a repository of the monolithic application;
generate a master data (205) for the monolithic application based on the metadata information (201) and the artefacts (203), wherein the master data (205) lists a plurality of modules associated with the monolithic application;
classify the plurality of modules into one of first level degree modules, second level degree modules, and third level degree modules, based on modularity of source code and bundling of the monolithic application, obtained from the master data (205); and
perform migration of one or more modules of the plurality of modules, classified as the first level degree modules, to the microservice architecture.

13. The application migration server (101) as claimed in claim 12, wherein the metadata information (201) comprises requirement details being addressed by the monolithic application, industry vertical, and domains details associated with the monolithic application.

14. The application migration server (101) as claimed in claim 12, wherein the master data (205) comprises enterprise framework and components detail of the monolithic application, list of modules and sub-modules of the monolithic application and dependencies between each module, business functionalities and third-party solutions associated with the monolithic application.

15. The application migration server (101) as claimed in claim 12, wherein the artefacts (203) comprises source code of the monolithic application, business logic, architecture documents, and requirement documents associated with the monolithic application.

16. The application migration server (101) as claimed in claim 12, wherein the first level degree modules are capable of being automatically migrated to the microservice architecture.

17. The application migration server (101) as claimed in claim 12, wherein the second level degree modules require one or more corrections in framework to comply with the microservice architecture.

18. The application migration server (101) as claimed in claim 12, wherein the third level degree modules are to be discarded and rewritten based on the microservice architecture.

19. The application migration server (101) as claimed in claim 12, wherein the processor (115) provides recommendation on at least one of, open source tools required for migration of the monolithic application, security recommendations, and report on vulnerability of the source code, one or more metrics for the plurality of modules, one or more changes required in artefacts (203), architecture diagram, and test cases associated with the first level degree modules for migrating to microservice architecture. .

20. The application migration server (101) as claimed in claim 19, wherein the one or more metrics comprises a roadmap for migrating the first level degree modules to the microservice architecture, technical debt indicating correction needed for the second level degree modules based on industry standard productivity, evaluation on applicability of the plurality of modules to be stored on a server and evaluating changes required for test cases of the plurality of modules.

21. The application migration server (101) as claimed in claim 12, wherein the processor (115) provides details of refactoring needed to comply with the microservice architecture for the one or more modules.

22. The application migration server (101) as claimed in claim 12, wherein the migration of the one or more modules comprises classifying the plurality of modules into a plurality of domains, based on the master data (205) and type of solutions provided by the plurality of modules.
Date this 15th day of February, 2018

R Ramya Rao
IN/PA-1607
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
The present subject matter is related in general to the field of application migration, more particularly, but not exclusively to method and system for migrating monolithic enterprise applications to microservice architecture.