Red Hat Enterprise Linux (RHEL) Reviews

My main use cases for Red Hat Enterprise Linux (RHEL) are everything from research computing to hosting websites. We've run a gamut of different things with RHEL. 

I used to use it a lot for a healthcare company and healthcare software. Now predominantly, it's research that is very statistically intensive. So anything where we have to do data computations, data rates, we need to synthesize data, aggregating it from instruments all over the world or within the lab itself. We take all of that, and we also use it to produce applications for people, whether it's just interacting with it via a website or an actual homegrown application where they can go through, search, look at the data, and do their own data manipulation.

My favorite feature of Red Hat Enterprise Linux (RHEL) is the ease of use; it is streamlined, making it very intuitive to do things. 

The ease of use of Red Hat Enterprise Linux (RHEL) reduces time for my company. It reduces the time to do things, allowing us to do very complex tasks in a very short period, since it is very straightforward and makes it easier to get things done. 

It has been around for so long, and it's such a standardized platform that the knowledge base from the employee perspective is usually pretty high compared to other enterprise Linux distributions. Therefore, the overall time savings with RHEL is huge.

Our upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) involve adhering to a rule: once a version reaches end-of-life, we do not enter the extended life cycle. We plan that out ahead, ensuring that all of our systems get migrated and updated about a year before the end of life of any version. Some systems get migrated to the latest version while others remain and just get updated to whatever is current. It depends on the application and its external dependencies, but it's just a solid plan we follow.

Red Hat Enterprise Linux (RHEL) has helped us mitigate downtime and lower risks, as we've utilized virtual machines and process load balancing to minimize issues. While we've had downtime with any systems, there tends to be a lot less with RHEL. We have had some systems running just for fun for three years without any downtime, which reflects their stability. I would say that RHEL has reduced risks by at least 80% compared to open-source distributions based on experiences in recent years.

To improve Red Hat Enterprise Linux (RHEL), the biggest thing is the availability of some tools that unfortunately have to be paid for. While I understand that you have to pay for resources, it would be nice to have a centralized location where you can easily find those tools.

I have been using Red Hat Enterprise Linux (RHEL) for close to 20 years.

Regarding the stability and reliability of Red Hat Enterprise Linux (RHEL), we have systems that we've kept running for years without any downtime, so I have never had a problem with stability or reliability.

Red Hat Enterprise Linux (RHEL) has scaled right along with our growing company needs; the only exceptions to that are with supercomputers, but that's a whole different animal.

My experience with customer service and support from Red Hat Enterprise Linux (RHEL) has been good so far. I haven't needed to use it often, which goes back to its reliability. Whenever I've had issues reaching out, they've responded quickly with appropriate information.

We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others, however, we keep going back to RHEL due to its reliability and available resources.

The deployment experience with Red Hat Enterprise Linux (RHEL) has been very easy; we've been doing it for years. The automation that they've built over the years to do the deployments just makes it easier and easier every year, transitioning from kickstarts to using things OpenShift. I'm excited to see how this Image Builder works with that, too, so it has continuously improved.

The biggest return on investment for me from using Red Hat Enterprise Linux (RHEL) is just overall time saved. 

We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others. We keep going back to RHEL due to its reliability and available resources.

I would rate Red Hat Enterprise Linux (RHEL) overall at least a solid ten out of ten.

I am currently working on dialing up telecom services that are due to telecommunication needs in Sri Lanka. We are using this for mother data center activities, not only as a solution but for multiple purposes. I am currently handling the data engineering team.

Red Hat Enterprise Linux (RHEL), we are testing. Red Hat Enterprise Linux (RHEL) ten point one is also there in beta. In that manner, Red Hat Enterprise Linux (RHEL) does a couple of things. We are the partner of Red Hat Enterprise Linux (RHEL) in our dialogue at the digital lab.

At the moment, we are using ten. Because we use it most of the time for the test bed, which is the development bed, ten is at the moment our version.

The main thing as a cloud-based solution is valuable. Beyond that, it is an on-premises solution. We are also using a stable established version called nine point two from Red Hat Enterprise Linux (RHEL). We are supposed to move to Red Hat Enterprise Linux (RHEL) as well.

