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: Performance
Filtered by:
Is the number of requests kept to a minimum (no looping) ?
Does the data have an expiration date when it is deleted ?
Are data replications between multiple Database Engine (Cluster) instances appropriate for sensitivity and availability requirement ?
Is frequently accessed data available in RAM ?
Are "live" and "dead" data handled differently (eg: Slow storage for "dead" data) ?
Are database indexes consistent with operations ?
Is the removal of obsolete data being managed ?
Do implemented queries use joins rather than multiple queries ?
Do interactions between components benefit from caching mechanisms ?
Is the security implemented justified with regard to the operations carried out ?
Are the browser caches not being blocked by the framework or technology used ?
Does service availability require redundancy ?
Are unused resources freed up as quickly as possible ?
Is the data exchanged compressed before transmission ?
Is pagination used on data exchanges ?
Is the number of requests between the client and the server kept to a minimum ?
Does the data exchanged match the immediate need only ?
Is code analysis used in the continuous integration process ?
Are code quality metrics being tracked ?
Is the envisioned functionality useful ?
Does the sizing of infrastructure resources follow the life of the application ?
Is the technical architecture permanently in line with the activity of the service ?
Are de-provisioning operations expressed at design time ?
