Recommendation : 3. Use environments and tools that limit impacts
Do the libraries used allow you to take only the components that are actually useful ?
How are the components used?
Very often components from public libraries (open source or commercial) provide a set of functionalities which are rarely all used and drain dependencies on other components with the same characteristics. In the end, the project aggregates a large volume of the library while a small part is actually used. Favoring components whose dependencies and functionalities are controllable in relation to the needs is efficient from the sustainable IT point of view.
Technical documention mention components dependancies and how to remove unneeded
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
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 ?
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 ?
Are the latest technical advances used when they really help reduce impact ?