Try our new research platform with insights from 80,000+ expert users
Devops engineer at a manufacturing company with 1,001-5,000 employees
Real User
Easy to use for containerization projects and has good documentation
Pros and Cons
  • "The solution's technical support is really good and responsive. I rate the technical support a ten out of ten."
  • "There are just some points in the solution's documentation where a few areas seem generic."

What is our primary use case?

I use the solution in my company to deploy our custom apps or to set up servers for DevOps operations, like running containers and those kind of tasks.

How has it helped my organization?

The benefits associated with the product for my company stem from the enterprise support the solution offers. Based on the fact that our company has technical exchange meetings with the product's staff members, I can say that I have never seen something like that happening in a hands-on engagement with our company, so that is just great. Being able to talk to the solution team about our company's issues and problems related to the tool all the time is something that really helps a lot.

What is most valuable?

I can't say anything specific about the product's valuable features, but I would say that whenever I have questions, I feel the tool's documentation is on point since I can always find anything I need easily.

What needs improvement?

There are some points in the solution's documentation where a few areas seem generic. The aforementioned area consists of the same scenario when it comes to some of the other products, so it is not just applicable for Red Hat Enterprise Linux (RHEL) alone, but also for some of the other supported products. I have never had a problem with Red Hat Enterprise Linux (RHEL), as it is really easy to use.

Buyer's Guide
Red Hat Enterprise Linux (RHEL)
April 2025
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
848,716 professionals have used our research since 2012.

For how long have I used the solution?

I have been using Red Hat Enterprise Linux (RHEL) for five years.

What do I think about the stability of the solution?

It is a stable solution.

What do I think about the scalability of the solution?

It is a scalable solution.

I believe that there are definitely some plans to increase the use of the solution in our company in the future.

I believe that there are definitely some plans to increase the use of the solution in our company in the future, especially if we start to get more customers and there is a need to ramp up automated testing since we would need more systems.

How are customer service and support?

The solution's technical support is really good and responsive. I rate the technical support a ten out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I believe that my company used to use a few products before starting off with Red Hat Enterprise Linux (RHEL), but I believe that it was before I joined the organization.

How was the initial setup?

The solution is deployed on the cloud and on-premises models.

What was our ROI?

In terms of the ROI, my experience using the solution revolves around the product's community. The fact that I can just go out and even in an ecosystem in general with tools like Fedora, CentOS, and other stuff, I can always find what I want with the help of the community where there are people with similar experiences, especially if it is not available in the documentation part. I feel Red Hat Enterprise Linux (RHEL) is community-focused, and I really appreciate that as a developer.

What other advice do I have?

Running Red Hat Enterprise Linux (RHEL) on the foundation of a hybrid cloud deployment has impacted our company's operations and I can say that it has been easy because there is not much to do between the two environments, as it is consistent, and that just reduces a bunch of headaches.

Red Hat Enterprise Linux (RHEL) has helped me centralize development. The operating system that we are developing is based on Red Hat Enterprise Linux (RHEL). In our company, we are able to use everything in the solution with the help of documentation, support shared knowledge resources, and all of that. Just using the tool to support our company's infrastructure is really great, and now we don't have to branch out and use other technologies. The tool is a platform that supports many different things.

I use Red Hat Enterprise Linux (RHEL) for containerization projects in my company as it is easy to use.

When it comes to the built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance, I can't really say anything much about it because the product is used in our company for a specific use case and we put ourselves on top, so we don't really use the aforementioned components for the policies.

In terms of how I would assess the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) for keeping our organization agile and flexible, I would say that the offering of minimal images and all such stuff really helps cut it down and make deployments faster. In our company, we are really excited to use Red Hat Enterprise Linux (RHEL) to check the containerization of our apps, so being able to do such things for our products helps keep everything moving quickly. In general, my company is excited that Red Hat Enterprise Linux (RHEL) is moving towards the area to check the containerization of apps.

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux.

In terms of the deployment model used in my company for Red Hat Enterprise Linux (RHEL), I would say that the tool is basically deployed on-premises for closed environments and in the cloud because some of our company's customers prefer to deploy the product on the cloud. Mostly, my company uses the cloud services offered by AWS, while some of our company's customers use the services from Azure.

I like Red Hat Enterprise Linux (RHEL) considering the support that it offers to our company along with good documentation.

