If I had to summarize what specifically could be improved in Debian, the only thing I would do is rolling release, as some other operating systems are doing. I can see why they do not do it, but I can also see that it would be helpful so that if there are things done better in a newer kernel, that could be integrated in quicker. I usually build my own kernels to suit specific applications for specific customers, and it pays to do that anyway with any Linux. I find Debian tends to have all of the switches available in their kernel build so that you can turn features on or off, include them, or leave them out, whatever you need to do.
One of its virtues is also one of its problems. 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. Therefore, if I want something, I have to go to trusted external repositories or compile something manually to be on the cutting edge. That is the only downside I see.
It is an old stack, and I am not necessarily a fan of PHP, to be honest. This is not improving LAMP Stack Debian but changing it. I am not necessarily a fan of PHP, but it is very performant and it uses very little resources. I also like using other stacks as well. How can it be improved? LAMP Stack Debian itself, I do not think can be improved; it is continuously updated with MySQL and with the proxy that is in there, the MySQL database that is in there, and the PHP server. I do not think it can be improved; there are other more contemporary stacks that might be interesting to consider, but LAMP Stack Debian is always updated. Things the .htaccess file can sometimes be a bit finicky with the Apache proxy. I think that will become then a different stack, and the Apache HTTP server is not a proxy. It is what it is; it is very much proven. If you change that, then it is not proven anymore.
LAMP Stack Debian can be improved by addressing the lack of a built-in caching mechanism. For example, I could integrate tools like Redis or Memcached, as it is reliant on the database side, like MySQL, without caching features currently available in the market.One needed improvement is the caching feature mentioned. Otherwise, I do not think there is any improvement required, and if future concerns arise, I will update accordingly.
Senior Software Engineer at a computer software company with 501-1,000 employees
Real User
Top 5
Jan 20, 2026
Regarding areas of LAMP Stack Debian that could be improved or enhanced, while it is very nice as is, one area might be the caching mechanism. It could be beneficial to integrate popular caching tools such as Redis or Memcache instead of solely relying on MySQL's database caching features. This could be a good thing to consider.
LAMP Stack Debian 10 offers a robust, open-source platform for developing and hosting web applications. Leveraging Linux, Apache, MySQL, and PHP, it provides a stable and flexible environment tailored for scalable web solutions.
Widely respected for its reliability, LAMP Stack Debian 10 is a preferred choice for developers seeking to deploy secure and efficient web applications. This ecosystem combines easy setup processes with solid performance metrics, advantageous for enterprises aiming to...
If I had to summarize what specifically could be improved in Debian, the only thing I would do is rolling release, as some other operating systems are doing. I can see why they do not do it, but I can also see that it would be helpful so that if there are things done better in a newer kernel, that could be integrated in quicker. I usually build my own kernels to suit specific applications for specific customers, and it pays to do that anyway with any Linux. I find Debian tends to have all of the switches available in their kernel build so that you can turn features on or off, include them, or leave them out, whatever you need to do.
One of its virtues is also one of its problems. 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. Therefore, if I want something, I have to go to trusted external repositories or compile something manually to be on the cutting edge. That is the only downside I see.
It is an old stack, and I am not necessarily a fan of PHP, to be honest. This is not improving LAMP Stack Debian but changing it. I am not necessarily a fan of PHP, but it is very performant and it uses very little resources. I also like using other stacks as well. How can it be improved? LAMP Stack Debian itself, I do not think can be improved; it is continuously updated with MySQL and with the proxy that is in there, the MySQL database that is in there, and the PHP server. I do not think it can be improved; there are other more contemporary stacks that might be interesting to consider, but LAMP Stack Debian is always updated. Things the .htaccess file can sometimes be a bit finicky with the Apache proxy. I think that will become then a different stack, and the Apache HTTP server is not a proxy. It is what it is; it is very much proven. If you change that, then it is not proven anymore.
LAMP Stack Debian can be improved by addressing the lack of a built-in caching mechanism. For example, I could integrate tools like Redis or Memcached, as it is reliant on the database side, like MySQL, without caching features currently available in the market.One needed improvement is the caching feature mentioned. Otherwise, I do not think there is any improvement required, and if future concerns arise, I will update accordingly.
Regarding areas of LAMP Stack Debian that could be improved or enhanced, while it is very nice as is, one area might be the caching mechanism. It could be beneficial to integrate popular caching tools such as Redis or Memcache instead of solely relying on MySQL's database caching features. This could be a good thing to consider.