Red Hat Enterprise Linux (RHEL) Reviews

We use RHEL for database servers, a few of them run Oracle servers, and we are also using it for some of the network and infrastructure services.

The best operating system I've ever used is Red Hat, in terms of its ability and consistency of the operating system. Other than that, the vast majority of applications that I had, I could deploy those on Red Hat without much effort as it supported a vast majority of applications. I never faced any major issues with the OS, the support is also very good.

The most valuable features are:

• The stability and reliability of the OS itself
• Being open-source and leading the open-source market trends/ technologies
  
• The wide variety of applications we can deploy on Red Hat
• Their support 

I am a big fan of the OS and the user experience. They're very good. The OS is very stable and very good in performance as well.

RHEL enables us to deploy current applications and emerging workloads across all virtualized hybrid cloud and multi-cloud environments. It is one of the most stable OS that are available. 

We use RHEL to run multiple versions of the same applications and databases on a specific operating system. We have several deployments of database and a few of them are running on a bit older versions of Red Hat and some of them are running on newer versions. We are running different versions on different platforms. The management aspect is also very good, especially when we need updates on the different packages from the RH support network, management is easy.

We also use the tracing and monitoring tools to monitor OS as well as applications running on RHEL platform. The OpenShift is also a big plus through which you can manage and deploy enterprise-ready containerized workloads.

Being an advocate of open source technologies I always wished that Red Hat subscription/ support should be offered free of cost. Having said that, I understand the economics involved in running large enterprise like Red Hat; support cost is one area that can be improved. They should offer it at reduced prices.

I have been using RHEL since the start of my technical career, which was around the mid of 2003. So it's been almost 18+ years. I started using RH when it was version 7.

Stability has always been a plus for RHEL. 

Scalability is excellent. With the introduction of hybrid and multi-cloud support, one can scale up as well as scale out his workloads pretty easily. We usually scale up our traditional workloads when we need more resources i.e., during peak seasons. 

Four people in my team are responsible for deployment and support of Linux based workloads. 

We have around 300 virtual machines (VMs) and roughly 20% of them are running on Linux environment.

Whenever I open a case, I believe the support team will be able to solve my problem. They are very good at it. The documentation RHEL provides is also very good. Almost all the time, I get a solution to my problem. :)

We are using other flavors of Linux OSes, that include Oracle Enterprise Linux (OEL) and CentOS, both of which are binary compatible with RHEL. We are also using a couple of other Linux flavors like Ubuntu and OpenSUSE.

RHEL provides features that help speed our deployment. Installing on a physical server takes more time than installing it onto a virtual machine (VM).

Because of absence of local support in our part of the region, we did find some difficulties in the initial deployments with hardware vendors/ partners when we started in 2003. The local partners didn't have much knowledge of Linux environments at that time, and the support for hardware was also a bit tricky. The deployment took a couple of days until we got support from the hardware manufacturer.

Nowadays, it's very good. I managed to get good support from the hardware vendors after that incident.

We have our own deployment plans for the operating systems that include some baseline configurations and security checklists.

We usually deploy in-house as we have a trained team. Occasionally, little help is sought from the vendor teams, some of them have skilled professionals.

RHEL offers an efficient, cost-effective and reliable OS environment for enterprise-level environments. Similarly cost of running operations and the scalability factors make RHEL a good choice for providing a better ROI. The feature set it offers, support for a variety of applications, ease of deployment, and an excellent level of support all result in a good ROI. 

I believe for an enterprise-level operating system and the feature set RHEL offers, it's like any other enterprise platform cost. The introduction of OpenShift is also a big plus in terms of deployment and management of container based workloads. Red Hat as mentioned earlier can improve a bit on support/ subscription costs.

We had been using a couple of Red Hat variants for some scientific experiments that included Scientific Linux CERN (SLC) and Scientific Linux (SL), which were a confidence booster for choosing and deploying RHEL for production workloads.

Since I started with version RH 7, I believe the GUI is quite close to any other GUI operating system. There have always been a variety of tools and features that attract a non-Linux user.  As already mentioned, RHEL has been a pioneer in open-source technologies; it continued to evolve with changing market needs, that has been a big success for them.

I would definitely advise choosing RHEL if you need stability, scalability, and reliability of the OS platform. I would be a big advocate for the use of Red Hat to any new person who wants to deploy his production workloads, on-prem or on cloud on a Linux environment.

