Family Backend | 6 recommendations - 72 criteria
The backend represents the computer translation of business processes, the technical means and data implemented for their use, as well as all the external interactions implemented for their realization.
Filtered by :
Data
Is the number of requests kept to a minimum (no looping) ?
Data
Is an alternative to SQL queries used when possible (local storage or similar) ?
Data
Do implemented queries use joins rather than multiple queries ?
Data
Can data be backed up incrementally ?
Data
Is the removal of obsolete data being managed ?
Data
Are database indexes consistent with operations ?
Data
Is an alternative to the relational model being considered ?
Data
Is a NoSql solution more efficient than its relational equivalent ?
Data
Have the different data access solutions (queries, triggers, stored procedures) been tested ?
Data
Are EXPLAIN clauses used on "Slow queries" to optimize indexes ?
Data
Are the slow query detection thresholds set effectively ?
Data
Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?
Data
Is frequently accessed data available in RAM ?
Data
Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?
Data processing
Does the data have an expiration date when it is deleted ?
Data processing
Is sensitive data collected ?
Data processing
Is the data collected really useful ?
Data processing
Does the API provide limits, filters and the list of fields to return ?
security
Is sensitive user data secure ?
Data processing
Does regulated data (personal, health, financial) comply with the recommendations for structuring these categories of data ?
Quality
Is the documentation of the functionality available to enable its reuse ?
Performance
Is the web server used asynchronous and multi-threaded ?
Performance
Has the dependency tree of the integrated components been evaluated ?
Performance
Can dependencies be reduced by using an alternative component ?
Performance
Is the user informed of a processing in progress in the background ?
Performance
Has the integration of asynchronous processing been evaluated ?
Performance
Are unused resources freed up as quickly as possible ?
Performance
Is a VM necessary as opposed to a container solution ?
Performance
Does service availability require redundancy ?
Architecture
Do interactions between components benefit from caching mechanisms ?
Architecture
Are the browser caches not being blocked by the framework or technology used ?
Architecture
Is there a lighter framework / library that meets the functional need ?
Architecture
Is an Open Source solution available for the functional need ?
security
Are the versions of the components used tracked and deployed ?
security
Is the security implemented justified with regard to the operations carried out ?
Data processing
Is the level of logs adapted to the environment ?
Data processing
Are temporary files included in the "logrotate" ?
Flux
Is the data exchanged compressed before transmission ?
Flux
Is pagination used on data exchanges ?
Flux
Is the number of requests between the client and the server kept to a minimum ?
Flux
Does the data exchanged match the immediate need only ?
Flux
Are user notifications necessary ?
IU
Is SSO implemented when possible ?
Life cycle
What would be my dev reflex, to take into account the life cycle ?
Life cycle
Does each stakeholder have the latitude to make decisions that may influence the environmental footprint ?
Quality
Is code analysis used in the continuous integration process ?
Quality
Are code quality metrics being tracked ?
Quality
Are functionality test reports available and tracked ?
Life cycle
Have the tools for monitoring Sustainable IT performance been identified and made available to developers ?
Life cycle
Has an analysis of the application's consumption profile been performed ?
Life cycle
Does each version deployed follow the same process for qualifying for Sustainable IT performance ?
Conformity
Is the overview of data handling processes (GDPR) available ?
Conformity
Is the risk analysis (RGPD) carried out ?
Conformity
Is the RGAA taken into account ?
Conformity
Is regulated data (banking, health, etc.) secure ?
Conformity
Is regulated data used ?
Conformity
Does the service being designed comply with changes in society and in legislation ?
Conformity
Can the infrastructure provider disclose its environmental metrics ?
Life cycle
Is the envisioned functionality useful ?
Life cycle
Are the Sustainable IT aspects propagated and maintained across all stakeholders ?
Life cycle
Was a benchmark on the environmental criteria carried out for the choice of the infrastructure supplier ?
Life cycle
Does the design process / tools integrate the treatment of Sustainable IT requirements ?
Architecture
Does the sizing of infrastructure resources follow the life of the application ?
Architecture
Is the technical architecture permanently in line with the activity of the service ?
Architecture
Is a summary of use cases of the features available ?
Architecture
Are de-provisioning operations expressed at design time ?
Architecture
Are all the technical equipment used by the service identified ?
Architecture
Are the characteristics available for each equipment (year of construction, environmental performance data...) ?
Life cycle
Is each function of the service understood in terms of its importance in the service ?
Life cycle
Do secondary functions also have a lower impact on the environmental footprint ?
Life cycle
Is each phase of the life cycle identified with specific actions ?
Life cycle
IsLCA data reused in the event of an adaptation of an existing service ?