Red Hat Enterprise Linux (RHEL) is paid. When it comes to the total Red Hat Enterprise Linux (RHEL) management, they are using project insight for part of the services. We will take that Red Hat Enterprise Linux (RHEL) Insight.

That is really helpful. It is a kind of dashboard, not only a dashboard. We can get decision-making capabilities going forward when it comes to security.

OpenShift gives a good solution for us on the Red Hat Enterprise Linux (RHEL) end. The session, not only the station, has the CI/CD pipeline and operators connecting. That is a really good improvement on the Red Hat Enterprise Linux (RHEL) side.

Sometimes we are lagging in the Red Hat Enterprise Linux (RHEL) part because we have to deploy in non-straightforward environments. Some environments have third party deployments where party enhancement happened.

Red Hat Enterprise Linux (RHEL) is lagging in these scenarios. The main problem we are facing is the cost factor. Because it comes to long and short terms, stakeholders do not want to move to a good business solution because of the cost factor. That is still where we are lagging.

I have been using this solution for more than industrial use, more than fifteen years, almost twenty.

I think that now, as of just now, there is no downside. It is not crashing, basically. The application is rebooting every time because of some kind of bug.

You have to master the tips and then come to Red Hat Enterprise Linux (RHEL). The knowledge base is actually lagging because most of the people do not want to work with the backend coding and Red Hat Enterprise Linux (RHEL). We are commanded to use it to upgrade anything.

Because of that knowledge gap and Red Hat Enterprise Linux (RHEL) in Manam, but people are not using much more. Even administrators are not using proper principles and guidelines to do so.

When I was in the consumer space, I realized console R is also more toward Red Hat Enterprise Linux (RHEL) kernel. Exadata and now Oracle are all moving to Red Hat Enterprise Linux (RHEL) because of the kernel quality.

It will help a lot. When it comes to big data development, we have twenty servers to deploy with all kinds of packages and modules. Then it will easily deploy using the Ansible playbook to write the code and everything. So it is easier to deploy, actually.

It is an integrator, basically. It is cloud and cloud enablement because I had experiences when we were going to do that Cloudera migration.

That is really helpful now when it comes to the integration point of view. That is Red Hat Enterprise Linux (RHEL) too, I believe.

Then we are going to do some implementation. They are aligned with the Dell partners. Those kinds of matters come up because of the cost. This comparison comes to the picture.

When it comes to the backup solution, we are using tune the profile to utilize the backup solution. When we are using performance stack, we have tuned the performance stack to do a couple of testing in production as well. That is the main thing we are basically using most of the time.

Our engineers are supposed to do that base. Now they are implementing that base. I carry it forward to the next level, which is the business solution. When we are seeing Red Hat Enterprise Linux (RHEL) Insight, we can take the next action as much as the next action method allows. For instance, when we say we want to patch the environment, Red Hat Enterprise Linux (RHEL) we are testing. Red Hat Enterprise Linux (RHEL) ten point one is also there in beta. In that manner, Red Hat Enterprise Linux (RHEL) does a couple of things. We are the partner of Red Hat Enterprise Linux (RHEL) in our dialogue at the digital lab.

Next year, I will recommend Red Hat Enterprise Linux (RHEL) because they have a lot of features and functions, especially for the enhancements. When it comes to security, now they have a lot of features. For instance, saving us is a really good enhancement way to achieve the environment. When it comes to the use of solution, that is really interesting.

I am using Red Hat Enterprise Linux (RHEL) for almost fifteen years now. I really understand what Red Hat Enterprise Linux (RHEL) did then and what kind of solutions they provide. Accordingly, I am aligned and most of the time when I say I am going to do some kind of upgrade, I definitely use that release and knowledge, principle, and guidelines. Otherwise, we cannot do it. I have given this review a rating of ten out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) are primarily our websites and applications that run on top of Red Hat Enterprise Linux (RHEL) operating system platform.

What I appreciate most about Red Hat Enterprise Linux (RHEL) is the SELinux policy that has been introduced; I believe that is truly good security, although it was difficult initially to become accustomed to it. In the modern world, you don't want every user to have accessible permissions. It gives you a granular level of control over each and every file and directory, just as ACLs used to provide in the past. By using SELinux policy, you can actually secure these accesses and establish a strong security posture.