I would rate it a nine out of ten. It's near perfect. 

It's what we run our primary mission systems on. Our office automation runs on Microsoft, which includes Word, email, etc. For everything that we present to the customers through the agency, the backend is an RHEL platform.

Through the various tools that we've utilized, RHEL was able to help improve our security posture. We run a very tight ship.

We use Satellite to do patch management and limited repository so that we don't have folks going out to the internet to get the repos. You have to get the repos through our Satellite system. We also do patches through that. We use Ansible for our automation to build boxes, to install all the security patches on them, and to run the vulnerability scan against them. It initiates that. Also, implementing IdM on them is done through Ansible. So, we use Ansible quite a bit, and we're just starting with OpenShift.

One benefit of using multiple Red Hat products is compatibility. Compatibility is the most important. We haven't had an issue where the tool doesn't understand the OS or doesn't understand the platform. Ansible written for Red Hat works perfectly. It understands the plugins and satellites, and it's having one ecosystem where it also gives one phone call. If there's a problem, we call Red Hat. That has been very handy.

RHEL’s built-in security features and security profiles are very good for reducing risk and maintaining compliance, but as a government agency, we have to use other baselines. CIS baseline is what we primarily rely on. We also put in a little bit of DISA as a baseline, but they're standard out-of-the-box solutions. It's pretty good. It just has to be tweaked slightly to get it to the level we have to run at.

It's relatively easy to troubleshoot using RHEL. Sometimes, the troubleshooting can take quite a bit of work, but it's an easily understandable OS. If you understand the basic key principles, you can pretty much work it out.

We're very happy with the amount of security customization we've been able to do with RHEL. The fact that Red Hat is really on top of security issues is also valuable. We get daily emails from Red Hat letting us know of possible issues and fixes, which is incredibly helpful for us.

Other than that, we use it as our primary DNS. So, DNS is an important piece of it. 

Compatibility is also extremely important. We get the ability to run as many applications on it. They are widely supported.

There are some things that we've seen from RHEL that have given us a little bit of consternation. Their IdM product could be improved greatly. It would be great if they had some type of application built in that would let you do whitelisting for applications. On the government side, for zero trust, that's becoming very important. We're currently using a third-party solution, and it's tough to get it to match up because anytime the kernel changes, you have to match the software to the kernel. If we get a critical vulnerability on a kernel, we have to roll out the new kernel but then our third-party software isn't cooperating, and it starts breaking down the system. So, it would be great if Red Hat could integrate that type of functionality into the product so that when a new kernel comes out, it includes the updated software to do whitelisting and blacklisting of applications and processes.

At the agency, we have been using it for about 10 years. For me personally, it has been about six years.

It has been relatively stable. The only time we see stability issues is when we introduce new third-party products. We have some mandates as a government agency to do some endpoint security stuff and integrating that in has caused us a few stability issues, but that's not so much the fault of Red Hat. It's a quagmire of the chicken and the egg. You have to run a certain kernel, but that kernel is not compatible with the other software that you are forced to run. So, we've artificially created stability issues.

They eventually work out or work themselves out. When the vendors get on board and update their products to match the kernel, then everything tends to function smoothly at that point until we introduce another hiccup. We're constantly throwing hurdles, but we also have a very good system for bringing stuff back to life after it's dead, and we've done it enough that we're pretty timely. We can get one of our servers up in about 10 minutes.

It has been relatively scalable. We don't have any super large deployments, but we've had some scaling of specific applications, which has worked out great. We're integrating it more into Ansible and using our virtual hypervisor platform to recognize times when it needs to scale, and when we expect a large deluge of customers coming into our website, we have to have the backend expand. We've been doing that manually up to this point, but we're looking forward to being able to automate that.

We wanted an enterprise platform that was going to be supported. So, support from the vendor has been very important to us, and Red Hat has always provided that. When IBM took over Red Hat, we were very afraid that it was going to change our relationship with Red Hat, but it worked out very well. We've got a great sales team that has helped us, and they've always been able to get us the technical support we need when we run into an issue.

Until we got our new salesperson, I would have rated them a two out of five. Now that we've gotten our new sales team, we've gotten the right people in the right places, it's definitely a five out of five. We had a salesperson who was more focused on larger agencies, and we're a relatively small agency. So, we weren't getting the amount of focus that we needed, but that changed when our Director and our CIO engaged Red Hat's Enterprise Management. They were able to get us someone who could be more focused on smaller agencies and be a lot more helpful, and he has absolutely done that.

