Has the dependency tree of the integrated components been evaluated ?
Is the dependency graph generated?
Very often components from public libraries (open source or commercial) provide a set of functionalities that are rarely used, and drain dependencies on other components with the same characteristics. In the end, the project aggregates a large volume of libraries while only a small part is actually used. Favouring components whose dependencies and functionalities are controllable in relation to needs is efficient from the Sustainable IT point of view.
Rule for assessing the level of compliance of the criterion
0 / 0
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 ?
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 ?
Are unused resources freed up as quickly as possible ?
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" ?