Hosting dynamic sites and blogs has become cost-effective and runs reliably for years
What is our primary use case?
My main use case for LAMP Stack Debian is hosting dynamic web applications which are in HTML and PHP, and also hosting WordPress applications inside the LAMP Dev stack.
What is most valuable?
The best features LAMP Stack Debian offers include stability and reliability, which are paramount when installing any setup and performing anything in production. LAMP Stack Debian is very stable and reliable, containing security updates which are thoroughly tested. Furthermore, its entire stack is open-source, so there is no licensing cost, making it cost-effective and easy to manage.
LAMP Stack Debian has impacted my organization positively because it is easy to set up and there is no cost related to licensing since the entire stack is open-source. Therefore, there are no licensing costs and it is easily manageable. I can install packages by using APT package management, write scripts, and integrate it with any third-party software. For example, if I am running a MySQL database, I can integrate it by installing phpMyAdmin to manage my database.
What needs improvement?
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.
For how long have I used the solution?
I have been using LAMP Stack Debian for the last five years.
What do I think about the stability of the solution?
LAMP Stack Debian is very stable.
What do I think about the scalability of the solution?
Its scalability is very commendable.
How are customer service and support?
The customer support for LAMP Stack Debian is excellent.
Which solution did I use previously and why did I switch?
Previously, I used Nginx and other solutions. The reason for switching is that with LAMP Stack Debian, I get the whole stack without needing to install all the tools individually, such as Apache, MySQL, and other components.
How was the initial setup?
My experience with pricing, setup cost, and licensing is very reasonable, as there are no licensing fees since it is an open-source stack.
What was our ROI?
I have seen a return on investment, as a stable system with no downtime leads to significant revenue and time savings from not having to repeatedly check the system and perform root cause analysis accordingly. I have experienced both time and money saved thanks to LAMP Stack Debian because by not paying a significant amount for licensing costs, considerable savings are achieved. Additionally, time is saved because it is very stable with no frequent downtimes. I can easily upgrade packages as one does in Ubuntu, and I can set up multiple automated scripts within this system.
Which other solutions did I evaluate?
Before choosing LAMP Stack Debian, I evaluated Nginx, but LAMP Stack Debian is one of the most efficient stacks, providing a whole range of software in one package, which led me to choose it.
What other advice do I have?
My advice to others looking into using LAMP Stack Debian is that if they want to host their static and dynamic websites and set up WordPress and other tools like Laravel, then they should definitely go with the Debian-based LAMP Stack Debian because it is very reasonable and cost-effective. Additionally, it is very stable. I would rate this product a 9.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Web platform has supported reliable deployments and security while caching still needs improvement
What is our primary use case?
I use LAMP Stack Debian to serve a web application. We use LAMP Stack Debian as the Linux environment to serve the application and configure the components of the web application by writing custom PHP scripts. We use the MariaDB MySQL binary version to store data and to create databases. We use it for a large enterprise application, and it has proven to be very suitable for us. We have various portals and other functionalities that I prefer not to discuss in detail, so I can say it offers very good benefits based on these factors.
What is most valuable?
The most valuable feature of LAMP Stack Debian is the way that you can make your changes and have those changes reflected exactly as you made them. The configurations that you can do inside the HTML directories of Linux and the security of the database, along with the integration between PHP and MariaDB, are some of the things that I admire.
I have utilized LAMP Stack Debian's integration features. Since I use the Debian version, we use package managers such as APT and we can write automated setup scripts. If you want an automated setup, you can use the PHPMyAdmin tool for easier database management. I also appreciate that it is open source and free, which reduces the costing fee that the company has to withdraw from its accounts. Additionally, it has a vast community where you can find different kinds of documentation for troubleshooting and potentially upgrading the application.
The versatility of LAMP Stack Debian for different web applications is valuable because, as I mentioned earlier, one of its common features is the package management. Since it is a Debian installation, we use the default package manager, making it easier and very versatile for integrations with MariaDB servers or PHP servers. You can have different updated software packages, and if you want to perform optimizations and configurations, you can use it on cloud platforms such as AWS. There are also pre-configured images that you can use for these tasks. Regarding versatility, I can say it is very versatile and easily scalable for increasing your infrastructure.
The security updates for LAMP Stack Debian have helped my projects, as we try to keep up with the security updates released regularly. We make sure to apply those updates to maintain our safety. Regular patching is part of our routine whenever there is an update for these features. It is very easy to implement these changes, and we can upgrade using the uncomplicated firewall feature of Linux. You can allow different kinds of ports and perform SSH to access those servers. I also appreciate MySQL database as a nice tool for setting up security mechanisms, allowing remote logins from other IPs and users, as well as the ability to create and remove testing databases easily.
The benefits and positive impact I have seen since starting to work with LAMP Stack Debian include cost-effectiveness, as it is open source and free with no licensing issues to handle. I appreciate the documentation and resources available.
What needs improvement?
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.
For how long have I used the solution?
I have been working with LAMP Stack Debian for approximately seven months.
What do I think about the stability of the solution?
I think LAMP Stack Debian is pretty reliable. We have actually proven that during multiple incidents. A couple of months back, we faced issues with cloud providers, and we could easily manage those incidents without experiencing significant downtime. It is very stable and reliable, capable of handling high traffic loads, and has various package components that can be added.
What do I think about the scalability of the solution?
The scalability level of LAMP Stack Debian is very high, based on the web servers and the database. You can independently scale up the server size or the different resources that the server depends upon, and if you want to scale the database independently, you can do that without disrupting the server. That is what I mean by scalability; it is easier to perform scalability adjustments.
Which solution did I use previously and why did I switch?
Before LAMP Stack Debian, it was not my preference. I joined a company that uses LAMP Stack Debian some months ago, and they were already utilizing that stack. I had some experience before that, which helped me refine my skills. While modern JavaScript frameworks can provide similar functionalities, my company preferred LAMP Stack Debian over other more modern frameworks.
How was the initial setup?
My experience with the initial setup of LAMP Stack Debian is that it is pretty easy the first time I install it. We do not have to go through too many integrations and installations because the Linux part can easily provide a good package manager, APT, which can get you the necessary components in minutes or even less than that in some cases. It is a very straightforward installation.
What other advice do I have?
I do not know where my company purchased this solution from. I do not think it is a purchased one. You can just integrate those different stacks together in a Linux server.
Until now, I have not used formal community support for LAMP Stack Debian, but I did check the documentation available on the official site of PHP, and it is very helpful for troubleshooting tasks.
My overall review rating for LAMP Stack Debian is seven out of ten.
showing 1 - 2