I rate the tool a ten out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Jason Dew - PeerSpot reviewer
Senior Linux Administrator at a retailer with 501-1,000 employees
Real User
Top 20
A rock-solid, scalable OS that allows you to do things that you want
Pros and Cons
  • "Why I like it in general is that I know what it is doing. I can figure out what it is doing, and I can make it do what I want. I am not delving into arcane registry things."
  • "I am still trying to figure out the features it has. There is so much that it can do."

What is our primary use case?

We are using Red Hat Enterprise Linux for running various things. We have a lot of virtual machines. The applications that are running on it are a bunch of shell scripts for processing orders, marketing campaigns, generating reports, or running some Java applications.

How has it helped my organization?

We have the customization capability. We can easily customize it, and we can also automate and deploy it. I have a command line interface. I am a command line junkie, and I am able to use that, config files, and Ansible to be able to easily figure out what I need to do to automate things. It feels like I know what it is doing and how to make it do what I want. I do not have to weave some magical arcane hack the way I have to do in Windows.

Red Hat Enterprise Linux has enabled us to centralize development in a lot of ways. We have it hooked in through our GitHub. We are trying to combine where we are storing things and then have a standard way of how we are deploying things and have some standard configurations. With every single server, we do not have to worry about how to set this up because we are doing the same thing the same way. We can just do it across the board, and then we only have to worry about the interesting parts.

Red Hat Enterprise Linux's built-in security features are great for risk reduction, business continuity, and maintaining compliance. There are published CVEs, and there is SELinux, which I do not use and I always turn it off. Firewalls and tooling around that make it easy to use. The automation on top of that makes it easy to configure. With a push of a button, it is done.

We do not have to worry too much about portability. We are coming from Oracle Linux. We were primarily an Oracle Linux shop, and because that is based on it, it just works. We have not had any issues.

What is most valuable?

The fact that it is Linux is valuable. Why I like it in general is that I know what it is doing. I can figure out what it is doing, and I can make it do what I want. I am not delving into arcane registry things.

What needs improvement?

I am still trying to figure out the features it has. There is so much that it can do. What it does really well is that it allows you to do things.

For how long have I used the solution?

It was probably 2008 when I first started using it. The company was using Red Hat Enterprise Linux, and I was with the internal help desk supporting the Linux side.

What do I think about the stability of the solution?

Its stability is great. It is stable and rock-solid.

What do I think about the scalability of the solution?

Its scalability is also great. It does not matter if the host is beefy or not. It is just going to run on it, and it is going to handle the work. Whether you have a couple of cores or 64 cores, it is just going to do it.

How are customer service and support?

Their support is good. There is good responsiveness. They quickly get me to the person who knows the answer, but I have not used them much.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We were using Oracle Linux. We are switching because of some of the things. Oracle licensing has been a point of frustration. Their support is comparably difficult to work with, and the support documentation is a mess.

Red Hat is so much easier to navigate. It has been overall a much more pleasant experience to work with Red Hat.

How was the initial setup?

We are using it on-prem, and then our cloud is a Kubernetes cluster on AWS, so it is basically on-prem.

Our deployment model is a manual kickstart with Ansible for configuration. My experience with deployment is good. I kickstart it and then hit it with Ansible, and it is done. It is very easy.

What about the implementation team?

I did the deployment on my own.

What was our ROI?

We have not yet seen an ROI. It has not been in for long enough. There are no savings in terms of manhours because the actual day-to-day usage remains the same with Oracle Linux or Red Hat Enterprise Linux. However, getting some of the metrics with Red Hat Insights is going to be helpful as we get into a better patching cycle. I am anticipating an easier life.

We are expecting an overall decline in the costs because of the differences between the Red Hat licensing and Oracle licensing. We are expecting a net decrease in overall cost. For using it, other than the license, there is no cost.

What's my experience with pricing, setup cost, and licensing?

The setup cost is non-existent. With licensing, there was a little snafu because I misread something. There was a slight learning curve because we use virtual data center licensing. We had to understand how it all maps. We had to understand how that mapping works when the hypervisors are Red Hat or VMware. There is a slight learning curve, but it worked out. It ends up being easy.

Which other solutions did I evaluate?

I did not evaluate other options mainly because I have had experience with it before. From my prior experience, I already knew what I wanted.

What other advice do I have?

We are trying to use Red Hat Insights. I need to finish updating the playbooks to hook our host. We are in the midst of transitioning from Oracle Linux to Red Hat Enterprise Linux. I have not fully hooked everything in, but we will be using Red Hat Insights.

We just started using Red Hat Enterprise Linux for containerization projects. We have not yet seen any impact of Red Hat Enterprise Linux on containerization projects.

