Recommendation : 3. Use environments and tools that limit impacts
Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?
Is the use of external APIs restricted (if possible)?
The loads introduced by the solicitation of remote resources via API mechanisms can be significant. Certain functionalities could be covered by local rather than remote actions, which reduces the volume of exchanges and the number of components used, thus reducing the environmental footprint. On the other hand, the local processing of a functionality which may require new technical dependencies must not increase the load on the front end.
Nagivation tests cover API calls. Developement tools allow tracking of data sizes (CHROME: network)
Rule for assessing the level of compliance of the criterion
Number of features analyzed / Number of candidate features
11 other criteria related to the recommendation: Use environments and tools that limit impacts
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 ?
Are the latest technical advances used when they really help reduce impact ?