The main business problem that Red Hat Enterprise Linux (RHEL) helped us solve is automation of tasks and scalability of the business. Red Hat Enterprise Linux (RHEL) has helped reduce downtime because in modern infrastructure, you do not face out of memory issues. Red Hat Enterprise Linux (RHEL) has affected the downtime by reducing it to a minimal level; the reboots are very speedy.

I think the support for Red Hat Enterprise Linux (RHEL) can be much better; when it comes to something such as SUSE Linux, I feel those providers are doing a much better job in terms of support than what Red Hat provides. One area where Red Hat Enterprise Linux (RHEL) stability could be improved is with Ksplice; Ksplice is used for online patching. The problem I have seen with it is that it applies patches at the user level, but not at the kernel level. That was a problem in terms of our security architecture because it doesn't recognize that the patch has been installed. I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.

I have been using Red Hat Enterprise Linux (RHEL) for the past three years.

My assessment of Red Hat Enterprise Linux (RHEL)'s stability and reliability once it is deployed in production and maintained is that it's straightforward, but there's a huge functionality and learning curve. We started using it and actually understood the reason why Red Hat has implemented it and the level of granularity in terms of security posture that it provides. We understood that it's doing a really good job.

I assess the stability, availability, and reliability of Red Hat Enterprise Linux (RHEL) as pretty stable and very reliable.

Red Hat Enterprise Linux (RHEL) has crashed or failed here and there, but there were some settings that needed to be changed. We make sure that we match those parameters.

Red Hat Enterprise Linux (RHEL) scales to my needs pretty much up-to-date.

The support from a competitor I've used is Oracle. My experience with Oracle support is that Oracle on-premises support, what it provides with Oracle Enterprise Linux, performs very well, and many of our customers believe that something from Oracle is more secure. When they compare Oracle with Red Hat, it has a much better support system and a much more secure posture than what we get.

I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.

Neutral

My experience with the deployment of Red Hat Enterprise Linux (RHEL) has been smooth because back then we were on-premises and all our information used to be on-premises, rather than run them completely as we do now.

I have evaluated a couple of operating systems including Ubuntu, Oracle Linux, SUSE, and then came to Red Hat Enterprise Linux (RHEL) because Red Hat is considered the pioneer.

I have considered replacing Red Hat Enterprise Linux (RHEL) with another solution; specifically Oracle Linux.

If I were to switch, I would consider factors such as security and support.

We are currently considering using the Ansible Automation Platform for configuration and patching; we are using a manual approach and a little bit of Ansible here and there, but not fully deployed an Ansible Automation Platform or command line approach. But today I had the experience in the lab with the Ansible Automation Platform. That looks truly promising. I hope to get a chance to do a proof of concept and show my company that this is the product we can use in the future.

I have used the in-place upgrades to migrate machines to a newer release of Red Hat Enterprise Linux (RHEL); I used LEAP which has been designed to upgrade Linux 7 to Linux 8, and it was smooth. I think that was truly good work, especially because it supports you in situations where you do patching.

The upgrade process for Red Hat Enterprise Linux (RHEL) is straightforward and we didn't have any problems.

We are planning on upgrading from Red Hat Enterprise Linux (RHEL) 6 and 7 to 8, though we do have some legacy applications that would not support it. However, other systems which are web servers or Apache, we are trying to upgrade them.

I haven't found any limitations in Red Hat Enterprise Linux (RHEL)'s security.

My assessment of the documentation offered by Red Hat Enterprise Linux (RHEL) is that Red Hat's documentation is top notch. You cannot compare that with SUSE.

My specific goals that led me to choose Red Hat Enterprise Linux (RHEL) include the security posture.

Current, I am using the standard lifecycle support add-on for Red Hat Enterprise Linux (RHEL); I think we are still sticking with the standard and haven't upgraded yet.

The advice I would give to a team considering Red Hat Enterprise Linux (RHEL) is that one of the new features that it has is promising, and everybody promises great things with new features. My overall rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) are server virtualization.

It allows us to stay more in line with our mandates.

What I value the most about Red Hat Enterprise Linux (RHEL) are the patching capacity and the patching capacity with Ansible. The patching capacity of RHEL has improved my company significantly. It allows us to stay more in line with our mandates for our infrastructure. I assess the knowledge base offered by RHEL as fantastic.

