How many times have I seen projects solve this problem in this way?
or the equivalent, of the web connection pool, of the CRM access pool, of the ticketing...
However, it's like that old bullet impact map from 1945, the evidence is misleading and I like simplicity too much to pervert it into simplism.
In reality, when a base is saturated, it is necessary to reduce the number of connections to smooth out traffic. Response times will certainly increase, and users will have to wait for resources to be released, but once they are available, requests will be executed quickly.
It's the same reason that pushes stores during sales periods to restrict entrances or motorway operators to close lanes and reduce speeds when people go on holiday to avoid traffic jams due to traffic irregularities.
I take off my hat from the professor I was: the performance of a system (whether it be road, IT, hydraulic, etc.) is governed by its most critical point. In case of system saturation, any action that aims to increase the resources of non-critical points can generate an even greater pressure on the critical point and thus make the flow even more difficult, or even interrupt it completely. It is often more interesting to limit the traffic upstream of the critical point, in order to smooth the flow. Remember that in case of performance problem, adding or freeing resources, if they are not the critical resources themselves, can aggravate your problems instead of solving them.
> Paradox of security, or Voltaire’s fault
When I think of the second case, I think it resembles an old maxim. switzerland telegram data "The best is the enemy of the good," wrote Voltaire in the 18th century.
I understand that your systems are becoming more and more complex. Ah, that word, "complex", that you use at every turn and which unfortunately means your subjection to a system that you no longer understand.
You need 8 characters including at least 3 numbers, 2 capital letters, 2 special characters among... and the word must not resemble the last 5, nor correspond to the blacklist of obvious passwords.
Choosing a password now requires intellectual gymnastics of a force 9 sudoku level intensity.
Administrators, wanting at all costs to secure the system of which they are the guardians, define increasingly restrictive password policies, with an obligation to change every 3 to 6 months.ust have certain qualities. So yes, we can focus on the scars of the survivors' lives... However, wouldn't it be wiser to look for the characteristics that allowed certain applications to stand the test of time? I have the weakness to believe that plunging your applications into simplicity is also bathing them in a fountain of youth...
And blessed are the skimmers of new technologies, challenged by time, they only pass through...