Red Hat Enterprise Linux (RHEL) basically runs the bank's apps as my main use case.

I like the feature Satellite the most because it has services to manage my multiple Linux servers.

Satellite has no parallel in the Linux distro world, especially for an enterprise, enabling me to manage my servers, patch them, create content, get them binaries, updated security updates, and all that. It makes it easier for admins and reduces the need for a lot of manpower, especially with Ansible that enables me to do configuration management of 20,000 Linux servers.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk because the servers can run for more than 300 days of uptime. I do have to reboot them for patching, but otherwise, they are a very stable operating system that doesn't crash for no reason. If I experience kernel panics, it often involves EDRs or agents such as CrowdStrike, but otherwise, it's very stable with proactive features. We had issues with CrowdStrike; they identified the issue with their kernel drivers that used to crash my OS and provided a patch to address it, so they take care of us.

The implementation had challenges like whenever we bring out new products, there's always one issue: Red Hat Enterprise Linux (RHEL)'s documentation is not complete. I have to really have an enterprise account because I get access to their support, which sorts me out since every environment is unique. It's not a cookie cutter; I would deploy RHEL 8 in a way different compared to a retail store. So when it gets to those niche deployments, they don't have anything documented. I really have to get hold of the support, saying, "Hey, I'm trying to do this. It's not working," and then they will give me a solution, but I would expect that a document would have solved that issue without raising a ticket. That's my only complaint.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation. I don't have any other suggestions. I think it's just the documentation that needs improvement. Otherwise, technically, I don't have anything to suggest.

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

I have experienced downtime or security incidents as a result of the solution when proper practices are not followed, especially if I am using any third-party security. You have to manage kernel options; otherwise, the base OS itself is very stable.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

I would evaluate customer service and technical support based on my experience. I felt naive about being a small enterprise versus a big enterprise, but the response time of tickets is consistent. I haven't seen a difference; I thought I would have a slower response being on a small account, but the speed of our calls is the same.

I considered other solutions before choosing Red Hat Enterprise Linux (RHEL), but it was a default choice for us. I see that they have expanded; earlier, it was just a bare-metal OS and not an ecosystem, but now they are in OpenShift, providing Kubernetes and everything.

I wasn't using another solution to address my needs prior to adopting it.

The upgrade or migration is straightforward if I have applications that depend less on what the OS is, but in our case, it was not that simple. We had a business requirement, so we had to shut down the older one, provision a new one, and move everything.

I have seen ROI from using Red Hat Enterprise Linux (RHEL) in terms of uptime itself.

My experience with pricing, setup, and cost of the solution is that it's a service based on how many cores, not sockets.

My deployment model for Red Hat Enterprise Linux (RHEL) is on-premises, but I am just starting off with cloud.

For security requirements in the cloud, I don't do SELinux; I just depend on my ACLs because my servers are not internet-facing. We trust Red Hat Enterprise Linux (RHEL) with the binaries, with nothing on the base OS such as firewalls or SELinux.

I use AWS and Azure as my cloud providers.

I manage my Red Hat Enterprise Linux (RHEL) systems for security, updates, and patches with Red Hat Satellite, which makes it very easy.

I have been involved in upgrades from RHEL 6 to 7 and from 7 to 8.

My assessment of Red Hat Enterprise Linux (RHEL)'s FIPS and security compliance features is that it's the best in the industry. They have FIPS, which I think is more for federal clients, and although I haven't used it, I know they offer it by default on their Linux.

My upgrade and migration plans are to always try to stay on the current version all the time, unless there's a legacy application. Any apps I manage are always on the latest Red Hat release, and we keep migrating them as Red Hat provides the first-ever release out, which is a requirement for our Satellite to support the latest version.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as paywalled, so if you don't pay for it, you wouldn't be able to access their system. The KB is pretty good, but you need to have a Red Hat account.

My advice to a company considering this solution is to go for it. It is supported by enterprise support from Red Hat, which I don't think any other enterprise can offer. While I know Canonical does it for Ubuntu, SUSE is another good option; however, the adoption is not there, and you don't have a lot of sysadmins. Red Hat Enterprise Linux (RHEL) is a bible due to the abundance of resources in the market. I would rate this solution a 10.

The main use case for Red Hat Enterprise Linux (RHEL) is to manage the database and the server.