Security requirements were a consideration when choosing the solution. We liked that the patching rules were straightforward. We've had good experiences with provisioning and patching.

It helps support risk reduction and maintain compliance. The user interface is very intuitive.

We'll be migrating more to RHEL 10. Some in our environment are still in RHEL 7.

It's helped us mitigate risk. Any time we've had to do a patch update, the patch time is minimal. The risk reduction has been significant.

The knowledge base offered by RHEL is excellent. 

Even though I don't have complaints, I would like them to focus even more on what they're doing with Lightspeed and the AI assistance, so they could look more into that.

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

I have never had any problems with the stability and reliability of the Red Hat Enterprise Linux (RHEL) platform.

Red Hat Enterprise Linux (RHEL) helps me solve pain points by being more scalable.

I have not yet had any experience with customer service and technical support.

We have not used another solution before choosing Red Hat Enterprise Linux (RHEL), nor are we considering another solution; we've been staying a RHEL shop.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is that it's very easy to scale up with regards to patching and updating.

I really dont have much to do with the licensing aspects. 

The advice I would give to other companies considering Red Hat Enterprise Linux (RHEL) is to seriously look into it and really not be too stuck or hung up on one single platform, and explore your options. 

I rate RHEL a nine out of ten.

My main use cases for it are servers, such as web servers, database servers, and any type of server that we need.

Red Hat Enterprise Linux (RHEL) helps us solve pain points related to security, CVEs, and patching. 

The benefit for my company is that it saves time on compatibility issues. I don't have any metrics of roughly how much time has been saved, but I just know we don't have the combat. I've done Ubuntu, and Ubuntu doesn't compare to Red Hat, so I just know when I need to install something, it works. There are very few times when I've had issues.

Security requirements were a major consideration when choosing Red Hat Enterprise Linux (RHEL) in the cloud because they have secure patching. We review all RPMs and stuff that we import, and that's the major reason.

The feature I appreciate the most about Red Hat Enterprise Linux (RHEL) is the DNF, yum updates, and RPM, which make it easy to install applications and customize it.

Red Hat Enterprise Linux (RHEL) can be improved by making the licensing easier for Amazon EC2 instances. When we try to do auto-scaling, the licensing is hard to automate.

I have been using it since Red Hat Enterprise Linux 4, so probably 2005.

It's very stable. I haven't had any issues. We don't have to worry about it crashing.

Red Hat Enterprise Linux (RHEL) scales very well with the growing needs of my company. I've done from one or two to thousands, so it's not a problem.

Their knowledge base is great. Anytime we have patching issues or anything else, we reach out to support, and they always have an answer.

Their technical support has been great. I haven't had any issues with that as they respond right away.

Positive

It has been very good. I've done from one or two to thousands, and I've never had a problem. The only issues were hardware-related. They've been able to support drivers and things like that.

We have a hybrid environment with both on-premises and cloud deployments. I specialize in AWS.  Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy. When we have things that can't go into AWS, we can spin up a Red Hat Enterprise Linux EC2 instance in AWS to run legacy stuff or stuff that's not compatible with AWS.

We usually use Ansible for provisioning and patching. I am 100% satisfied with the management experience of Red Hat Enterprise Linux (RHEL) systems when it comes to provisioning and patching, and I have no issues.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is probably stability, as I don't have to worry about it crashing. I've had issues with other forms of Linux, so it's been pretty stable.

It's been good, but I don't really get involved with that.

We did consider other solutions, such as Ubuntu, Amazon Linux, and Rocky Linux. but Red Hat Enterprise Linux was the one we went with. The biggest reason Red Hat Enterprise Linux (RHEL) leads the way is support and security.

I would rate Red Hat Enterprise Linux a 10 out of 10 because of the stability and security. That's the main reason I use it.

My use cases for Red Hat Enterprise Linux (RHEL) include doing OpenShift tasks and general Linux use cases.

The feature of Red Hat Enterprise Linux (RHEL) that I value the most is automation. Automation saves time for me as I don't have to keep doing the same tasks repeatedly. My company benefits from automation in Red Hat Enterprise Linux (RHEL) since we use Ansible to deploy numerous operating systems. 

We can initiate 20 deployments, and they get configured automatically, which is efficient.

