Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Backend    ODD#12     ODD#13    

Is the number of requests between the client and the server kept to a minimum ?

Recommendation 

Flux

B People

A Planet

A Prosperity

Difficulty

**

Priority

High

Récurrence

OnUpdate

Tests

How many requests are needed for a user journey?

Precisions

The operations carried out on the front end generate requests to the remote services. The greater the number of requests, the more resources the processing and exchange mechanisms will consume. The scope and design of the back-end requests should make it possible to limit the number of requests.

Use Case

Source code checks track API calls parameters to avoid unlimited returns. Development tools & browser console are used to track network flows, size & frequency (CHROME: console / network)

Opquast 9 / GreenIT 9

Additional elements

Operational issues related to the project

Posts

Rule for assessing the level of compliance of the criterion

Size of network transfer compressed / Size of network transfer

Life cycle

Réalisation

3 other criteria related to the recommendation: Limit the volume of exchanges

Recommendation Essential

Flux

Is the data exchanged compressed before transmission ?

Recommendation

Flux

Is pagination used on data exchanges ?

Recommendation

Flux

Does the data exchanged match the immediate need only ?