My customers primarily use Red Hat Enterprise Linux for application hosting and small databases. It is used for hosting Java applications and small web servers.

Cloud-based Red Hat Enterprise Linux deployments provide cost savings. If customers are purchasing a physical server, they need to have a proper setup. They need to have a data center, cabling, and a lot of other things. For cost-saving purposes, they are going for a cloud. As an operating system, it offers the same functionality on-prem or on the cloud.

It saves money for company owners. It helps our customers save money and do things quickly. They can build servers quickly. There is a menu where they can fill in the VM name and other details and attach storage. In ten minutes, they have a server ready.

I am Red Hat certified. I train people in corporations and educational institutes. Red Hat's material is very good. Their testing system is awesome. If someone is certified in Red Hat, you know that they know it well. There are millions of videos on YouTube, but they are not always updated. On the Red Hat site, the documentation is very clear. You just need to focus and study for two to three months to get certified.

Nowadays, delays are common with their support, and it often takes time to get assistance from experienced engineers.

I have been using Red Hat Enterprise Linux for seven to eight years.

Red Hat Enterprise Linux is an excellent product, and its stability has improved significantly over time. It can operate for extended periods, like six months to one year, without issues.

Red Hat Enterprise Linux scales well with increasing user demands or infrastructure size. It is easily available and efficiently adapts to varying needs.

Most customers host medium-sized applications on the cloud. Storing a big application can lead to higher costs.

The technical support from Red Hat has declined over the past four or five years. It could be because there are not many skilled people. When we raise a case, it is attended by junior people or new people, which wastes two to three days. We might even have to raise the severity of the ticket. However, when senior people take ownership of the case, the support is awesome. They give proper support. This was not the case earlier, so whenever we raised a ticket, we got an immediate response from Red Hat.

Positive

The initial setup is smooth.

We have Cloud-based deployments. We are using AWS, GCP, Azure, and other cloud platforms. We also have on-premises deployment. Some customers also have a mixed deployment with the cloud and on-prem but in such environments, I have seen problems in terms of performance. For example, if my database is on-prem on Red Hat Enterprise Linux, and I am storing my application on the cloud on Red Hat Enterprise Linux, whenever someone hits the website, there will be latency issues. I sorted out such issues for a customer. I suggested they migrate their server from the cloud to on-prem because their database was quite big. With a mixed setup, they were having a lot of issues in terms of performance and storing data. It was very slow. After they moved it on-prem, it was much faster. This is not a Red Hat-related issue. From the operating system side, no improvements are required. However, cloud providers need to improve their facilities.

For patching, I use Red Hat Satellite, and for configuration, I use Red Hat Ansible. Leapp upgrades are also awesome. A month back, I upgraded Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9. I created detailed documentation about the procedure. There were about 14 steps. It was straightforward.

With Red Hat Insights, we can see the security threats. Red Hat Insights is integrated with Red Hat Satellite. It will be helpful from the patching point of view. It lets you do subjective analytics of servers.

I did some research on pricing a long time ago, and at that time, it was much cheaper than Windows. I do not have current details about pricing, but it is affordable.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten.

The primary use case for Red Hat Enterprise Linux is automation. We have Ansible running on some Red Hat Enterprise Linux servers, and a lot of it is geared towards automation. We have the automation of processes like patching, upgrades, OS enhancements, or OS upgrades. Additionally, our stores run on Red Hat Enterprise Linux.

Red Hat Enterprise Linux is pretty secure, but we rely on our network products to handle a lot of our security. We have Cisco products. These servers that we are currently running are not necessarily tightened down on the ports, traffic, etc. We rely on Cisco firewalling to handle a lot of the traffic, load balancing, and so forth. I have not configured a lot of security per se right on the server itself at a kernel level.

I like the knowledge base. They have a pretty good knowledge base portal. On their website, they have a lot of great classes. I do appreciate doing that. I have taken several myself, so I am pretty impressed by that.

We use Ansible Playbooks for patching our devices, especially those that are out in the field. We are using Ansible Playbooks to handle patching. We are using the systemctl command that goes into the repos to grab whatever patches we need. So far, the management experience has been good.

I have used a lot of different Linux distributions, and one thing that I like about Red Hat Enterprise Linux is the support. The support from Red Hat is very good. They offer excellent customer and vendor support. 

The ease of training is great, and I appreciate products like Ansible Tower. 

Its interface is good. It is a very solid operating system.

Some of the documentation that I have run into or encountered appeared to be a bit outdated. That would be an area for improvement.

I have been using Red Hat Enterprise Linux since early 2000. It has been about 20 years.

Red Hat Enterprise Linux is very stable. I have not experienced any instances of crashing with the Red Hat servers that I have worked on.

