Avoid launching OS-specific sub-processes from code
Cloud/PaaS applications must be OS-agnostic as much as possible and should not rely on OS-specific features or processes, which may not be available on the Cloud environment as the underlying operating system (in this specific case, Windows) may change over time. Sub-processes that are executed from code are specific to an Operating System.
Criticality
The criticality level impacts the application Cloud Maturity score, whether it is a blocker (a negative pattern found during the code scan) or a booster (a pattern that makes your app more Cloud-ready) and the corresponding level (low, medium, high, critical).Migration Impacts
[nz_btn text="Code" link="#" target="_self" icon="icon-heart-broken" animate="false" animation_type="ghost" color="black" size="small" shape="rounded" type="normal" hover_normal="fill" hover_ghost="fill" el_class="" /] Migration impact levels indicate the different layers of your application that you should modify or fix, in order to comply with Cloud-oriented programming best practices and remove the identified roadblocks.Searched Code Patterns
Search in code for sub-processes.
Examples:
- C#/VB.Net: Detect of using System.Diagnostics in combination with new Process(
- Python: subprocess.run(
References
https://developer.ibm.com/articles/1404-brown/
For reference only. For the complete details please refer the original article
https://doc.casthighlight.com/cloudready_launch_sub_processes/
https://doc.casthighlight.com/cloudready_launch_sub_processes/
Comments