Does service availability require redundancy ?
Is the SLA defined?
Redundancy makes it possible to guarantee a high level of service. This solution however requires a considerable duplication of physical equipment, networks and storage. This fault tolerance is sometimes justified by the functionality of the service, and sometimes goes beyond the requirements. Adapting the level of service and the need for the service allows the environmental impact to be reduced.
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100
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 ?
Are unused resources freed up as quickly as possible ?
Is a VM necessary as opposed to a container solution ?
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" ?