The solution helps solve pain points for monitoring servers, for example, databases and servers.

The most valuable feature of Red Hat Enterprise Linux (RHEL) is the security and also the performance for scheduling and tasking for the memory.

These features benefit the organization because we have hundreds of servers, databases, and many files, and we have the ability to use Red Hat Enterprise Linux (RHEL).

I am interested in migrating to the cloud platform, so we are trying to implement that in the organization.

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

I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) scales well to meet the growing organizational needs.

We are looking for containerization for scalability, and it is easy to scale out and scale in.

We have expanded usage and tried manually to increase the number of servers, and we see the disk increasing exponentially, which is why we are looking for scaling.

I would evaluate customer service and technical support as quite good, since I technically get 24/7 support if I encounter issues from updates or new features.

I would assess the level of support from Red Hat Enterprise Linux (RHEL) team as very informative; we learn a lot from the documentation from the Red Hat support team.

Before selecting Red Hat Enterprise Linux (RHEL), I considered the availability of resources and security, as we have files and a lot of data with not enough time to handle that from the internet, and distribution is mostly for security.

The experience deploying Red Hat Enterprise Linux (RHEL) was easy, as we use different methods, such as installing or using some source files by using some servers to deploy.

The most common challenges faced with the deployment are mostly enterprise related, such as resource compatibility and making automation instead of active compatibility.

The opinion on pricing and its cost-effectiveness for Red Hat Enterprise Linux (RHEL) is that it is quite good for production on-premises.

The advice I would give to other organizations is that they should mostly rely on the Linux operating system; it is quite reliable and easy to use, install, deploy, and manage, so I would advise them to use it.

I would rate this product a 10.

My main use cases include running our application in Red Hat Enterprise Linux (RHEL) since all our applications are based on a Red Hat server. Everything we use is Red Hat Enterprise Linux (RHEL).

As SecDevOps Lead, I drove the adoption of Red Hat’s Ansible Automation Platform, which transformed our deployment process. Previously, manual scripts led to inconsistencies and delays; now, we achieve consistent, error-free deployments in under 10 minutes. Weekly RHEL patching, integrated into our CI/CD pipeline, has strengthened our security posture—critical for meeting regulatory requirements. These improvements have directly supported our business goals of agility and reliability.

A key area for improvement is the ability to apply patches without requiring a full server reboot. This would minimize downtime for mission-critical applications. I’m actively evaluating Red Hat’s live kernel patching solutions and advocating for their adoption to further enhance our uptime and operational efficiency.

I've been using Red Hat Enterprise Linux (RHEL) for almost seven years.

I assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as good since I didn't see much downtime with the servers or any random problems coming up with Red Hat Enterprise Linux (RHEL). I would say it's good in terms of stability.

Red Hat Enterprise Linux (RHEL) scales well with the growing needs of my organization because whatever solutions we are trying, we are able to do in Red Hat Enterprise Linux (RHEL). It's coming along well.

I evaluate customer service and technical support as something I'm not sure about because I didn't directly work with them.

I didn't consider any other solutions before Red Hat Enterprise Linux (RHEL), and I haven't used any other solution to address similar needs.

My experience with deploying Red Hat Enterprise Linux (RHEL) is nice, but I didn't deploy anything from a Linux perspective. Overall, I think it's a nice experience that I have with Red Hat.

When it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, it has come up well over the years. Before, I think it took a lot of time to provision a server and patch it, including securing and hardening the server. Nowadays, it's very easy. I didn't work directly, but I have provisioned.

I feel that we've seen ROI since I'm not involved in purchasing, but I can feel that it's a good ROI.

My experience with pricing, including cost and licensing, is that I'm not sure.

I haven't expanded any usage of it, apart from using Ansible and Red Hat Enterprise Linux (RHEL).

My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security features when it comes to simplifying risk reduction and maintaining compliance is that it's pretty good from what I've heard when I talk with the team, even though I'm not directly working on that.As for my upgrade and migration plans to stay current, we recently upgraded to Red Hat 8. If we want to do another Red Hat 10, it's good.Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk as it allows provisioning servers very easily. In case the servers go down, it comes up very fast as well.I assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as very good. Recently, I had a walkthrough of a trial, and it's pretty much simplified and whatever we need is there.My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is to just use it. It's easy. I gave this review a rating of 10.