Try our new research platform with insights from 80,000+ expert users
reviewer2398773 - PeerSpot reviewer
Team lead cloud infrastructure at a renewables & environment company with 1,001-5,000 employees
Real User
Offers security and is useful in the area of automation
Pros and Cons
  • "I would like to say Red Hat Enterprise Linux (RHEL) is much more efficient than Windows, and my employees love the Linux command line."

    What is our primary use case?

    My company currently uses Red Hat Virtualization to host all our virtual machines, and then we install Red Hat Enterprise Linux (RHEL) for almost everything we do. My company only has 30 or 40 Windows Servers, while we have over 2,000 Red Hat Enterprise Linux (RHEL) machines. In my company, we use Red Hat Enterprise Linux (RHEL) for everything from provisioning systems to Speedtest Servers to whatever we need in the company.

    How has it helped my organization?

    I would like to say Red Hat Enterprise Linux (RHEL) is much more efficient than Windows, and my employees love the Linux command line. All in all, Linux is what my company has been using since the beginning, so it is imprinted in everyone working in the technology section of our organization.

    What is most valuable?

    All Red Hat Enterprise Linux (RHEL) features have been valuable.

    Red Hat Enterprise Linux (RHEL) is a Linux system, and in our company, we could probably use different Linux systems. My company mainly uses Red Hat Enterprise Linux (RHEL) because of the kind of security and the patching delivered, including the backporting of patches, instead of actually having to do version upgrades. The product's valuable features include stability and security.

    In my company, the solution has helped centralize development in most parts.

    The use of the product for containerization projects is an area that my company has been dealing with lately. In our company, we are installing a lot of OpenShift clusters now and moving that way, but if they run on Red Hat Enterprise Linux (RHEL) or bare-bones or bare-metal OpenShift, the shift needs to be made.

    In terms of the impact my company has experienced after making Red Hat Enterprise Linux (RHEL) a part of our containerization projects, I would say that a different team is handling the development parts for our company. Our company would be happy if the products we use were Red Hat Enterprise Linux (RHEL) or OpenShift. My company is very interested in Red Hat Enterprise Linux (RHEL), even if it will take many years for us to be completely over containers.

    As per my assessment of the tool's built-in security features when it comes to areas like risk reduction, business continuity, and compliance, all of the aforementioned functionalities are the main reasons my company stayed with Red Hat Enterprise Linux (RHEL). My company prefers Red Hat Enterprise Linux (RHEL) because of its stability, patch management, and other features that make us feel more secure.

    In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that my company has done a lot of automation, which helps us keep everything as flexible as we want. One of my team members told me that the product is super when it comes to everything related to automation. The tool allows you to be kind of flexible.

    At the moment, I don't use Red Hat Insights even though we have looked at it in our company. In our company, we have put up Red Hat Insights, and we have it on the machines, but it's not that deep in use yet. I believe that Red Hat Insights will be more and more important since the security team wants to use it to get a better overview.

    If I have to speak to a colleague who is looking at open-source cloud-based operating systems for Linux, I would say that everyone needs to make a choice when it is not something concerning our company since we are standardized with Red Hat Enterprise Linux (RHEL) or Red Hat products in our company. My colleagues will have to use Red Hat products if they work in my company.

    Speaking of whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape, I would say that we have been using virtualization in Red Hat Enterprise Linux (RHEL) for many years, and it has been a very good and cost-effective tool for our company. The product may reach the end of the life phase soon, so we have to migrate to some other solution, though we know that the prices may go up whenever we do it. Up until now, the tool has been very good.

    My company deploys Red Hat Enterprise Linux (RHEL) from Red Hat Satellite. Red Hat CloudForm is a self-service portal we use in our company but now it is an IBM product. I don't remember the name as it is long and boring. Red Hat CloudForm is a self-service portal that is connected to Red Hat Satellite to provision the machines.

    What needs improvement?

    My manager role is the reason why I am not that deep into the technical part anymore. In my company, the IT team is happy with Red Hat Enterprise Linux (RHEL) since they don't have to use Windows.

    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?

    Personally, I started using Red Hat Enterprise Linux (RHEL) around ten years ago. In my company, I have been using the tool for twenty 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?

    The solution scales up perfectly fine, especially since everything is automated since we have a very small team of 10 people in our company managing everything, including 2,000 servers.

    How are customer service and support?

    The product's support team was good whenever my company needed support services. Our company also uses some professional services from time to time, especially since Red Hat has a deep knowledge of the tool. If our company faces a problem, we have a very good connection with the tool's team in Norway, and they always help us, even if it's time-critical. The tool's support team manages to get us the consultants our company needs. 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?

    My company has been using Red Hat Enterprise Linux (RHEL) from the beginning.

    How was the initial setup?

    When I started in the company almost ten years ago, deployment of Red Hat Enterprise Linux (RHEL) was done with an ISO image, which you mount it up, and you put in the IP addresses and do a lot of manual things. It is a different story today since you just enter how many courses you want and how much disk you want, and the deployment is done in two minutes.

    The solution is deployed on an on-premises model, and we don't have a lot in the cloud at the moment in our company. As an ISP, the services we deliver are kind of time-sensitive or latency-sensitive, so as long as we have a data center, it doesn't make that much sense to put stuff in the cloud just because it is the best.

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

    In terms of the prices and license of the product, I feel the solution has been good so far, especially since it has been quite easy to understand compared to a lot of other tools. I have been working with IBM and other vendors, where I have seen how other tools might have a bit more difficult pricing or licensing models compared to Red Hat Enterprise Linux (RHEL). In terms of pricing, Red Hat Enterprise Linux (RHEL) has been quite okay in general.

    Which other solutions did I evaluate?

    Red Hat Enterprise Linux (RHEL) was present ten years ago before I joined my current company, so I don't know if any other products were evaluated against it before my joining.

    What other advice do I have?

    We have a few applications that we have started developing in the cloud now managed by a different team, but I don't think they use Red Hat Enterprise Linux (RHEL) specifically.

    I rate the tool a ten out of ten.

    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
    IT Manager at Sangicor Bank
    Real User
    The portability of applications and containers will be good for keeping our organization agile
    Pros and Cons
    • "Its stability is most valuable. Its administrative aspect is also good. It is relatively easy to administer."
    • "Currently, there is a gap in the file system management. I want to be able to expand the file system in a simpler way and have the application or the database use that expansion without any downtime."

    What is our primary use case?

    We first used it for application installation to run applications on Windows. We had it running on Windows. We then upgraded it. It was still on the IBM platform, but it was still x86. We have now updated it, and it is now running on IBM Linux Z.

    We use it for Internet banking, core banking applications, and other peripheral applications.

    How has it helped my organization?

    It has helped with consolidation. When we first started to do clusters, we were using Oracle cluster and Red Hat cluster. The Red Hat cluster was more stable than the Oracle cluster, so we had to uninstall the Oracle cluster and just use the Red Hat feature to have floating IP addresses between two cluster nodes. Having it in a cluster was the single most useful application of Red Hat in the environment.

    We use Red Hat Insights, Ansible, and Satellite. Red Hat Insights is helping us big time. A year ago, I was looking at bolstering my team to about five or so administrators. With Red Hat Insights and other tools, I am satisfied with just two administrators. They are there just to manage the system and not necessarily go down into the trenches.

    It seems that Red Hat Insights provides vulnerability alerts and targeted guidance, but my team would know that better. I manage a team that does that.

    What is most valuable?

    Its stability is most valuable. Its administrative aspect is also good. It is relatively easy to administer. I am familiar with AIX. AIX is super easy. I did not have to struggle much to adapt to Red Hat.

    What needs improvement?

    They can make the extended file system dynamic. Currently, we have to bring down the server to add an Hdisk. We cannot extend the database on the fly. We have to have downtime. We want to ensure that we make the blackout periods as minimal as possible. Currently, there is a gap in the file system management. I want to be able to expand the file system in a simpler way and have the application or the database use that expansion without any downtime.

    For how long have I used the solution?

    I have been using Red Hat Enterprise Linux since 2004. It has been 20 years.

    What do I think about the stability of the solution?

    There is no problem with stability. It is stable. We have a couple of Red Hat Enterprise Linux 4 still running. We also have Red Hat Enterprise Linux 6 systems. The hardware is functional, but the application was retired. We cannot get an update for it. It has been running since 2008.

    What do I think about the scalability of the solution?

    Its scalability is fine. There is no problem with scalability. We can do it in real-time. Now with containers and other things, we can scale on the fly without much downtime. We can build a small system and scale it. We can start at a much lower level than several others.

    How are customer service and support?

    It has improved tremendously. I remember when it used to be centralized. I have been to North Carolina to get training, but now they can come to us for the training. The whole support architecture has improved. We can reserve hours for calls when the need arises. If we do not use it, it is reallocated the next month to some other project. They are doing well. I am impressed.

    How would you rate customer service and support?

    Positive

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

    We were using and still are using AIX, but most of the applications have been imported, so we are between AIX and Red Hat. We are also using Windows, but Red Hat has stood out. It is not yet there with AIX, but it is getting there.

    We were using Ubuntu and a few other flavors, but they were not organized. They were still too open. The support and the training for Red Hat Enterprise Linux was spot on. It was exemplary. We could find support easily.

    How was the initial setup?

    We have them in clusters, and we also have standalone ones. We have DR where we synchronize with DR. We synchronize at the file system level with DR, which eliminates some of the application limitations.

    We are using it on-prem, but we have applications to be upgraded in another 18 months, which would be a hybrid cloud.

    Its installation the first time was overwhelming. Once you get used to it, the team settles down, and you have knowledgeable people, it is a breeze.

    What about the implementation team?

    We have an integrator, a reseller, and a consultant. Somebody would come in and help us connect the dots. I guess that is their reseller, and then the integrator helps us properly connect the dots.

    Pedro is our accounts manager. He probably comes from Puerto Rico, and then there is Lincoln Walters from Jamaica. Together, they help us identify the resources we need for the things that we want to do.

    What was our ROI?

    The biggest ROI is in terms of the reduction of human resources required to manage and maintain it. The administrative duties have been vastly reduced. You can even have resources from Red Hat. They have something where you can block certain hours a month and you can just use them as needed. If you do not use them entirely, you can reallocate them. That means you can reallocate unused resources. There are savings on investment.

    We are still learning about it, but our TCO has reduced because we do not have to have as much manpower, hardware, and processes to manage and operate.

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

    Licensing is the most attractive part of it. With Red Hat Insights and Ansible, we now know that it was done with the intention of simplifying the licensing so that you get the support for what you have and not necessarily what you want to have.

    What other advice do I have?

    Red Hat Enterprise Linux has not helped us to centralize development. We have not capitalized on that as yet. I am here at the Red Hat Summit to learn about Kubernetes and containers. It is all new to me, and at this point, I do not know from where to start. I am getting exposed to so many things, but I still need to understand from where to start. I need to know the foundations. In about 18 months, we will be going to containers. We have people developing Dockers, Kubernetes, and other things, but we need to find a way to integrate them. We will have containers running on OpenShift, but we need to know how to secure, store, and manage those containers.

    I have participated in a few presentations, and I see that there are prescribed ways to ensure that you maintain compliance by upgrading. In one of the presentations, one of the presenters said to not expand or scale too quickly because some of the applications get left behind. That is something that I am taking away.

    The portability of applications and containers built on Red Hat Enterprise Linux will be good for keeping our organization agile. It is flexible. They say, "Build once and run anywhere." That is the buzzword for me.

    To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that Linux is for beginners, whereas Red Hat Enterprise Linux comes with the bells and whistles and the stability for business. It is an enterprise-grade software.

    Overall, I would rate Red Hat Enterprise Linux a nine out of ten. There is innovation and adaptability. Ten years ago, it was unheard of. It has grown, and it has been growing tremendously.

    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.
    Georgios Atsigkioz - PeerSpot reviewer
    Senior Consultant at Atea AS
    Consultant
    Top 10
    A good and standardized product offering stability while relying on automation, making it cost-efficient
    Pros and Cons
    • "I have seen a return on investment, especially considering the time taken to resolve the problem where we bought some support from Red Hat."
    • "New products need better documentation. The websites also have a single sign-on to get you from one side to the other. As a partner, I had a problem finding out how I needed to connect and to which side of the solution."

    What is our primary use case?

    Internally, we use Red Hat Enterprise Linux for services and for applications that we run, especially Linux based-applications. We also have SAP solutions, which we sell to the customers as a total solution with Red Hat, SAP HANA, and also for our own cloud-based SAP HANA, which is under Red Hat's operating system.

    What is most valuable?

    Red Hat Insights is quite an interesting and valuable feature. Lately, we used the malware scan feature. The Cockpit feature and web interface were quite helpful. We have also begun with OpenSCAP, which used is to harden the operating system's security features.

    What needs improvement?

    The first area for improvement is documentation, and I consider it since I have been working in IT for more than twenty-five years. For twenty years, I have been working with open source, and I see that the documentation is lacking, so it needs to do more work on its documentation part. Most open source and upstreams from Red Hat products work from the open source solution and have better documentation than in the actual Red Hat products.

    New products need better documentation. The websites also have a single sign-on to get you from one side to the other. As a partner, I had a problem finding out how I needed to connect and to which side of the solution. I consider myself an expert user of the internet and websites, but going from one side to the other, was quite problematic.

    For how long have I used the solution?

    I have been using Red Hat Enterprise Linux on the cloud for four to five years at least. My company has a partnership with Red Hat, and so we have our own licensing for the product. We have customers whom we manage, and they purchased the licenses on the go from the cloud provider. We just sold them the managed services. But mostly through us, we should be selling the licenses.

    What do I think about the stability of the solution?

    It's a very stable product, and that is actually the reason we are forcing or pushing customers to go with Red Hat Enterprise Linux.

    What do I think about the scalability of the solution?

    The solution is scalable.

    How are customer service and support?

    I rate the support a seven out of ten. The support is knowledgeable but slow if we have to get answers.

    How would you rate customer service and support?

    Neutral

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

    We use Red Hat Satellite for managed services for our customers. And, of course, we use a product of Red Hat Enterprise Linux for servers. We started with OpenShift in the lab at the beginning, but now I'm beginning to produce it for our own services. So, now I can offer these to the customers.

    One of the discussions in my company at the beginning of this year was to see if we could test our services on-premises for the virtualization, specifically for the KVM virtualization. But since it was not approved, we'll have to see the next step.

    I have worked with other open source distributors. I have worked with SCO-Linux and Unix, which is the base of Linux. I didn't personally make the decision to switch. The company decided to switch since we are partners, and we are focusing on putting in the best efforts in terms of the partnership and customers we have with Red Hat.

    How was the initial setup?

    The solution is deployed on both on-premises and the cloud. We have customers on the cloud server platform where we run their network, and we manage through Satellite. We also have it on-premises.

    I was involved in the deployment of the solution. We created some automation, so the setup phase is straightforward. We use templates for all of those, but to manage the templates, and what it will include, we use external tools to make it easier for the deployment automation.

    Regarding deployment time, it can be done in seconds. It also depends on what application we are speaking about since for an OS or more difficult solution, like Red Hat Satellite, you need more time.

    What was our ROI?

    I have seen a return on investment, especially considering the time taken to resolve the problem where we bought some support from Red Hat.

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

    Regarding the prices, the new changes are actually not bad as it works for enterprise solutions. But it could have some other options for super solutions for the students in colleges, and they could actually win more customers from that. Of course, we have the test licensing and all that for the partners, where it's very useful for us to be able to test more of the products. But to win more would be much easier for us also if they introduce special pricing for students, universities, governmental institutions and all that. Most probably there is a price for them, but we haven't got that information. Also, Red Hat sometimes goes directly and not through the partner, but I'm not an expert.

    Which other solutions did I evaluate?

    I wasn't the one to make a choice, but I think my company evaluated other options, and it was their choice to go with Red Hat.

    What other advice do I have?

    My company is a private cloud company. Mostly, we have our own private services, providing private cloud services to the customers. But we also provide public clouds like Azure and some Amazon clouds.

    Regarding resiliency, it is a good standardized OS with stability. But sometimes, it is a little slow in reaction to problems that might appear. For example, we had this big Java Log4j bug where their reaction was very slow compared to other distributions. Of course, they found the solution when they had it, but it was quite a slow reaction. In general, it's a very stable OS.

    Regarding how easy or difficult it is for you to move workloads between the cloud and your data center using Red Hat Enterprise Linux, I don't have any solution for that. I have to migrate it manually right now.

    Regarding the cost-saving capability of the solution, I would say that it is possible to save on costs because of the automation we use through Red Hat Satellite for maintenance and how we have managed automation, time to spend on the service, maintenance, test, problems, etc. So, you can say that it's been a cost-saving procedure.

    I rate the overall product a seven and a half out of ten.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    Allan E Cano - PeerSpot reviewer
    Sr IT Solution Architect at a wholesaler/distributor with 10,001+ employees
    Real User
    The solution has made our operations more reliable by giving us a more repeatable process
    Pros and Cons
    • "RHEL has made our operations more reliable by giving us a more repeatable process. After we've built it once, we know it will work the same way the next time we build it. It has reduced the time I spend training my operations team, and the cost of ownership is low."
    • "The cost could be lowered. We don't use RHEL in the cloud because Ubuntu is cheaper. Ubuntu factors support costs into the license when you're running it in the cloud, and it's a fraction of the cost of what RHEL is. I'm also not sure if RHEL supports open-source products. If they do, they don't advertise it. Adding stuff like Apache and other open-source tools like Tomcat to their support portfolio would help."

    What is our primary use case?

    We primarily use RHEL for LAMP stacks. Our deployment is currently on-premises, but if they change their licensing model on the cloud, we might start rolling it out in the GCP. It's used globally in VMware environments. We use it in APAC and AMEA, but the majority of the deployments are in the US. The major platforms that we run on it are PLM environment and digital asset management.

    Our shop is what we call out of the box and if it doesn't run on a container out of the box, then we don't run it on a container. So none of our stuff is running containers right now.

    How has it helped my organization?

    RHEL has made our operations more reliable by giving us a more repeatable process. After we've built it once, we know it will work the same way the next time we build it. It has reduced the time I spend training my operations team, and the cost of ownership is low. 

    The OSCAP scanner and Ansible help enforce company security standards, decreasing our exposure to attacks, data loss, ransomware, etc. From an operations point of view, managing the environment requires less overhead.

    What is most valuable?

    I like the Ansible automation and RHEL's backward compatibility with Script. It's also reliable. I also used the OSCAP stuff for a while for PCI/PI compliance. That was pretty handy and straightforward. I like the SE Linux for the LAMP stacks.

    What needs improvement?

    The cost could be lowered. We don't use RHEL in the cloud because Ubuntu is cheaper. Ubuntu factors support costs into the license when you're running it in the cloud, and it's a fraction of the cost of what RHEL is. I'm also not sure if RHEL supports open-source products. If they do, they don't advertise it. Adding stuff like Apache and other open-source tools like Tomcat to their support portfolio would help.

    For how long have I used the solution?

    I have been using RHEL for 12 years

    What do I think about the scalability of the solution?

    Linux is highly scalable in general, especially if you are using the container model, but unfortunately, we're not. I have no problem with scaling Linux or Red Hat's specific implementation of it.

    How are customer service and support?

    I rate Red Hat support eight out of 10. Most of the support engineers are competent and helpful.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    When I deployed RHEL initially, it was not very straightforward, but it's relatively easy today. The difference is the improvements to Satellite. Satellite Version 5 was kind of clunky. Version 6 seemed a little more straightforward and reliable. We don't use any kickstart, golden image, and roll and update, so there's not much to our strategy. 

    The initial deployment took over a week, but it took about two days when we moved to RHEL 6. 

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

    RHEL is competitive on-premises, but it's too expensive in the cloud. There are many cheap solutions for the cloud. In terms of upfront costs, open-source is more affordable and, in many cases, free. The long-term cost of support, staffing, and maintenance make it untenable. 

    Which other solutions did I evaluate?

    I have used Ubuntu and CentOS. I'm not a fan of Debian platforms. That's the main difference.

    What other advice do I have?

    I rate Red Hat Enterprise Linux nine out of 10. I've been pretty happy with RHEL over the years. That's 20 years of Unix right there. I tell anybody coming into Linux or Unix to learn the program. Scripting is your best friend, and you can't understand automation if you don't understand basic scripting. 

    If you've never seen Unix or RHEL before, go to a class and learn how to do it in a lab so you don't have to screw up your job. Once you're comfortable with that,  start learning containers because I firmly believe containers will replace how we do most of what we do today.

    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
    IT Systems Engineer
    Real User
    Server deployment automation has helped with our infrastructure-as-code approach, decreasing deployment times
    Pros and Cons
    • "The most valuable features are stability and supportability... You want to have something that's up and running and stable, something that's not going to crash. But if we do have an issue, we can get somebody for technical support who can help us work through the problems."
    • "Red Hat's standard deployment is with Satellite and Kickstart, but we're looking at other options to help speed it along. We do have a mix of bare metal and virtualized servers and it's easier to spin up in the virtualized world versus bare metal. That's why we're looking at some options outside of Red Hat, for the bare metal."

    What is our primary use case?

    We're using it to support security applications. We also use it for various infrastructure aspects, such as hosting Satellite or Ansible Automation or Confluence. We have a mix of different apps running on it.

    How has it helped my organization?

    Our improvement as an organization, from using RHEL, has been the ability to take the stance of an infrastructure-as-code approach. We've seen that with automation of server deployment, getting them spun up a lot faster. Traditionally, the environment was using Satellite and Kickstart. Regardless of whether we were bare metal or virtual, it could take a couple of hours to Kickstart a server. Moving to infrastructure-as-code and deploying a server takes about 10 minutes until it's ready to use. It's a lot faster.

    In addition to Satellite, we're using Ansible Tower. Those are the only ones we're paying for. We use other products, like Red Hat IDM for identity management but that's part of RHEL. When it comes to the integration between these products and RHEL, we're able to use Satellite for our dynamic inventory, with Ansible to help deploy new servers or manage servers, and we use Ansible Tower to patch our servers. Everything works pretty well.

    That integration has helped to improve things compared to how they were when I got here. For example, we have a more automated process for patching. As we develop it and work through issues, we hope it will be more of a pipeline and a lot easier and faster, compared to how it was done before. Similarly for building servers, now that we're able to use Satellite as our dynamic inventory, we're able to run Ansible, whether it's predefined playbooks or ad hoc, without having to do something manually or maintain an inventory file.

    We also use the AppStream feature in some cases. We have a couple of applications that require different versions, and we're able to install it and it makes the requirements for those specific applications.

    What is most valuable?

    The most valuable features are

    • stability
    • supportability.

    Those have been the two common and important features over the years. They're pretty equal. You want to have something that's up and running and stable, something that's not going to crash. But if we do have an issue, we can get somebody for technical support who can help us work through the problems.

    As for the consistency of application and user experience, we spin it up and almost forget about it. It just does what it's supposed to do, regardless of the underlying infrastructure. It's all good and there are no issues as far as supporting applications or things crashing go. Because it's doing what it's supposed to do, it's not a source of concern.

    And similarly, there are no issues when it comes to deploying current applications and emerging workloads across bare metal, virtualized, hybrid cloud, and multi-cloud environments. We just have to take note of whatever the requirements are for the application we're deploying, to make sure requirements are met, and then build a server based on those requirements.

    In this environment, I'm not doing any cloud work, but in my last environment we did do a bunch of public and private cloud and we had no issues there. It worked fine and as expected in AWS and OpenStack. We were doing infrastructure-as-code in that environment as well. We would create an image-base, whether for AWS or OpenStack, and then we would automate the deployment again, using Terraform and Ansible for configuration. It made deployment of cloud-based workloads relatively quick.

    What needs improvement?

    My biggest issue right now is Red Hat Consulting and trying to use some of their services to help get us going. Technically, they're good, but we seem to have issues with scheduling.

    Also, we initially deployed it with Red Hat Satellite. We're now moving more to automation using Terraform within VMware, to automate the clone and then follow up with Ansible to configure. Red Hat's standard deployment is with Satellite and Kickstart, but we're looking at other options to help speed it along. We do have a mix of bare metal and virtualized servers and it's easier to spin up in the virtualized world versus bare metal. That's why we're looking at some options outside of Red Hat, for the bare metal. We'd like something that we can use to build a server a lot faster, as well as address network latency issues.

    For how long have I used the solution?

    I have been using Red Hat Enterprise Linux (RHEL) since version 4 or even before that, since 2000 or 2001, before it was RHEL.

    What do I think about the stability of the solution?

    In the environment I'm in right now, we've never had any issues. It's very stable. 

    In another environment that I worked in, we had some Oracle Databases, but that wasn't really an issue with the operating system. It was more an issue with some configuration items between the database and the OS. And that was about four years ago.

    What do I think about the scalability of the solution?

    In the last company I worked for we were deploying a PasS environment, where we were doing some stuff with containers, and RHEL worked well. In my current environment, it's more of an application base but, again, it seems to scale. Both have worked fine.

    How are customer service and support?

    Red Hat's tech support has been pretty good. I'll open up a ticket to see if I can get information from Red Hat when I don't have the time to find it on my own. But 99 percent of the time we get great support and we're able to get the answers that we need.

    How would you rate customer service and support?

    Positive

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

    The pricing is fair. We do a bunch of dev work and there is some free dev licensing out there that's great for doing proof of concept work. When that was brought out a couple of years ago we heard about it, but it didn't seem to have been communicated to our Red Hat representative. We would ask him about it and it seemed that they were confused. 

    But the cost has been pretty stable over the years for what you get.

    We figure out what we need for servers, make our purchase, and then manage it all in Satellite. We just make sure we're using what we pay for.

    Which other solutions did I evaluate?

    In the past, I've used other versions of Unix, such as Solaris and HP-UX, as far as paid versions go. In other environments we also used community versions, like CentOS and Oracle Linux

    Oracle Linux would probably be the closest thing to a paid solution, although I think it's free. But using Oracle Linux wasn't a good experience. Dealing with Oracle support was not the best. Maybe it has improved, but it just wasn't the same as Red Hat support.

    What other advice do I have?

    Times have changed from when I first started using it. Back then it was just a matter of putting a CD in and installing it. One of the companies I worked for did a lot of homegrown stuff and I used their tools that were like Kickstart. Now it is all automation with infrastructure-as-code. The complexity of deployment is about the same. Some of what we're doing to deploy stuff is outside of Red Hat and it's a matter of finding what tools are available.

    We're in the process of deploying something right now where we have different versions of Python. That's the only use case we have with multiple versions on the same server. I don't expect any issues, but it's still early in that deployment.

    We have three people dedicated to maintaining the infrastructure environment that we work in. That includes managing Linux servers, the applications that go with them, and dealing with day-to-day tasks like patching. It's the typical life cycle maintenance functions: break/fix, dealing with hardware issues, deploying new applications, and maintaining a VMware environment.

    The reason we're using it is because it's stable and we know we can get support. I know there are other versions of Linux, ones that I've used, but I've never experienced the kind of support with those versions that Red Hat has provided. Red Hat is a stable Linux solution provider.

    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
    Snr Manager Systems Infrastructure at a financial services firm with 5,001-10,000 employees
    Real User
    Simplifies operations and offers high stability and ease of use
    Pros and Cons
    • "The simplicity of patching Red Hat Enterprise Linux is most valuable."
    • "I would rate Red Hat Enterprise Linux a nine out of ten because of the support, stability, and ease of use."
    • "Identity management could be simpler. Red Hat Enterprise Linux has Identity Manager, but it is not as simple to use as Microsoft Windows Active Directory."
    • "Upgrading from one version to another can be a bit complex. It is sometimes an issue because of multiple compatibilities."

    What is our primary use case?

    We mainly use Red Hat Enterprise Linux for general applications. We have Red Hat Enterprise Linux for identity management. We use it for NTP services. Most of the bank services that run on Linux run on Red Hat Enterprise Linux. Our core applications include bank cards solutions.

    How has it helped my organization?

    It is a stable operating system, and that is why we use it. We have many team members who understand how to use Red Hat Enterprise Linux, so it's much easier to use this version of Linux to deploy services.

    There is ease of use. A lot of resources are available online if the team wants to understand something. There is also the ability to use various automation tools to run multiple tasks.

    For risk reduction and compliance, we have CIS benchmarks. There are various configuration files that we are able to update and change. Using the benchmarks available from CIS, I can have a template and automate that across multiple machines using automation features such as Ansible. When examining permissions for file systems, enabling login, and enabling file integrity, these are the items we would use for security.

    What is most valuable?

    The simplicity of patching Red Hat Enterprise Linux is most valuable. We just use the DNF update. We use the Red Hat satellite for our patch repositories, which is quite simple. I look at it at an infrastructure level because I'm in the infrastructure team, not in the application team.

    The knowledge base is good. When we troubleshoot or have issues, we go to the Red Hat website. There are a lot of documented issues. They have a good knowledge base.

    What needs improvement?

    Identity management could be simpler. Red Hat Enterprise Linux has Identity Manager, but it is not as simple to use as Microsoft Windows Active Directory.

    For how long have I used the solution?

    I have been working with Red Hat Enterprise Linux for a very long time, approximately 15 years.

    What do I think about the stability of the solution?

    It is stable. I would rate its stability a nine out of ten.

    So far, I have not been affected by significant issues in terms of security.

    What do I think about the scalability of the solution?

    Red Hat Enterprise Linux is scalable, so I would rate its scalability a nine out of ten.

    We are using it across two sites. We have 6,000 people.

    How are customer service and support?

    I have contacted tech support of Red Hat Enterprise Linux for some questions. Their tech support is quite good compared to other companies.

    How would you rate customer service and support?

    Positive

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

    Before working with Red Hat Enterprise Linux, I used CentOS and Microsoft Windows. While comparing CentOS with Red Hat Enterprise Linux, I see stability as an advantage; Red Hat Enterprise Linux is quite a stable operating system.

    How was the initial setup?

    I have done cloud deployments and upgrades.

    It does not require a lot of maintenance. For managing Red Hat Enterprise Linux systems, when it comes to provisioning and patching, we use Ansible, which allows us to patch multiple machines. We normally use Red Hat Insights. Once we configure our machines to talk to Red Hat Insights via Red Hat Satellite, it can tell us the vulnerability status of various machines in the environment. Then, we can decide which machines are most vulnerable and patch accordingly. We can use automation tools such as Ansible to run various patches across the environment.

    We have used Leap to do the upgrades from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. Red Hat Enterprise Linux 7 was going end of life. Upgrading from one version to another can be a bit complex. It is sometimes an issue because of multiple compatibilities. You need someone who is a bit skilled on the operating system.

    What about the implementation team?

    We did the deployment ourselves, not through an integrator, reseller, or consultant.

    We have four people involved in maintenance because we have many servers.

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

    The cost of Red Hat Enterprise Linux is reasonable.

    What other advice do I have?

    I would recommend it for mission-critical applications. It's a good operating system to run mission-critical applications.

    I would rate Red Hat Enterprise Linux a nine out of ten because of the support, stability, and ease of use.

    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
    reviewer2585583 - PeerSpot reviewer
    Senior Manager, Credit Settlement Risk at a financial services firm with 10,001+ employees
    Real User
    Centralized development with long support and compliance commitment
    Pros and Cons
    • "Red Hat Enterprise Linux provides a strong foundation for compliance and offers extended support, which is particularly valuable for critical upgrades and assistance."
    • "To enhance Red Hat Enterprise Linux, I would like to see more focus on improving performance and tools such as compilers."

    What is our primary use case?

    Our banking applications, primarily those focused on transactional data services, operate on Red Hat Enterprise Linux.

    We run our workloads on Red Hat Enterprise Linux due to its compliance and long support cycle.

    How has it helped my organization?

    Red Hat Enterprise Linux has enabled us to centralize development by providing a standardized image that we customize for developer laptops, developer environments, virtual machines, and production machines.

    Our containerization projects run on OpenShift, a virtualized platform based on Red Hat Enterprise Linux, where we deploy and manage our workloads and applications.

    Red Hat Enterprise Linux is a high-performing operating system that effectively supports our business-critical operations, including high-latency, high-throughput applications essential for transaction services.

    Red Hat Enterprise Linux has robust built-in security features that effectively reduce risk in our environment.

    Red Hat Enterprise Linux significantly contributes to our business continuity and compliance efforts by inherently supporting various compliance standards, including PCI and others. This built-in compliance functionality is a major advantage, as it simplifies the process of meeting regulatory requirements and provides robust evidence for audits. Ultimately, Red Hat Enterprise Linux streamlines our compliance procedures and strengthens our overall security posture.

    The Red Hat Enterprise Linux portfolio helps reduce our TCO.

    What is most valuable?

    Red Hat Enterprise Linux provides a strong foundation for compliance and offers extended support, which is particularly valuable for critical upgrades and assistance.

    What needs improvement?

    To enhance Red Hat Enterprise Linux, I would like to see more focus on improving performance and tools such as compilers.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    Red Hat Enterprise Linux offers high performance for our business-critical operations, especially for high-latency throughput applications that are critical for transaction services.

    What do I think about the scalability of the solution?

    Red Hat Enterprise Linux is flexible, and we always get support from the team if something is not working.

    How are customer service and support?

    The customer support and technical service from Red Hat is good. When we needed support, such as for Java 21, we received early access. However, it's rarely the case that we need support.

    How would you rate customer service and support?

    Positive

    What was our ROI?

    The most significant return on investment is the long-term support, as we don't need to worry about support over an extended period. It ensures the continuation of service.

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

    Red Hat Enterprise Linux licensing is not cheap, but it is worth it, especially considering the compliance and support it provides.

    What other advice do I have?

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

    If you're considering a third-party Linux OS, try Red Hat Enterprise Linux. It offers a free subscription for developers, and if it suits your needs, you can easily transition to the production-ready Red Hat Enterprise Linux nine.

    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
    reviewer2398734 - PeerSpot reviewer
    System engineer at a comms service provider with 10,001+ employees
    Real User
    Top 20
    Affordable, feature-rich, and has enabled us to centralize development
    Pros and Cons
    • "I see so many features in Red Hat Enterprise Linux that I do not see in other Linux operating systems, such as Ubuntu. That is why Red Hat is very popular"
    • "If Red Hat can improve on the cloud side, they can retain their customer base. Their customers do not need to go out for other cloud resources, and they can use the Red Hat cloud."

    What is our primary use case?

    We have a database that we maintain for root passwords, and sometimes I need to break the root password to reset it. We work a lot on logical volumes where I need to grow and shrink volumes on the fly. I did not have to shrink the logical volumes much, but I worked a lot on growing logical volumes on the fly to make them available for the database team. I have done network-related things. I configured network multipathing or IP multipathing where we can parallelly route the traffic to multiple ethernets.

    I work a lot on user-related issues as well. We are also using Ansible a lot for automation. I am writing some playbooks, so there are a lot of use cases.

    How has it helped my organization?

    Red Hat Enterprise Linux helps us a lot. We host a lot of our applications on the Red Hat platform. We are using Red Hat Enterprise Linux for both on-prem and VM platforms. Most of them are VMs, but we do have some old legacy systems where we have Linux running on some Dell architecture. Our goal is to get rid of them this year and implement everything on virtualization because virtualization is growing a lot.

    Red Hat Enterprise Linux has enabled us to centralize development. We are using it in the production and lower environments. We are using a common platform for our deployments. We have a centralized environment.

    In terms of portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile, it is flexible. Agile methodologies are very popular nowadays, and they help with coordination between dev and production teams. It is fulfilling the gaps between these teams. It is helpful.

    What is most valuable?

    I see so many features in Red Hat Enterprise Linux that I do not see in other Linux operating systems, such as Ubuntu. That is why Red Hat is very popular. All my experience is mostly on the Red Hat side. In terms of features, I like breaking root passwords, and I like the XFS file system over ext4.

    What needs improvement?

    I have not used it on the cloud side. I have not heard much about how Red Hat is doing on the cloud side. In the market, AWS and Azure are very popular, and they have captured most of the market. If Red Hat can improve on the cloud side, they can retain their customer base. Their customers do not need to go out for other cloud resources, and they can use the Red Hat cloud.

    We are using it on-prem and in the virtual environment on VMware. We are using a cloud, but it is not a Red Hat cloud. We are using AWS in our organization. We have some EC2 instances deployed with Red Hat Enterprise Linux images, but I cannot say it is a Red Hat cloud. It is an AWS cloud, and we have instances. We are depending on a third-party cloud. If Red Hat provides that kind of service to our company, we can retain Red Hat. We do not need to go for a public cloud.

    For how long have I used the solution?

    I have been using Red Hat Enterprise Linux for almost 12 years. I started with Red Hat Enterprise Linux 5.

    What do I think about the stability of the solution?

    It is a stable platform, but our company still wants to stick to the older version. They do not want to change the application base. They do not want to take risks. Unfortunately, Red Hat is not able to help to provide the patches for older versions. They suggest upgrading, but management is not doing that, so the Red Hat Enterprise Linux side is good, but our management side is bad.

    What do I think about the scalability of the solution?

    Its scalability is good. We plan to use it more. We are growing. As our infrastructure grows, we are buying more licenses.

    How are customer service and support?

    Their customer service is excellent. I like it. I am in touch with Ed who is one of the support engineers with Red Hat. He is helping me. 

    I am also in touch with a few other people at Red Hat. If I run into any issues, I can simply email them, and I get a quick response from them. Based on the support I am receiving, I would rate them 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?

    We did not use any similar solution previously.

    How was the initial setup?

    We are using it on-prem and in the virtual environment on VMware. Our cloud provider is AWS.

    We are using the CI/CD model for Red Hat Enterprise Linux. We are using blue/green deployments as well for our containerized applications, and we have some canary deployments.

    My initial deployment experience with Red Hat Enterprise Linux was not great. It was not as easy as the current version. It was difficult during those days. We had to load the GUI and then change to CLI. It is better now. Red Hat has made some improvements in the newer versions. The current version 9 looks better than any other previous version.

    What about the implementation team?

    I did not use any integrator or consultant. I downloaded an ISO image from Red Hat. I downloaded and installed it myself, and it worked very well. I did not run into any issues with the installation process.

    What was our ROI?

    Over the last few years, we have been within budget. We do not have any constraints about Red Hat. We are a big organization. We use a lot of products from different vendors. We are working on cost optimization for some of the vendors but not Red Hat, so Red Hat is still good. We are still happy with it.

    The biggest return on investment is the customer base. We are in the telecom industry. We try to get as many customers as we can. Red Hat is not the only product that we are using, but it is a major product that we are using in our company.

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

    We are good as of now. We do not have any concerns about licensing. Its price is still good for us.

    What other advice do I have?

    We are not using Red Hat Enterprise Linux for containerization projects. We are using Kubernetes and Dockers for that.

    When it comes to patching, our goal for 2024 is to make all the systems compliant. Especially at the infrastructure and application levels, I am actively working on the compliance tasks, and our goal is to fix all vulnerabilities. I am working with someone at Red Hat on some issues because I am not able to find the exact patch for certain vulnerabilities.

    For now, we are happy with Red Hat Enterprise Linux. We are happy with what we are getting.

    Overall, I would rate Red Hat Enterprise Linux an eight out of ten. The reason for reducing two points is that I have not explored other operating systems very well.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    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.