Workload Assessment Overview
This topic describes workload assessment where the intelligent engine assesses the legacy workloads and produces insights and actionable recommendations for migration. It analyses code (business logic) and execution logs, which aids in the prioritization of the roadmap for offloading business processes and applications to modern cloud-based platforms.
As part of the analysis, it provides end-to-end data and process lineage that helps to visualize complex interdependencies between all the workloads in a simplified and intelligible manner. For example, data lineage helps identify the complete chain of input and reference tables that are used to populate the output tables. Additionally, process lineage shows the linkages between scripts, procedures, jobs, and any other piece of code calling/using certain scripts, etc. This helps to analyze the existing codebase end-to-end, segregate workloads into logical units for migration, and provide 360-degree visibility from origination to reporting.
As part of actionable recommendations, it provides a recommendation for an optimized future-state architecture ensuring that it leverages the underlying cloud services efficiently and reaps the advantages of the modern environment as promised.
In a nutshell, the assessment’s iterative prescriptive process is summarized below.
As part of the Analysis, it does the following:
- Profiling of entire inventory
- Scheduler scripts, procedures, DML and DDL scripts, ETL graphs, database logs, application logs…
- Complex interdependencies/lineage
- Rich visualizations
As part of Discovery, it does the following.
- Identifying different code patterns
- Resource utilization
- Assessing complexity, frequency of use
As part of Segregation, it does the following.
- Workload segregation based on patterns, complexity
As part of Optimization, it does the following.
- Identifying Technical debt
- Parallel workload execution
- Target schema optimization recommendations
As part of Future-state Architecture Blueprint, it does the following.
- Mapping compatibility
- Identifying tech stack components
- To-be architecture – elastic and flexible suitable for current and future requirements
Leaplogic