Como IT Director y profesional técnico verificado en PeerSpot (anteriormente IT Central Station), comparto evaluaciones objetivas basadas en el uso directo de herramientas en entornos de misión crítica: bases de datos, observabilidad, infraestructura cloud, seguridad y DevOps.
Cada análisis en PeerSpot refleja pruebas en entornos productivos reales evaluando:
By minimizing errors, minimizing time, with an incredible cost saving, eliminating database incidents, having a diff inspector against our baseline to know which client schemas are outdated or not up to date, to know what differences there are between the different schemas, this has produced an immense cost saving for us.
However, it lacks native multitenant orchestration, it has a lot of rigidity in checksum management with programmable code, and the use of native SQL within XML does not work entirely well.
The reduction of security leaks since we implemented GitGuardian Platform has been drastic and we have brought the indicator down to zero percent of secrets revealed within the code.
GitGuardian Platform has the occasional false positive in testing.
The only way I have to see the costs is via CloudCheckr.
The interface could be improved because it is too dense and overloaded with too many charts and too much information on each screen.
The benefit is significant because it has resulted in a drastic reduction in downtime and maintenance costs, knowing that a routine security update will not break anything and that the PHP runtime environments and Apache configuration provide me with enormous peace of mind in my daily work.
The main drawback is the old age of the packages; in the stable branch, I do not get the latest versions of PHP, Apache, or similar software.
I think that the most important advantage of using LAMP Stack CentOS is low consumption of CPU.
I would like to see new functionalities or improvements in LAMP Stack CentOS because the packets are older than in other distros.