Software ResiliencyCode Reliability
Production Risk
How we detect
Why you should care
Background processes occur behind the scenes without user intervention. They can be considered unwanted and slow down the software that is running and is of main priority to the user.
Background processes occur as KSH is capable of providing a facility to control and run job in the background.
Background processes occur as KSH is capable of providing a facility to control and run job in the background.
Business Impacts
Background processes are risky because it has a tendency of greatly slowing down the code; rendering it unproductive.
CAST Recommendations
How we detect
This code insight shows that background processes introduces asynchronous processes execution. They can potentially create resource conflicts. Execution in background is useful for command line but should be avoided in scripts.
About CAST and Highlight’s Code Insights
Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.
See featuresHow it works