Are unused resources freed up as quickly as possible ?
Is local data released as soon as it is no longer needed?
Development techniques free developers from explicit allocation and release of resources used. However, the volume of resources is conditioned by the scope of the information and the extensive use of data will result in an overload of consumption which may lead to an over-sizing of the equipment. A more rational use of ressources would allow to avoid this.
Source code checks validate resources are freed asap
Rule for assessing the level of compliance of the criterion
Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100
Fin de Vie
16 other criteria related to the recommendation: Use the technical components that improve the sustainable IT aspects, security and performance
Is the documentation of the functionality available to enable its reuse ?
Is the web server used asynchronous and multi-threaded ?
Has the dependency tree of the integrated components been evaluated ?
Can dependencies be reduced by using an alternative component ?
Is the user informed of a processing in progress in the background ?
Has the integration of asynchronous processing been evaluated ?
Is a VM necessary as opposed to a container solution ?
Does service availability require redundancy ?
Do interactions between components benefit from caching mechanisms ?
Are the browser caches not being blocked by the framework or technology used ?
Is there a lighter framework / library that meets the functional need ?
Is an Open Source solution available for the functional need ?
Are the versions of the components used tracked and deployed ?
Is the security implemented justified with regard to the operations carried out ?
Is the level of logs adapted to the environment ?
Are temporary files included in the "logrotate" ?