If a colleague is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, a lot of it would depend on their use case, what they are going to need for it, and whether they have an enterprise environment. There is a cost associated with it which can be a downside. I am an open-source lover. I do not like paying for stuff, but I get it. They need to look at the cost, and if the cost is prohibitive, they need to look at something that is compatible and as similar as possible.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. I generally do not give out a ten. There needs to be something spectacular for a ten, so that is my personal bias against the top of the scale.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Red Hat Enterprise Linux (RHEL)
April 2025
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
848,716 professionals have used our research since 2012.
Richard Geherty - PeerSpot reviewer
Associate Director SAP Infrastructure Solution at a manufacturing company with 10,001+ employees
Real User
Top 20
Helped us achieve our security standard certifications
Pros and Cons
  • "We also use Ansible. Ansible is a wonderful tool for automation. We use it to automate our patching. We use Ansible to get playbooks to take care of anything that's manual."
  • "Red Hat Enterprise Linux has affected our HA systems in a negative way. We're working through some of those issues."

How has it helped my organization?

The SAP solution subscriptions have made things a lot easier because it's a standard build. 

The solutions were premium and standard, which were not the same. They've combined those into just one standard version. Only the support hours are different. That is fantastic for us. It makes life easier.

For the standard subscriptions, in the past, updating the OS could increase your downtime. With the production ones, it did not. It got our non-production and production out of sync. Now, they've combined that all into one. It's just the support hours that are different. They're fantastic.

What is most valuable?

We use the SAP solution subscriptions only for SAP, which are great. 

We also use Ansible. Ansible is a wonderful tool for automation. We use it to automate our patching. We use Ansible to get playbooks to take care of anything that's manual.

We were able to achieve our security standard certifications.

What needs improvement?

Red Hat Enterprise Linux has affected our HA systems in a negative way. We're working through some of those issues.

Red Hat Enterprise Linux 8 came up with a new feature that's like a MOM API in our cluster. It goes out into the AWS side and it needs to be adjusted. It does a retry that causes a cluster to failover pretty quickly, so we turned that feature off. That's something that could be improved. 

For how long have I used the solution?

I have been using Red Hat Enterprise Linux for a long time. It has been at least 10 to 15 years.

What do I think about the stability of the solution?

 

How are customer service and support?

Support has been great. We get the right people for what we need.

How would you rate customer service and support?

Positive

How was the initial setup?

The patching has been good, but we scan with Qualys all the time. It comes up with thousands of EIDs all the time, but putting on the patches seems to resolve that.

We're operating right now from 7.9 to 8.6. We have to go with the supported versions. We did qualify for RHEL 9. 

Which other solutions did I evaluate?

We used Unix in the past. We did have to come up with the SAP side. It was always Unix.

What other advice do I have?

Overall, I would rate the solution an eight out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2295390 - PeerSpot reviewer
Senior Systems Engineer at a energy/utilities company with 10,001+ employees
Real User
Top 20
Secure, easy maintenance, and good support
Pros and Cons
  • "We have access to the Red Hat knowledge base. We have frequent meetings with Red Hat. Red Hat partners provided us with all the information and any kind of training."
  • "As such, there are no specific features that we are looking for. We have frequent meetings with them. We have had some issues on the application side and the OS side for which we opened cases and discussed those concerns and questions in the meetings offered by Red Hat."

What is our primary use case?

We had a lot of IBM AIX servers. We migrated a lot of them to Red Hat Enterprise Linux. We have a lot of VMs, and we have a few physical servers. Currently, we are moving all the Red Hat VMs to the cloud. There are 1,600 to 1,700 Red Hat VMs that we are currently running.

How has it helped my organization?

The main benefit is that it can be easily recovered and easily restored. It is on the VM. We can easily restore every image that we back up on the VM. If something happens, we can easily fix it. Support and maintenance are easy. The most common issues that happen with Red Hat Enterprise Linux are password restore issues. We can go and restore the passwords through the single-user mode. This feature is well-developed and good.

We are using Ansible for the most automations. We can push everything through Ansible. We are moving towards automation to make sure our system can be easily maintained, and we can recover, restore, and do the things that we want. We have 1,600 to 1,700 servers. We have Ansible Tower, and we have a few satellite servers and a lot of capsules to support Red Hat servers.

If anything is supported by Red Hat Enterprise Linux and the feature is available in Red Hat Satellite, we are able to install it on Red Hat Enterprise Linux. We are using Red Hat Satellite to install all the patches and all the packages, so if a feature is available, we can easily install it if it is supported.