Red Hat Enterprise Linux (RHEL) might have helped to mitigate downtime and lower risk, though I cannot think of a specific example.

Improving Red Hat Enterprise Linux (RHEL) is a challenging question. Regarding SELinux, they could make that clearer or make it easier to use.

I have been using Red Hat Enterprise Linux (RHEL) for about a year.

The stability and reliability of the Red Hat Enterprise Linux (RHEL) platform are really amazing. There are many instances where I'll have an Active Directory server go down, and I go into the remote consoles because Windows is doing forced updates, and it drops, which is extremely annoying. I haven't experienced any similar issues using RHEL.

Evaluating how Red Hat Enterprise Linux (RHEL) scales with the growing needs of my company is challenging because much of what I do is lab work, so most projects are not scaling out. They remain at a set scale, then get torn down, and we create another one at that same scale.

I've had limited experience working with Red Hat support. 

I submitted a ticket because I was trying to access training material since we were a partner and were supposed to get it free, however, I had an issue with my account. 

I opened a ticket, and the person who took it responded in 20 seconds and fixed it immediately, which was excellent. I would rate the customer service and technical support of Red Hat Enterprise Linux (RHEL) at a ten out of ten. It was extremely fast.

Positive

I'm not certain if Red Hat Enterprise Linux (RHEL) is the first solution of its kind that our company is using.

Most of my management of Red Hat Enterprise Linux (RHEL) systems for provisioning and patching is done in labs, so I don't see many persistent workloads. Most systems get torn down. I haven't done much patching, but I'm familiar with Cockpit, and I have personal VMs that I manage that way.

When upgrading from RHEL 8 to RHEL 9, we encountered some issues and had to use a leap utility for jumping between releases. Once we found the documentation, the process was straightforward.

Since we operate in a lab environment, instead of upgrading Red Hat Enterprise Linux (RHEL), we typically download the newest release.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) from my technical perspective is automation. I use automation daily to provision VMs and other systems. You can initiate the process and focus on other tasks while it runs, which increases efficiency.

I get our licensing for Red Hat Enterprise Linux (RHEL) through our account team, so I don't handle that aspect.

We did not consider other solutions to my knowledge before choosing Red Hat Enterprise Linux (RHEL) since Ansible is ubiquitous in our environment.

I would rate Red Hat Enterprise Linux (RHEL) overall as a nine. There are some inconsistencies with commands, since it's built upon years of development, some legacy commands remain with opposite rules compared to newer commands. If it were more consistent, it would merit a ten.

Red Hat Enterprise Linux (RHEL) is user-friendly and easy to use. The affordability and free open source nature are main points. Multiple tools can be installed easily, and the interface is very user-friendly.

I am using Red Hat Enterprise Linux (RHEL) on Docker. I work on Docker with both Red Hat Enterprise Linux (RHEL) and Docker. Installation of so many tools is easy and simple for my Red Hat machine.

The features of Red Hat Enterprise Linux (RHEL) that I find to be the most valuable and useful are that it is user-friendly. The command is very user-friendly and easy to use, and easy to remember. That is a main point. I install it everywhere on my cloud server because I am using a virtual machine also on my PC.

A specific feature of Red Hat Enterprise Linux (RHEL) is that I can install multiple tools without any interruption. I can configure everything easily, such as network ports. I can configure networking using vim commands and multiple commands. Red Hat Enterprise Linux (RHEL) provides more alternate commands for my convenience.

Red Hat Enterprise Linux (RHEL) is very good. Red Hat Enterprise Linux (RHEL) provides the updated latest version yearly. However, they could provide more flexibility in areas such as adding more networking features. For security reasons, since security is a main key point for privacy in upcoming years, they could provide more DPDK for fast signaling and add more new protocols.

I have more than four years of experience with Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) needs some improvement for stability. I am currently working on the latest version only. The latest version is not familiar to me, and I need to upskill on my side also. Red Hat Enterprise Linux (RHEL) should provide more free courses for the upcoming or latest version that explain what changed between the latest and previous versions. Red Hat Enterprise Linux (RHEL) is not providing courses on sites or readable materials that explain what commands should be used.

I have communicated with the technical support of Red Hat Enterprise Linux (RHEL). Previously, I did receive technical support in my previous company, and they provided an update for my servers. I rate the technical support services of Red Hat Enterprise Linux (RHEL) as good, giving it a 9 out of 10.

