Recommendation : 1. Reduce the impact of data from its storage and access
Is the removal of obsolete data being managed ?
Data
C People
A Planet
A Prosperity
Difficulty
**
Priority
High
Récurrence
Periodic
Tests
Are data lifetimes managed?
Precisions
The regulations require control of the data life cycle for certain categories (for e.g.: personal data governed by the RGPD). Lack of consideration to other categories of data leads to the accumulation of data without taking into account their expiry dates, which increases the volume of data, the volume of backups and the resources consumed by accessing the data. Over time, the level of detail of the data becomes less important, which should lead to a reduction in the volume of data, preceding its eventual removal.
Use Case
Impact assessment define actions and stakeholders involved in impact reduction
Additional elements
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
Life cycle
Fin de Vie
19 other criteria related to the recommendation: Reduce the impact of data from its storage and access
Data
Is the number of requests kept to a minimum (no looping) ?
Data
Are the slow query detection thresholds set effectively ?
Data processing
Does regulated data (personal, health, financial) comply with the recommendations for structuring these categories of data ?
security
Is sensitive user data secure ?
Data processing
Does the API provide limits, filters and the list of fields to return ?
Data processing
Is the data collected really useful ?
Data processing
Is sensitive data collected ?
Data processing
Does the data have an expiration date when it is deleted ?
Data
Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?
Data
Is frequently accessed data available in RAM ?
Data
Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?
Data
Are EXPLAIN clauses used on "Slow queries" to optimize indexes ?
Data
Have the different data access solutions (queries, triggers, stored procedures) been tested ?
Data
Is a NoSql solution more efficient than its relational equivalent ?
Data
Is an alternative to the relational model being considered ?
Data
Are database indexes consistent with operations ?
Data
Can data be backed up incrementally ?
Data
Do implemented queries use joins rather than multiple queries ?
Data
Is an alternative to SQL queries used when possible (local storage or similar) ?