Red Hat Enterprise Linux has built-in security features for simplifying risk reduction and maintaining compliance. We are working with most of the security environments. Security is our main concern. We have zero tolerance when it comes to security. We are able to apply security rules and regulations within the Red Hat environment.

What is most valuable?

We are using Red Hat Enterprise Linux 7, and we normally look at how it can easily support the system. With Red Hat Enterprise Linux 7, we have a high-security system. We have a lot of features there. That is the main thing, but currently, we are moving from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. 

Red Hat Enterprise Linux Leapp and Red Hat Insights have been useful. RHEL Web Console is also helpful.

We have access to the Red Hat knowledge base. We have frequent meetings with Red Hat. Red Hat partners provided us with all the information and any kind of training.

What needs improvement?

We are using the features that are available with Red Hat Enterprise Linux and Ansible. As such, there are no specific features that we are looking for. 

We have frequent meetings with them. We have had some issues on the application side and the OS side for which we opened cases and discussed those concerns and questions in the meetings offered by Red Hat.

For how long have I used the solution?

I have been using Red Hat Enterprise Linux for almost 10 years.

What do I think about the scalability of the solution?

Upgrades and migrations are ongoing processes to stay current. We are a big company. We always have migration going on. We always have the build process. Red Hat's presence keeps increasing in our environment. We are going to have about 2,500 Red Hat Enterprise Linux VMs in the next year.

How are customer service and support?

If there are any concerns, we have a meeting with Red Hat, and they provide the required support. When we have any concerns or questions, they answer them. It is easy. I would rate their support a nine out of ten.

How would you rate customer service and support?

Positive

What was our ROI?

We have probably seen an ROI. Red Hat is getting better every day. 

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Dan Shaver - PeerSpot reviewer
Sr. Automation Architect at a healthcare company
Real User
Integrated approach across Red Hat products simplifies our operations greatly
Pros and Cons
  • "The AppStream feature provides access to up-to-date languages and tools in a way that interoperates with third-party source code. It makes it a lot easier to maintain that, as well as keeps our developers happy by having newer versions of development languages available."
  • "I don't see anything that needs improvement with RHEL itself, but there is room for improvement of the support infrastructure for it. The management and updates to Satellite, which is the support update, have been cumbersome at best, including releases and changes to a release. Communication on how that will work going forward has not been great."

What is our primary use case?

We have various use cases with about 12,000 instances across four data centers and three different clouds. In general, it's for the adoption of and standardization with other vendors, so that other vendors' software is known to work. We're doing lift-and-shift of existing hardware infrastructure that is onsite into the Cloud.

How has it helped my organization?

It enables us to deploy current applications and emerging workloads across bare-metal, virtualized, hybrid cloud, and multi-cloud environments. Typically, there haven't been a lot of issues in terms of the reliability of applications across these environments.

The AppStream feature provides access to up-to-date languages and tools in a way that interoperates with third-party source code. It makes it a lot easier to maintain that, as well as keeps our developers happy by having newer versions of development languages available.

In addition, as we roll into version 8 and, upcoming, 9, it makes the migrating of older applications into these environments easier.

We also use Red Hat JBoss Fuse and Red Hat Insights, the latter being a part of RHEL. Red Hat products integrate greatly with the OS itself. We're pretty pleased with that. The integrated approach simplifies our operations to a great extent.

What is most valuable?

The most valuable features are the

  • flexibility of the OS itself
  • reliability
  • support model.

Also, the two versions we use are fairly standard. Most of our applications work with versions 6, 7, and 8 meaning migration and maintainability are pretty good.

In addition, we run multiple versions of the same application on a specific operating system, between different instances. RHEL is great at managing and maintaining those different versions. It's so much easier, and it does it without destroying the operating system itself.

What needs improvement?

I don't see anything that needs improvement with RHEL itself, but there is room for improvement of the support infrastructure for it. The management and updates to Satellite, which is the support update, have been cumbersome at best, including releases and changes to a release. Communication on how that will work going forward has not been great.

For how long have I used the solution?

I've been using Red Hat Enterprise Linux (RHEL) for about 20 years.

What do I think about the stability of the solution?

We chose Red Hat for the stability.

What do I think about the scalability of the solution?

The scalability is really good too. In terms of increasing our usage, I can only foresee it becoming greater in the environment.

How are customer service and support?

Sometimes the tech support is hit and miss, but most of the time they're really responsive and knowledgeable. If the first-line tech doesn't know something, they will escalate quickly.

