Recommendation : 3. Use environments and tools that limit impacts
Are the latest technical advances used when they really help reduce impact ?
How often are improvements evaluated?
Technological advances follow one another quickly, Sustainable IT by spreading is also progressing in practices and efficiency. The conjunction of these 2 phenomena requires during the project, a permanent watch and a strategy to assess the benefits of the adoption of new technical elements vis-à-vis the sustainable IT impacts
Rule for assessing the level of compliance of the criterion
0 / 0
11 other criteria related to the recommendation: Use environments and tools that limit impacts
Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?
Do you use caching mechanisms to limit exchanges ?
Is the data fed back by the APIs really only the data that the application needs when it is requested ?
Is an openSource alternative available for APIs ?
Do the libraries used allow you to take only the components that are actually useful ?
Are unused dependencies identified and removed ?
Couldn't the expected functionality be implemented with the native capabilities of the browser ?
Is an openSource alternative available ?
Are all the technical equipment used by the service identified ?
For each equipment, are the characteristics available ?
Are the functionalities related to regulated data processing (health, personal, banking) validated in terms of interoperability ?