My main use case for Debian is primarily server-side and IoT, or Internet of Things devices. I work with small devices like a Raspberry or an ESP32 for small local software solutions or small hardware devices.
One specific example of how I use Debian on those devices is a Wi-Fi captive portal. When a customer enters the public Wi-Fi, they receive a Wi-Fi captive portal, which enables them to log in and use the company Wi-Fi while being registered and monitored. This includes some web application services and IPtables, which is the firewall, providing a secure environment for customers to access the company's Wi-Fi network.
Regarding my main use case with Debian, I also have website applications on the server side that are on the internal domain. For example, I have a building that is part of the company, and I want to monitor IP cameras or security features detecting motion, checking the temperature, and ensuring the fire alarm is working.
Debian offers features that are best for my needs, including being open source, which allows for the implementation of many things and the use of a wide variety of open-source tools. It is excellent for developing in a really short time, and it is also very sustainable and stable, meaning it works without any major software updates, and once you program it, it should be done.
Debian's stability and open-source nature have helped me in my work. For instance, I used to have a Windows-based server, which required a lot of dependency on third-party software, making it high-maintenance and costly. In contrast, with Debian, I can develop quickly with any code language, such as Python, Java, or JavaScript. The switch I made over the past three years made the process significantly less labor-intensive and maintenance-free.
In terms of cybersecurity, there is a Debian-based Linux operating system called Kali Linux. It has a wide range of tools helpful for penetration testing and network security. This aspect is intriguing and educational, whether for personal exploration or for the company if you want to dive into security topics such as zero-day exploits.
In terms of usability and integration with other systems, regarding sustainability, Debian is very user-friendly because the applications I use are most frequently web-based. As long as the system has a supported web browser, it works across different platforms including Mac, Windows, Android, or iOS, and that is where its user-friendliness shines.
Debian has positively impacted my organization primarily in cost-efficiency, with on-premises hardware running faster and cheaper.
Although I find the documentation very helpful and mostly utilize features built into the system itself or open forums, it would be nice to see a comprehensive website that encompasses not only Debian but also other Linux operating systems such as Red Hat or resources for IoT.
In my current field, I have been working for over ten years, but my current job is for approximately four years.
Debian is very stable, and I have experienced no issues whatsoever.
In terms of scalability, Debian on-premises is not very scalable because it depends on your hardware. However, solutions such as Amazon Web Services offer great scalability and flexibility.
I have never needed to reach out for customer support with Debian.
Before switching to Debian, I used Windows because it was higher maintenance and more costly.
Regarding return on investment, although I needed more employees, I cut down on licensing and maintenance costs, estimating around sixty percent savings percentage-wise.
My experience with Debian's pricing, setup cost, and licensing has been that it is all free.
I did not evaluate other options before choosing Debian; I went straight to it because it suited all my needs.
My advice for others looking into using Debian is to first build your own system as a proof of concept. Look for the applications or software you need by starting with Ubuntu if necessary, and then make it more efficient by removing unnecessary components. For example, if you do not need a graphical user interface because you are only using it server-side, then you should choose a lighter variant. I would rate this experience as an eight out of ten.