Recommendation : 3. Use environments and tools that limit impacts
Is the data fed back by the APIs really only the data that the application needs when it is requested ?
Are the volumes of data transmitted commensurate with the presentation capabilities of the user device?
The journeys and needs of users are very difficult to anticipate. One trend is to collect as much front end data as possible to cover as many use cases as possible. This practice is inefficient from an IT point of view. Sustainable because the collection, the processing, the routing, the local storage of the data generates a load and therefore a significant energy consumption without certainty that all this data will actually be used. The service footprint must be reduced by collecting only essential data as the service unfolds through API mechanisms.
Developement tools are used to track API call & data sizes (CHROME: network)
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of API calls analyzed / Number of API calls
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 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 ?