If I were to compare the tech support from Dell, HP, and Red Hat, Red Hat is probably our best support structure.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I've been with my current company for 10 years. We've used other UNIX platforms, like Solaris and AIX, but those are for different use cases. The company I started at, which was bought, had seven different implementations and I standardized them on RHEL, before the acquisition.

We switched to RHEL because those seven different operating systems were supporting a single team and none of them had a great management infrastructure, or they were just plain open source with no support. And getting to a single, supported, managed environment was the goal.

Red Hat's open-source approach was a factor when we chose the solution. I'm a big fan of the entire open-source consortium. The more people there are who can look at the code, validate it, and make sure it works as it moves upstream into the solidified package that Red Hat supports, the better. It gives you more visibility, more transparency, and you can customize it more. Whereas with closed code, you have no idea what's going on in the background.

How was the initial setup?

The initial setup of the solution is relatively simple. It's pretty much click, click, click, done. And the single subscription and install repository for all types of systems make the purchasing and installation processes easier.

Depending on the platform, deployment of a single RHEL instance could take anywhere from  five to 30 minutes. Bare metal is going to take longer than deploying the cloud.

What's my experience with pricing, setup cost, and licensing?

The licensing is a subscription model and the only product whose model I don't like is Ansible. At $100 per server, with 12,000 servers, it adds up.

What other advice do I have?

My biggest advice would be to read the documentation and reach out to Red Hat, or even just search the internet, so that you understand what you're getting into and what you're implementing.

I can't think of very much that needs to be improved with RHEL. The model that they have for maintaining patching, and their cadence on Zero-day attacks is fantastic, and their support is really good. I don't see any issues.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer1486413 - PeerSpot reviewer
Principal Analyst - AIX and Linux at a transportation company with 10,001+ employees
Real User
The integrated solution approach reduces our TCO tremendously because we are able to focus on innovation instead of operations
Pros and Cons
  • "The integrated solution approach reduces our TCO tremendously because we are able to focus on innovation instead of operations."
  • "Linux overall needs improvement. They cannot go much beyond what Linus Torvalds's kernel implementation can do. I come from AIX, and there were very cool things in AIX that I am missing dearly, e.g., being able to support not only adding, but also reducing memory and number of processors. That is not supported on Linux right now, and it is the same for the mainstream file systems supported by Red Hat. There is no way of reducing a file system or logical volume. Whereas, in AIX, it was a shoo-in. These are the little things where we can say, "Ah, we are missing AIX for that.""

What is our primary use case?

It started mostly with websites and open source environments overall for development. Now, we are moving into business applications as we are migrating our ERP, which is a cp -r tree, to Linux. We are also migrating the database of SAP to SAP HANA on Red Hat Enterprise Linux. 

We use RHEL versions 7 and 8. There is a bit of version 6 still lying around, but we are working on eradicating that. It is mostly RHEL Standard subscriptions, but there are a few Premium subscriptions, depending on how critical the applications are.

How has it helped my organization?

It has fulfilled all the promises or goals of different projects, not just because our internal team is strong, but also because our external partner is strong.

What is most valuable?

Satellite is an optional system which provides for extensive deployment and patch management. That is quite valuable.

We use Red Hat Enterprise Linux's tracing and monitoring tools. You don't leave them on all the time, as far as tracing is concerned. When you are sick and go to the doctor, that is when you use it, e.g., when an application is sick or things are really unexplainable. It gives you a good wealth of information. In regards to monitoring, we are using them to a point. We are using Insights and Insight Sender as well as the Performance Co-Pilot (PCP), which is more something we look at once in a while. 

Other Red Hat products integrate with Red Hat Enterprise Linux very well. In fact, they integrate with pretty much everything around the universe. We are doing API calls without even knowing what an API is, i.e., towards VMware vCenter as well as Centreon. There are certain individuals who use it for free without subscription and support for Ansible in our Telco group with great success.

What needs improvement?

Linux overall needs improvement. They cannot go much beyond what Linus Torvalds's kernel implementation can do. I come from AIX, and there were very cool things in AIX that I am missing dearly, e.g., being able to support not only adding, but also reducing memory and number of processors. That is not supported on Linux right now, and it is the same for the mainstream file systems supported by Red Hat. There is no way of reducing a file system or logical volume. Whereas, in AIX, it was a shoo-in. These are the little things where we can say, "Ah, we are missing AIX for that."

We are not loving our servers anymore. If we need them, we create them. When we don't need them, we delete them. That is what they are. They are just commodities. They are just a transient product.

For how long have I used the solution?

I have been using it for nine years, since 2012.

What do I think about the stability of the solution?

