Software Engineer at a outsourcing company with 5,001-10,000 employees
Real User
Top 20
Jun 23, 2026
LAMP Stack CentOS could be improved in terms of configuration being a little easier. For new developers or new users, configuring and deploying production servers is a little complex compared to easier options such as Docker. If we could have the same capabilities that Docker provides for deploying products, that would help.
An area for improvement I can think of is the setup and installation process, which can be challenging. Making it easier by breaking it down into chunks or transitioning from a monolithic architecture to microservices could enhance the installation experience.
Senior System Specialist at a transportation company with 51-200 employees
Real User
Top 20
Jun 16, 2026
Regarding how LAMP Stack CentOS can be improved, I would add a few points. Over the two decades of optimizations, the relational integrity that MariaDB and MySQL handle for complex data relationships and transactional integrity is perfect. The cost efficiency is also excellent. LAMP Stack CentOS's scalability is good so far, but there are some challenges as well. As we enter the agentic AI, achieving stability in LAMP Stack CentOS depends entirely on managing traditional web infrastructure. I manage the web infrastructure easily via LAMP Stack CentOS. However, when I try agentic AI, instability does not mean server uptime. I mean execution predictability and preventing logical failure. Therefore, AI in LAMP Stack CentOS becomes unstable and exhibits special behavior. LAMP Stack CentOS is stable in my experience; however, sometimes when more traffic comes and hits, it fluctuates. When we need to upgrade, there are some difficulties in LAMP Stack CentOS. Suppose I need to use MySQL 8 in my production environment but my LAMP Stack CentOS is outdated. At that time I need to upgrade the full stack to maintain it. If I use Apache, MySQL, and PHP separately, my DBA can normally upgrade MySQL, and my developer can upgrade PHP. However, when I use LAMP Stack CentOS, the whole team combination is needed, and then we can upgrade the full stack. This is the challenge so far.
The bigger area for improvement for LAMP Stack CentOS is overall ecosystem lifecycle predictability. Since CentOS pivoted to the CentOS Stream rolling model, it serves as a midstream delivery platform rather than a static downstream clone. This makes it trickier to use for hyper-conservative production web stacks that cannot risk upstream package updates occasionally shifting beneath them. The documentation for LAMP Stack CentOS can be improved. The technical details are sometimes missing and technical errors sometimes lack any documented details. The default native app stream repositories often include older or hyper-conservative versions of PHP. To get modern, performant PHP versions such as 8.2 or 8.3 for LAMP Stack CentOS, you almost always have to rely on third-party repositories such as Remi or EPEL. It would be much better if newer or fully supported PHP versions were more aggressively maintained in the core stream.
I believe LAMP Stack CentOS could be improved by focusing on security enforcement, which would be beneficial. I would appreciate specific security improvements for LAMP Stack CentOS, such as enforcing some security modules like mod_ssl that we need to configure. There are no other improvements needed for LAMP Stack CentOS that I have not mentioned.
LAMP Stack CentOS can be improved by tracking the CVEs and releasing fixes as fast as possible. The release cycle of CentOS packages and Red Hat packages sometimes is a bit slow, so I do not always have the latest releases or I experience a delay for related releases, the same applies to CVE fixes.
LAMP Stack CentOS offers a reliable platform for deploying web applications. By combining Linux, Apache, MySQL, and PHP on a CentOS operating system, it provides a consistent environment for building and running complex web applications.This solution is commonly used in web hosting and IT environments due to its open-source nature, making it cost-effective and flexible. LAMP Stack CentOS is valued for its stability and security, which are critical for developing and maintaining web...
LAMP Stack CentOS could be improved in terms of configuration being a little easier. For new developers or new users, configuring and deploying production servers is a little complex compared to easier options such as Docker. If we could have the same capabilities that Docker provides for deploying products, that would help.
An area for improvement I can think of is the setup and installation process, which can be challenging. Making it easier by breaking it down into chunks or transitioning from a monolithic architecture to microservices could enhance the installation experience.
Regarding how LAMP Stack CentOS can be improved, I would add a few points. Over the two decades of optimizations, the relational integrity that MariaDB and MySQL handle for complex data relationships and transactional integrity is perfect. The cost efficiency is also excellent. LAMP Stack CentOS's scalability is good so far, but there are some challenges as well. As we enter the agentic AI, achieving stability in LAMP Stack CentOS depends entirely on managing traditional web infrastructure. I manage the web infrastructure easily via LAMP Stack CentOS. However, when I try agentic AI, instability does not mean server uptime. I mean execution predictability and preventing logical failure. Therefore, AI in LAMP Stack CentOS becomes unstable and exhibits special behavior. LAMP Stack CentOS is stable in my experience; however, sometimes when more traffic comes and hits, it fluctuates. When we need to upgrade, there are some difficulties in LAMP Stack CentOS. Suppose I need to use MySQL 8 in my production environment but my LAMP Stack CentOS is outdated. At that time I need to upgrade the full stack to maintain it. If I use Apache, MySQL, and PHP separately, my DBA can normally upgrade MySQL, and my developer can upgrade PHP. However, when I use LAMP Stack CentOS, the whole team combination is needed, and then we can upgrade the full stack. This is the challenge so far.
The bigger area for improvement for LAMP Stack CentOS is overall ecosystem lifecycle predictability. Since CentOS pivoted to the CentOS Stream rolling model, it serves as a midstream delivery platform rather than a static downstream clone. This makes it trickier to use for hyper-conservative production web stacks that cannot risk upstream package updates occasionally shifting beneath them. The documentation for LAMP Stack CentOS can be improved. The technical details are sometimes missing and technical errors sometimes lack any documented details. The default native app stream repositories often include older or hyper-conservative versions of PHP. To get modern, performant PHP versions such as 8.2 or 8.3 for LAMP Stack CentOS, you almost always have to rely on third-party repositories such as Remi or EPEL. It would be much better if newer or fully supported PHP versions were more aggressively maintained in the core stream.
I believe LAMP Stack CentOS could be improved by focusing on security enforcement, which would be beneficial. I would appreciate specific security improvements for LAMP Stack CentOS, such as enforcing some security modules like mod_ssl that we need to configure. There are no other improvements needed for LAMP Stack CentOS that I have not mentioned.
LAMP Stack CentOS can be improved by tracking the CVEs and releasing fixes as fast as possible. The release cycle of CentOS packages and Red Hat packages sometimes is a bit slow, so I do not always have the latest releases or I experience a delay for related releases, the same applies to CVE fixes.