Positive

I was involved in the deployment or setup of RHEL to a degree, but it was mostly during our life cycle refreshes when we moved from RHEL 6 to RHEL 7 to RHEL 8. And now, we're looking at RHEL 9. 

On the backend development of the base image, I'm part of the team that puts together the base design, and then we put the steps into our repository so that we can rebuild the images easier. Right now, it's a manual process. We want to get to the point where we have all of the changes documented in a GitHub solution or something where we can make a change, push a button and have it implement those changes in there by using a script or something else. I'm mostly the one yelling to the Linux developers to get their stuff done because they have a tendency to run multiple instances while they're transitioning. They'll run an RHEL 6 box, an RHEL 7 box, and an RHEL 8 box at the same time when they have to get off of RHEL 6 and RHEL 7. So, I'm more of the management yelling at them to get this stuff done.

I would advise making sure you get a good support contract and you have a very good salesperson to work with.

In terms of RHEL's effect on our organization's management and efficiency, it can always be improved, but we probably are a three out of five on efficiency. As we move into OpenShift and get a lot more automation working, we will move slowly to the five, but that's not the fault of Red Hat. That's the fault of our organization having limited resources, and Red Hat is helping to provide the tools to get us to the next level.

Given that we started running everything on Microsoft, Red Hat is a lot more flexible in giving us the ability to span out specifically as we move into containers. It's going to give us the ability to stand up a lot more resiliency. When we're getting a heavy load, we can expand. Even currently, we have the ability to expand slightly but moving into containers will give us even more capability. We've chosen Red Hat as our platform. Red Hat has done well enough for us, and that's the platform that we're moving to with containers.

At this point, I would rate it an eight out of ten because there's always room for improvement. I don't feel that there's a perfect OS. I would even rate Windows as a seven. There's definitely room for improvement, and with Red Hat being one of the larger targets out there for hackers and people, there are always issues coming up.

We use this solution for disaster assistance. 

This solution has increased the speed of our technology. It is easy to troubleshoot using RHEL. RHEL's built-in security features and security profiles for helping to reduce risk and maintain compliance are good. It has also improved our organization's management and efficiency.

The cost of this solution could be improved. 

I have been using this solution for four years. 

This is a stable solution and we have not had any major issues when using it. 

The customer support team are very responsive and always provide the help we need. I would rate the support a nine out of ten. 

Positive

We used to use JBoss at my previous company.

I would rate this solution a nine out of ten. 

For applications, we are the OS support. We build servers and deliver applications.

RHELs overall effect on our organization's management and efficiency has been good. It's easy to support and involves no downtime. It is simple to handle, apply patches and maintain.

The most valuable feature of this solution is how easy it is to use.

When there is down time from a system admin perspective, this solution could improve how they communicate why this down time is happening. 

I have been using this solution for seven years. 

This is a stable solution. Our machines reside on vSphere and when a server goes down, we have to find out the root cause. This requires pulling information from the vSphere. 

I would rate the support for this solution an eight out of ten. 

Positive

We previously used Solaris. We moved to Red Hat because it is easier to manage and more cost-effective. It is also easier to manage patches and security using Red Hat. 

I was only involved in testing this solution during the deployment process. During testing, it was easy to make changes to configurations which also support our decision to use Red Hat. 

This is a cost-effective solution.

I would recommend this solution to others. It is easy to use, manage and handle with very little downtime. 

I would rate this solution an eight out of ten. 

Typically, we use this solution as a base to create and secure container images. Sometimes we use SELinux through RHEL and sometimes we only use RHEL. It is easier to apply STIG baselines to a RHEL system than other systems. We mainly use it for building and securing containers.

RHEL is different than any other Linux distribution folder. Folder locations are different and using this solution makes us more secure.

We are assured of added security because of the STIGs, automation and all the repositories that exist for securing Red Hat and SELinux. We have scripts that can automate the STIGing out of an RHEL machine, RHEL container or an RHEL BM.

It is also easy to troubleshoot using RHEL and follow the same process as other solutions such as Ubuntu, Debian, or Arch.

RHEL's effect on our organization's management and efficiency is noticeable because we check all the compliance boxes when we run STIG machines. It helps us because Red Hat is trusted in the governmental space. It also helps management save people's time by just having use of templated containers.