The stability has been very good. However, there is a learning curve. We were running huge in-memory databases, about 2.5 terabytes of RAM, which is SAP HANA. Then, we were getting really weird problems, so we asked the app guys 20,000 times to open a ticket because we were seeing all kinds of weird timeouts and things like that on the OS side. We were saying, "It's the app. It takes forever." Finally, they said, "Oh yeah, we use a back-level thing that is buggy and creates a problem." It took us six months and four people to get that from the app guys. We were ready to kill them. That was not good. Whatever you put on Linux, make sure that you have somebody supporting it who is not dumb, or on any platform for that matter.

What do I think about the scalability of the solution?

The scalability is six terabytes. That is what we're doing. We are printing HANA servers on that scale, which are more in the 2.5 terabyte range. However, we had to create one for the migration initiative on the VMware, which was six terabytes with 112 cores. It worked, and that was it. It also works with bare-metal, but you have to be aware there are challenges in regards to drivers and things.

How are customer service and technical support?

RHEL provides features that help our speed deployment. For example, for SAP HANA, they have full-fledged support for failover clustering using Red Hat HA, which is a solution to create a vintage approach of failover clustering. They do provide extensive support for value-adds for ERP solutions.

They also provide value left, right, and center. Whenever we have a problem, they are always there. We have used both their professional services as well as their Technical Account Manager (TAM) services, which is a premium service to manage the different challenges that we have had within our business. They have always come through for us, and it is a great organization overall.

Their support is wonderful. They will go beyond what is supposed to be supported. For example, we had a ransomware attack. They went 20 times above what we were expecting of them, using software provided by them on a pro bono basis, meaning take it and do whatever you want with it, but it was not ours. That was a nice surprise. So, whenever we have needed them, they did not come with a bill. They came with support, listening, and solutions. That is what we expect of a partner, and that is what they are: a partner.

Which solution did I use previously and why did I switch?

I, for one, was managing AIX, which is a legacy Unix, as my core competency. I still do because we haven't completed the migration. 

RHEL is a value-add right now. As we are migrating more payloads to containers, we are putting less Linux forethought into these container-hosting servers. You just shove your containers on top of them with your orchestrations. This may reduce our need to manage RHEL like a bunch of containers. That changes the business. 

We were paying for premium SUSE support for an initial pilot of SAP HANA on the IBM POWER platform. We were stuck between an IBM organization telling us, "Go to SUSE for your support," and the SUSE organization saying, "Go to IBM for your support." So, we told them both to go away. 

We are so glad that we haven't mixed the Red Hat and IBM more, because SUSE and IBM don't mix, and we were mixing them. That was prior to the merger with Red Hat. In regards to IBM's ownership of Red Hat, we are a bit wary, but we think that IBM will have the wisdom not to mess it up, but we will see. There is a risk.

How was the initial setup?

The initial setup is as straightforward as it can get for anyone who knows what they are talking about. It does require technical knowledge, because that's what it is: a technical solution. It is not something that I would give to my mother. Contrary to other people's perception of, "My mom had a problem with her Windows. Oh, put her on Linux." Yeah, no thanks. Give her a tablet, please. Tablets are pretty cool for non-techies, and even for techies to a certain extent. 

For the migration from AIX, Ansible has been our savior. You do need somebody who knows Ansible, then it is more about printing your servers. So, you press on the print button, then you give it to the apps guys, but you do have to know what you are trying to aim for so the guy who is creating the Ansible Playbook codes exactly what is required with the right variables. After that, it is just a question of shoving that into production. It is pretty wonderful.

What was our ROI?

We do get a return on investment with this solution in regards to a comparative cost of ownership of going with the niche solution of IBM AIX systems and hardware. There is a tremendous difference in cost. It is about tenfold.

The integrated solution approach reduces our TCO tremendously because we are able to focus on innovation instead of operations.

What's my experience with pricing, setup cost, and licensing?

RHEL is a great place to go. They have a great thing that is not very well-known, which is called the Learning Subscription, which is a one-year all-you-can-drink access to all of their online self-paced courses as well as their certifications. While it is a premium to have the certifications as well, it is very cool to have that because you end up as a Red Hat certified engineer in a hurry. It is good to have the training because then you are fully versed in doing the Red Hat approach to the equation, which is a no-nonsense approach.

Because it is a subscription, you can go elastic. This means you can buy a year, then you can skip a year. It is not like when you buy something. You don't buy it. You are paying for the support on something, and if you don't pay for the support on something, there is no shame because there are no upfront costs. It changes the equation. However, we have such growth right now on the Linux platform that we are reusing and scavenging these licenses. From a business standpoint, not having to buy, but just having to pay for maintenance, changes a lot of the calculations.

