Abstract: The present invention provides for a system and a method for application transformation to cloud for conversion of an application source code to a cloud native code. The present invention provides for receiving a first, second, third and fourth transformation recommendation paths. Further, the present invention provides for applying a set of remediation templates based on the first and the second transformation recommendation paths. The present invention provides for applying a pre-defined transformation process flow on the application source code based on the first and the second transformation recommendation paths to transform the application source code to the cloud native code. The present invention provides for applying a reusable service template on the application source code. The present invention provides for creating plurality of configuration artifacts specific to the cloud platform. The preset invention provides for building a CI/CD pipeline for integration and deployment of the cloud native code.
We Claim:
1. A system for application transformation to cloud by
conversion of an application source code to a cloud native
code, the system comprising:
a memory storing program instructions; a processor configured to execute program instructions stored in the memory; and an application transformation to cloud engine executed by the processor and configured to:
receive a first and a second transformation recommendation paths;
apply a set of remediation templates based on the first and the second transformation recommendation paths, wherein the set of remediation steps comprises pre-defined parameterized actions;
apply a pre-defined transformation process flow on the application source code based on the first and the second transformation recommendation paths to transform the application source code to the cloud native code; and
apply a reusable service template on the application source code, based on the first and the second transformation recommendation paths, wherein the reusable service template apply repeatable code changes required for integration and deployment of the cloud native code to a cloud platform.
2. The system as claimed in claim 1, wherein the application transformation to cloud engine executed by the processor is configured to receive a third and a fourth transformation recommendation path.
3. The system as claimed in claim 1, wherein the first transformation recommendation path signifies moving the
application source code to the cloud platform with minimal code changes.
4. The system as claimed in claim 1, wherein the second transformation recommendation path signifies moving the application source code to the cloud platform with more number of changes to the source code as compared to the changes to the code required for the first transformation recommendation path.
5. The system as claimed in claim 2, wherein the third transformation recommendation path signifies moving the application source code to the cloud platform with configuration changes.
6. The system as claimed in claim 2, wherein the fourth transformation recommendation path signifies that the application source code cannot be reused and a new application source code is to be written to host the application source code in the cloud platform.
7. The system as claimed in claim 1, wherein the application transformation to cloud engine comprises an orchestration unit executed by the processor to execute a semi-automated workflow based on the transformation recommendation paths received from a cloud readiness assessment tooi interfaced with the application transformation to cloud engine.
8. The system as claimed in claim 7, wherein the orchestration unit further comprises a workflow management unit executed by the processor to render information on stages of execution of the semi-automated workflow including rendering a result summary of execution of the semi-automated workflow.
9. The system as claimed in claim 7, wherein the
orchestration unit comprises a settings management unit
executed by the processor and configured to enable
selection of various transformation tools like cloud
readiness assessment tooi and CI/CD pipeline tooi required
for transformation of the application source code to the
cloud native code.
10. The system as claimed in claim 7, wherein the
orchestration unit comprises a scheduler unit executed by
the processor for checking a status of the semi-automated
workflow by calling an application program interface (API)
end-point.
11. The system as claimed in claim 1, wherein the
application transformation to cloud engine comprises a
cloud configuration unit executed by the processor to
create plurality of configuration artifacts specific to
the cloud platform.
12. The system as claimed in claim 1, wherein the
application transformation to cloud engine comprises a
remediation unit executed by the processor to apply source
code changes to remediate anti-patterns based on the
predefined parameterized actions.
13. The system as claimed in claim 1, wherein the application transformation to cloud engine comprises a cloud native transformation unit executed by the processor to generate the cloud native code which is compatible with the cloud platform.
14. The system as claimed in claim 1, wherein the application transformation to cloud engine comprises a template distribution unit executed by the processor to apply the reusable service templates.
15. The system as claimed in claim 2, wherein the
application transformation to cloud engine comprises a
continuous integration/ continuous deployment (CI/CD)
pipeline builder executed by the processor to build a CI/CD
pipeline for continuous integration and deployment of the
cloud native code to the cloud platform based on the first,
second and third transformation recommendation paths.
16. A method for application transformation to cloud by
conversion of an application source code to a cloud native
code, executed by a processor comprising program
instructions stored in a memory, the method comprising:
receiving, by the processor, a first and a second transformation path recommendation;
applying, by the processor, a set of remediation templates based on the first and the second transformation recommendation paths, wherein the set of remediation templates comprises predefined parameterized actions;
applying, by the processor, a pre-defined transformation process flow based on the first and the secondtransformation recommendation paths on an application source code to transform the application source code to a cloud native code; and
applying, by the processor, based on the first and the second transformation recommendation paths, a reusable service template on the application source code, wherein the reusable service templates apply repeatable code changes required for integration and deployment of the application source code to the cloud native code .
17. The method as claimed in claim 16, wherein the
receiving step further comprises receiving a third and a
fourth transformation recommendation path.
18. The method as claimed in claim 16, wherein the first transformation recommendation path signifies moving the application source code to the cloud platform with minimal code change.
19. The method as claimed in claim 16, wherein the second transformation recommendation path signifies moving the application source code to the cloud platform with more number of changes to the source code as compared to the changes to the code required for the first transformation recommendation path.
20. The method as claimed in in claim 17, wherein the third transformation recommendation path signifies moving the application source code to the cloud platform with some configuration changes.
21. The method as claimed in in claim 17, wherein the fourth transformation recommendation path signifies that the application source code cannot be reused and a new application source code is to be written to host the application source code in the cloud platform.
22. The method as claimed in claim 16, wherein the method comprises executing a semi-automated workflow based on the transformation recommendation paths received from a cloud readiness assessment tooi interfaced with the application transformation to cloud engine.
23. The method as claimed in claim 16, wherein the method comprises executing a semi-automated workflow including rendering a result summary of execution of the semi-automated workflow.
24. The method as claimed in claim 16, wherein the method comprises enabling selection of transformation tools
including cloud readiness assessment tooi and CI/CD pipeline tooi for transformation of the application source code to the cloud native code.
25. The method as claimed in claim 16, wherein the method comprises checking a status of the semi-automated workflow by calling an application program interface (API) end-point.
26. The method as claimed in claim 16, wherein the method comprises creating a plurality of configuration artifacts specific to the cloud platform.
27. The method as claimed in claim 16, wherein the method comprises remediating anti-patterns in the application source code based on the predefined parameterized actions.
28. The method as claimed in claim 17, wherein the method comprises building a CI/CD pipeline for integration and deployment of the cloud native code to a cloud platform based on the first, second and third transformation recommendation paths.
| # | Name | Date |
|---|---|---|
| 1 | 201941051520-STATEMENT OF UNDERTAKING (FORM 3) [12-12-2019(online)].pdf | 2019-12-12 |
| 2 | 201941051520-PROOF OF RIGHT [12-12-2019(online)].pdf | 2019-12-12 |
| 3 | 201941051520-POWER OF AUTHORITY [12-12-2019(online)].pdf | 2019-12-12 |
| 4 | 201941051520-FORM 1 [12-12-2019(online)].pdf | 2019-12-12 |
| 5 | 201941051520-DRAWINGS [12-12-2019(online)].pdf | 2019-12-12 |
| 6 | 201941051520-COMPLETE SPECIFICATION [12-12-2019(online)].pdf | 2019-12-12 |
| 7 | 201941051520-FORM 18 [16-12-2019(online)].pdf | 2019-12-16 |
| 8 | Correspondence by Agent_Form1-Power of Attorney_18-12-2019.pdf | 2019-12-18 |
| 9 | 201941051520-Request Letter-Correspondence [23-12-2019(online)].pdf | 2019-12-23 |
| 10 | 201941051520-Form 1 (Submitted on date of filing) [23-12-2019(online)].pdf | 2019-12-23 |
| 11 | 201941051520-FORM 3 [26-05-2020(online)].pdf | 2020-05-26 |
| 12 | 201941051520-FER.pdf | 2021-10-17 |
| 13 | 201941051520-PETITION UNDER RULE 137 [19-01-2022(online)].pdf | 2022-01-19 |
| 14 | 201941051520-FORM 3 [19-01-2022(online)].pdf | 2022-01-19 |
| 15 | 201941051520-FER_SER_REPLY [19-01-2022(online)].pdf | 2022-01-19 |
| 16 | 201941051520-DRAWING [19-01-2022(online)].pdf | 2022-01-19 |
| 17 | 201941051520-CLAIMS [19-01-2022(online)].pdf | 2022-01-19 |
| 18 | 201941051520-ABSTRACT [19-01-2022(online)].pdf | 2022-01-19 |
| 19 | 201941051520-PatentCertificate12-03-2024.pdf | 2024-03-12 |
| 20 | 201941051520-IntimationOfGrant12-03-2024.pdf | 2024-03-12 |
| 1 | SearchE_22-07-2021.pdf |