There's a lot more automation for STIGing out a Red Hat machine than there is in a Ubuntu or a Debian machine and this is one of the most valuable features. 

Since it's based off Fedora, I don't like the DNF package manager. 

I have been using this solution for six months. 

It's very stable. I've never had any breaking issues when upgrading packages or versions. 

We run this solution on a really small scale. We are a development group so we're not working on large-scale systems. We generate proof of concepts and then show that to the company for them to use so I can't really speak to how it scales.

Red Hat's tech support and customer service are really good. The Red Hat team are my favorite people to work with. They are easy to work with and genuinely care. I would rate them a nine out of ten. 

Positive

The initial setup is mostly straightforward depending on the specific setup. We build our own containers and that is more complex but there are simplex supported setups. In both scenarios, maintenance only involves a few commands and is simple. It is maintained by two security engineers. 

From an ROI perspective, this solution helps us win contracts. Contract values are negligible to what the RHEL licensing cost is. It has a really large effect on our contract deals because it gives our work and service credibility.

I would advise others to read up on the solution first. Try Fedora first before you get into Red Hat. There are some similarities and a lot of what you know about Linux transfers over. 

I would rate this solution a nine out of ten. 

Absolutely rock solid performance, security, stability and reliability, essential features for a business that needs to mission critical applications in a 24 x 7 environment.

Plethora of useful tools and services that just make getting the job done a lot less time consuming.

RedHat Enterprise Linux has been running mission critical systems in my organization now for nearly 8 years, in a 24 x 7 environment.

During this time we have never, ever had any of our servers fail to function as needed.

Red Hat Linux has given us five nines (99.999%) uptime for years.

I have been using Linux in various forms for 10+ years

Mainly just the usual issues one will encounter whilst learning the platform, working out the best way to deploy and configure the servers, other than that though, the actual deployments were very straight-forward.

None, our RHEL servers have been rock solid.

No, we have RHEL servers of varying capacities and workloads, so far it's taken everything we can throw at it.

The technical support subscription is absolutely worth while if you need to use RHEL in production, knowing you can get support if you need it is comforting.

I've lodged a few support tickets over the years and always had prompt, informative responses, I would rate their support as being excellent.

We were using an earlier version of HP UX running on PA-RISC architecture, however we became concerned about the cost of remaining on the PA-RISC HP UX platform and possible future issues at virtualization.

When setting up any Linux environment, make sure you understand how the LVM works. Other than that it was all fairly straight-forward.

It was implemented in-house.

The uptime and reliability are the main ROI's, the product is also very competitively priced RE: Licensing, so many thousands of dollars in licensing costs alone.

The ROI on 10 years of rock solid reliability is almost impossible to calculate.

In Australia, you need to go through a channel partner, shop around and find a good partner that understands the licensing model well.

We evaluated HP UX 11.23, which we had been using before hand. However HP (at the time) had not delivered an x86 port of HP UX at the time when we were going to virtualization, so we needed an alternative to HP UX as we could not move into onto VMWare.

RHEL ticked all the boxes and was support by our technology provider.

Well worth a look if you want supported enterprise Linux.

We are internet service providers in Bangladesh and resellers of this product to our customers to manage their network infrastructure. 

I think this solution is more secure than others because it's not open source. Red Hat will ensure the details when you purchase the package. Having a certification will offer value. 

We've found that there is a huge demand for it. 

Although the security features are good, I'd like to see more added in the security sphere.

I've been using this solution for just three months and still not completely familiar with it. 

The solution is stable. 

The documentation is sufficient for my needs. 

The initial setup is easy, it takes around 10-15 minutes. 

I rate this solution eight out of 10. 

We are using it for application services.

We find the Red Hat Satellite deployments very useful. It integrates well with other solutions.

It could be a bit more user-friendly. It could also be cheaper.

It is very stable. It is more stable than Windows Server.

It is scalable. The number of users would be in thousands. They include IT teams and end-users who obviously don't even know that they're using it.

I don't call them directly, but their technical support is good. 

It was straightforward. Our deployments are automated. To deploy a build internally, it only takes half an hour, but that's usually in automation. It would probably take a couple of months to put the infrastructure in place to be able to deploy it.

We have a site license on a yearly basis. Generally, we're okay with its price, but everything could be cheaper.

I would recommend this solution to others. I would advise others to do their research before deploying it and make sure that they are up to speed with the OS and what it can do. It is fairly easy to use as long as you know what you're doing.

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