Which other solutions did I evaluate?

We tried SUSE on the IBM POWER platform, and it was a very lonely place to be in. That was for SAP HANA migration. We are glad that we decided to be mainstream with leveraging what we already had at Red Hat Linux (over a few dead bodies now). We also leveraged the Intel x86 platform, which is very mainstream. 

We are not using the Red Hat Virtualization product. We are using VMware just so we can conform to the corporate portfolio.

Our RHEL alerting and operation dashboard is not our route one right now. We have been using Centreon, which is derived from the Nagios approach, for about seven years.

With AIX, we couldn't get a single software open source to run. It was like a write-off, except for reducing a file system or logical volume in Linux.

What other advice do I have?

We are a bunch of techies here. RHEL is not managed by end users. We don't really mind the GUIs, because the first thing that we do is stop using them. We are using Ansible, which is now part of RHEL, and that can automate the living heck out of everything. For now, we are not using the Power approach, but we may in the future. We are doing a business case for that, as it would be an easy sell for some communities and the use cases are not techie-to-techies.

There is a cloud, but we have very little infrastructure as a service in the cloud right now. 

It delivers to the targeted audiences. Could Red Hat Enterprise Linux be used in all types of other scenarios? Most likely. They have an embedded version for microcontrollers, i.e., things that you put into your jewelry or light switches. However, this is not what they're aiming for.

I would rate RHEL as a nine and a half (out of 10), but I will round that up to 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2620827 - PeerSpot reviewer
Systems Engineer at a tech vendor with 501-1,000 employees
MSP
Great performance with flexibility and security
Pros and Cons
  • "One of the most beneficial aspects of Red Hat Enterprise Linux is its performance, combined with the flexibility to install a wide range of available packages online."
  • "I recommend Red Hat Enterprise Linux to others, especially larger companies."
  • "Red Hat could enhance its user experience by incorporating built-in automation tools, eliminating users needing to install, set up, or configure external applications."
  • "Red Hat could enhance its user experience by incorporating built-in automation tools, eliminating users needing to install, set up, or configure external applications."

What is our primary use case?

We use Red Hat Enterprise Linux to host databases and Citrix desktops on our servers. This allows us to offer virtual desktops as a service to other companies.

We implemented Red Hat Enterprise Linux due to its widespread industry use and extensive resources for assistance. The platform's popularity ensures a seamless experience when installing applications and creating packages, as it's utilized by many and offers ample support.

How has it helped my organization?

Red Hat Enterprise Linux offers excellent documentation and resources, including those provided by Red Hat and the wider community. While I don't rely solely on Red Hat's websites for instructions or troubleshooting, experienced users like myself generally find ample support and clear guidance to resolve any issues.

Red Hat Enterprise Linux's widespread use in cloud and on-premises servers is its most significant benefit, providing access to various online resources and support. Furthermore, Red Hat's comprehensive collection of packages and built-in applications simplifies development, making it an easy and obvious choice for many users.

Our workflows have been seamless with our hybrid environment.

Before Red Hat support, we used CentOS without expert assistance. This meant our OS team spent significantly more time troubleshooting issues and installation failures. Implementing Red Hat has resulted in increased efficiency.

What is most valuable?

One of the most beneficial aspects of Red Hat Enterprise Linux is its performance, combined with the flexibility to install a wide range of available packages online.

What needs improvement?

Red Hat could enhance its user experience by incorporating built-in automation tools, eliminating users needing to install, set up, or configure external applications. By providing pre-installed, native automation tools within the operating system, Red Hat would streamline processes and improve user efficiency.

For how long have I used the solution?

I have been using Red Hat Enterprise Linux for five years.

What do I think about the stability of the solution?

Red Hat Enterprise Linux is stable.

What do I think about the scalability of the solution?

Red Hat Enterprise Linux is scalable.

Which solution did I use previously and why did I switch?

Our organization transitioned from CentOS to Red Hat Enterprise Linux due to the enhanced security and support offered by Red Hat. The availability of online support for our OS team, combined with improved performance and rigorously tested patches, were key factors in our decision.

How was the initial setup?

Upgrading Red Hat Enterprise Linux is a straightforward process that involves running a single command to update and patch all packages. However, syncing the repository to the new one is a manual step. Despite this, I haven't encountered any issues. To perform the upgrade, I synchronize our Red Hat repository with Red Hat Satellite, execute the upgrade command, and verify the package versions to confirm successful updates.