Positive

I used SUSE Linux and CentOS before Red Hat Enterprise Linux (RHEL). Red Hat Enterprise Linux (RHEL) is much better than CentOS and SUSE. Red Hat Enterprise Linux (RHEL) provides its own cloud, OpenStack.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) provides free courses for everyday work. I am currently using shell scripting, which is very useful for automation and easy to deploy on Docker and CI/CD pipelines for Jenkins. Shell scripting is the main knowledgeable area right now.

The most important security feature in Red Hat Enterprise Linux (RHEL) is that it provides multiple ports in the Linux machine that are connected via the kernel. The kernel is the main core of the network of Linux. No one can bypass this kernel line. The networking security feature is a main point.

I am not familiar with Image Builder for Red Hat Enterprise Linux (RHEL) and have not built any images using Red Hat.

Regarding the pricing of Red Hat Enterprise Linux (RHEL), I am not purchasing any membership right now. I purchased it previously, but I am not currently.

I chose Red Hat Enterprise Linux (RHEL) because it is so user-friendly. In every server, I need to use it for security reasons, and it is user-friendly for everyone. The source code is very simple. I can create my own tools and automation scripting.

My overall rating for Red Hat Enterprise Linux (RHEL) is 10 out of 10.

My main use cases for Red Hat Enterprise Linux (RHEL) are that previously, I used it on database servers, and right now, we are using them for web servers, JBoss, and JDV servers.

Red Hat Enterprise Linux (RHEL) scales well with the growing needs of my organization because RBC always needs new servers, whether they can be Linux or Windows servers, but mostly we are using Linux since we don't use JBoss or JDV on Windows.

Red Hat Enterprise Linux (RHEL) helps me solve pain points because it is very versatile and stable, and we always use it for our new business.

Specifically, I can say that if we have a subscription, we can make installation easily and access repositories easily.

This benefits my organization significantly because Red Hat Enterprise Linux (RHEL) is really useful, very stable, and very versatile.

In terms of additional features for the next release, I saw it comes with AI integration, but we don't know the architecture yet. We want to see it first, then we can say. AI will be important for us.

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

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as nine out of ten.

I have experienced downtime, crashes, or performance issues, but it happens only maybe once a year or something. There is not very much downtime.

I'm not sure if we have expanded our usage at all.

I am very satisfied with the technical support experience; it is very nice.

I would evaluate customer service and technical support as nine. I can give a nine because if we have any problem, we can get a response in a short time, but sometimes it is not the relevant solution; that can happen one or two times in a year, which seems normal.

Positive

I have not used another solution to address similar needs prior to adopting Red Hat Enterprise Linux (RHEL).

Our deployment model is that RBC is using all of them—on-prem, cloud, and hybrid.

I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as limited because mostly it is our Linux team working on it. They are the ones deploying it while we mostly are ordering servers and using them.

I have not seen an ROI with Red Hat Enterprise Linux (RHEL), as I'm not on the finance side and I'm not calculating it.

My experience with pricing, setup cost, and licensing indicates that if you compare it with other operating systems, Red Hat Enterprise Linux (RHEL) is cheaper than them.

We are not on the selecting side before choosing Red Hat Enterprise Linux (RHEL) because if you want to use Linux, Red Hat Enterprise Linux (RHEL) is always our first option. We don't check other options.

What stood out to me about Red Hat Enterprise Linux (RHEL) is that I remember Oracle released a Linux for their database installation, but I don't see anybody using that, as we are mostly using Red Hat Enterprise Linux (RHEL).

I prefer Red Hat Enterprise Linux (RHEL) as an operating system.

I'm not sure if Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk.

Red Hat Enterprise Linux (RHEL) has improved since version five, then six, seven, right now eight and nine; it always comes with new features, sometimes new application security enhancements. Red Hat Enterprise Linux (RHEL) is improving, and it has improved.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as very nice because if we have any problem or error, we can find it easily at the portal.

Nothing is perfect.

My advice to another organization considering Red Hat Enterprise Linux (RHEL) is that I prefer to use Red Hat Enterprise Linux (RHEL) always. I recommend Red Hat Enterprise Linux (RHEL).

I gave this review a rating of 9 out of 10.