Other than the issues with the legacy software or some of the IBM AS/400 that we tried to add to it, it has been pretty seamless. Building them out and migration to the data center or the VMware environment has been pretty seamless. 

Customer service is great. We use a support portal to open a ticket, and the response time is good. We usually get an email response or an update to the ticketing system, and then if necessary, we get a callback within four hours. The response time also depends on the priority. If we are looking at a massive data center outage, I am sure it is a priority one. Most of the tickets I submitted took one to four hours.

Positive

I have used SUSE in the past. They have a pretty good support system. They have got a good OS. I am not sure what the market share is for those guys, but they are pretty good.

Our environment is a combination of the cloud and on-premises, but we primarily use Red Hat Enterprise Linux on-prem. We have a few development test servers running on Azure. They are not used in production. They are just for testing.

I was involved with the migration from SUSE to Red Hat, but that was close to a decade ago.

From what I recall, the initial setup was not that difficult. We did have some engineers from Red Hat who came out to help us. It would have been more difficult if we did not have them there, but from my recollection, it was not very challenging or difficult. We were able to get that done pretty quickly. There were some issues with legacy software, but those applications were built on the Windows platform. They were a little bit of a mess. Other than that, it appeared to go pretty smoothly for us.

It does not require much maintenance. Other than patching and keeping up with bulletins as to what might be out there, there is not much. There is not a huge amount of maintenance. They run pretty solidly. The uptime is great. I do not have to restart a lot of these servers. I might have to restart a service here and there, but nothing that I can remember.

We had help from Red Hat engineers during the implementation.

Red Hat Enterprise Linux provides a much more secure and stable system than Windows infrastructure, and the support is also great. Of course, you pay for the support.

We were able to see its benefits after some time. Some of the returns are seen after a while, not immediately. Sometimes, migrations might be difficult to do if you are running legacy software.

I am not involved in the budgetary aspect, but from what I understand, the pricing is competitive, similar to what we paid for SUSE.

Having a solid foundation in Linux can be very helpful. Learn as much as possible. Automation has become a very important part of the industry now. Learning how to automate with Ansible, Kubernetes, Docker, and Python along with Red Hat Enterprise Linux should set you up for success.

We have not tried Red Hat Enterprise Linux Image Builder or System Roles. Image Builder sounds good, but I have not tried Image Builder. We build our images from vCenter. Image Builder would definitely be something to check out.

Using it in a hybrid environment is a very interesting concept, where we keep some of the hardware and applications on-prem and then maybe rely on Red Hat to handle some of the networking or other configurations externally. I would like to try that hybrid approach.

I would rate Red Hat Enterprise Linux an eight out of ten.

We use Red Hat Enterprise Linux as our server operating system to install and configure various applications. Its uses include system troubleshooting, DNS configuration, and many other tasks, especially in a mixed environment with Ubuntu.

Patching Red Hat Enterprise Linux in our environment is a straightforward process that utilizes Red Hat Satellite. We identify necessary patches for production servers in the content view and notify customers two days in advance via email. Before patching, we verify the Nagios servers for identification purposes. We then execute a pre-configured Ansible playbook to efficiently patch our 300 servers. This playbook was already established, and our only interaction with it is to run it.

The web console is handy, especially for tasks like command line operations. Its secure environment allows for the safe execution of queries.

Red Hat Enterprise Linux is most valued for its reliability, as evidenced by my daily use.

The documentation needs improvement. Providing more detailed explanations would make it easier to work on projects.

I have been using Red Hat Enterprise Linux for my entire career, which spans over eight years.

Red Hat Enterprise Linux is stable. There has been no significant issue regarding lagging or downtime.

Red Hat is highly scalable and essential in the industry. I would rate scalability nine out of ten.

The customer support from Red Hat is good. They are always there to help when needed.

Positive

I have used Ubuntu, and Kali Linux alongside Red Hat.

I have been involved with migrations to Red Hat Enterprise Linux, which are not complex. For example, migrating to Red Hat Enterprise Linux 7 or 8 is easy, requiring only the installation of necessary dependencies and the creation of a file to sync files to the new system.

I typically work as part of a team rather than implementing integrations on my own.

Red Hat Enterprise Linux is quite expensive, particularly its technical support, which can cost $500 per hour.

I would rate Red Hat Enterprise Linux nine out of ten.

Realizing the benefits of Red Hat Enterprise Linux took time, as post-deployment troubleshooting was often necessary. This included tasks like opening ports and verifying functionality, which were sometimes prerequisites for the system to operate. These requirements varied depending on the specific application used and its security needs.

We perform maintenance on Red Hat Enterprise Linux every weekend, including backups. Incremental backups are done daily, while full backups are completed every weekend.