The required personnel for server upgrades depends primarily on the number of servers and the testing duration. Potential connection issues may also influence staffing needs. Based on previous patching experience, approximately five people are needed for the off-hours patching process, typically conducted between two AM and six AM.

What about the implementation team?

The upgrades were done in-house. 

What other advice do I have?

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

Our organization has approximately 3,000 users and operates five data centers in the United States that utilize Red Hat Enterprise Linux.

Red Hat Enterprise Linux maintenance is straightforward but necessary due to occasional unexpected spikes in CPU usage and storage capacity reaching its limit. This presents a challenge because storage and CPU load management are not fully automated, requiring manual intervention to address these issues effectively.

I recommend Red Hat Enterprise Linux to others, especially larger companies. Purchasing Red Hat support, while an added cost, saves valuable time and resources compared to extensive independent research.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Vincent Ceulemans - PeerSpot reviewer
Database administrator at a tech services company with 1-10 employees
Real User
Top 20
It's a reliable distribution for installing and working with open-source databases
Pros and Cons
  • "Red Hat Enterprise Linux 's most valuable feature is its reliability. I don't have to worry about the operating system. It's one of the easiest operating systems for databases, and the integration is excellent. It gives me peace of mind because I can focus on my database work without worrying about my OS. I want to ensure I have applications that run on the OS without searching for temporary fixes or workarounds."
  • "I haven't identified anything that needs to be proved, but I hope RHEL maintains its reliability."

What is our primary use case?

I am a database administrator, and we mostly use Red Hat Enterprise Linux to manage databases. Primarily, we use it for Postgres, as it works best on Red Hat Enterprise Linux (RHEL). It's easiest to set up and has the best documentation.

I'm aware of one customer that is thinking about it. But I'm not sure what specific projects they want to use it for. I think there's one customer who is interested in it and is trying to find a solution that might benefit from it. 

How has it helped my organization?

Red Hat Enterprise Linux (RHEL) contributes significantly to our business continuity and compliance efforts. The best example is uptime. Many critical businesses need to be operational twenty-four hours a day. If a database goes down for some reason, it is seldom Red Hat Enterprise Linux that is the issue. This provides peace of mind.

It has helped us centralize development because Red Hat Enterprise Linux has many tools that aren't accessible to our Windows customers. 

What is most valuable?

Red Hat Enterprise Linux's most valuable feature is its reliability. I don't have to worry about the operating system. It's one of the easiest operating systems for databases, and the integration is excellent. It gives me peace of mind because I can focus on my database work without worrying about my OS. I want to ensure I have applications that run on the OS without searching for temporary fixes or workarounds. 

It has some of the best out-of-the-box security features of any Linux distributor. Red Hat Enterprise Linux has more built-in security features than most standard flavors, or it has implemented them better. 

What needs improvement?

I haven't identified anything that needs to be proved, but I hope Red Hat Enterprise Linux maintains its reliability.

For how long have I used the solution?

I have used Red Hat Enterprise Linux for the past five years.

What do I think about the stability of the solution?

Red Hat Enterprise Linux has been perfect. My Windows customers experience a lot more downtime and bugs. Our critical businesses need to be up 24/7. It's rarely its fault if a database goes down. I would estimate that there's about 10 percent less downtime compared to Windows customers. 

What do I think about the scalability of the solution?

I haven't been involved in any real project that necessitates scaling as our needs change.

How are customer service and support?

The support is excellent compared to other solutions like Oracle. They're knowledgeable and easier to work with. We have a nice, transparent working relationship. 

How would you rate customer service and support?

Positive

What was our ROI?

The biggest ROI is from Red Hat Enterprise Linux's reliability. If I run databases on Windows, I have to find other tools or workarounds. It's a big hassle. Red Hat Enterprise Linux lowers the total cost of ownership for my customers because I bill fewer hours than I would in a Windows environment. Open-source databases run better on Red Hat Enterprise Linux than on Windows. Most things I need are built-in or can be downloaded from the repo. 

Which other solutions did I evaluate?

Ubuntu is commonly used, and there's a decent amount of documentation for databases, but it can't compare to Red Hat Enterprise Linux. Setting up Postgres or any open-source database on Red Hat Enterprise Linux is way easier. The documentation is more extensive. It's also easier support because many customers have a subscription with Red Hat.

What other advice do I have?

I rate Red Hat Enterprise Linux nine out of 10.

My advice would be to focus on reliability and ease of integration when choosing a Linux OS. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2025
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.