Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Backend    ODD#12     ODD#13    

Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?

Recommendation 

Data

C People

B Planet

B Prosperity

Difficulty

***

Priority

Low

Récurrence

Periodic

Tests

How much inactive data is kept?

Precisions

Historical data must be retained for legal reasons or service functionality. The usage rates of inactive data do not justify the use of high performance storage systems. The most efficient storage solutions are also often those that consume the most energy or have the shortest lifespan.

Use Case

Impact assessment

Additional elements

Operational issues related to the project

Posts

Rule for assessing the level of compliance of the criterion

Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100

Life cycle

Fin de Vie

19 other criteria related to the recommendation: Reduce the impact of data from its storage and access

Recommendation Essential

Data

Is the number of requests kept to a minimum (no looping) ?

Advice

Data

Is an alternative to SQL queries used when possible (local storage or similar) ?

Recommendation

Data

Do implemented queries use joins rather than multiple queries ?

Advice

Data

Can data be backed up incrementally ?

Recommendation

Data

Is the removal of obsolete data being managed ?

Recommendation

Data

Are database indexes consistent with operations ?

Advice

Data

Is an alternative to the relational model being considered ?

Advice

Data

Is a NoSql solution more efficient than its relational equivalent ?

Advice

Data

Have the different data access solutions (queries, triggers, stored procedures) been tested ?

Advice

Data

Are EXPLAIN clauses used on "Slow queries" to optimize indexes ?

Advice

Data

Are the slow query detection thresholds set effectively ?

Recommendation

Data

Is frequently accessed data available in RAM ?

Recommendation

Data

Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?

Recommendation

Data processing

Does the data have an expiration date when it is deleted ?

Recommendation

Data processing

Is sensitive data collected ?

Recommendation

Data processing

Is the data collected really useful ?

Recommendation

Data processing

Does the API provide limits, filters and the list of fields to return ?

Recommendation

security

Is sensitive user data secure ?

Advice

Data processing

Does regulated data (personal, health, financial) comply with the recommendations for structuring these categories of data ?