My main use cases for Red Hat Enterprise Linux (RHEL) are mostly development at first, and then after that, it's actually running full production loads on it.

One of the nice pain points that Red Hat Enterprise Linux (RHEL) addresses compared to other distributions is the polished applications within it.

Their repository tends to be more foolproof. The SELinux feature in RHEL is pretty strong.

SELinux is not something that I was ever using before in the open source community, and it was very confusing at first; however, after a while, it made sense why that layer exists. The SELinux feature and other features of RHEL benefit my company by allowing us to lock in the server more traditionally than we would be able to with special permissions.

It's about getting very granular versus just putting an umbrella on some things, and security-wise, it's very effective.

The security features of Red Hat Enterprise Linux (RHEL), including SELinux and its features, make it easier to be aware of compromises.

The Insights tool is very good at providing CVEs to alert us about vulnerabilities quickly. I can't quantify the impact in percentage terms since I haven't faced specific situations. However, the outlook compared to other distributions looks good.

To improve Red Hat Enterprise Linux (RHEL), it would be helpful to have a step-by-step process to make setup easier. Cockpit needs more features to manage complex tasks such as RAID configurations, as most of that is reserved for the command line.

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

I find Red Hat Enterprise Linux (RHEL) to be super stable and super reliable.

I have not scaled Red Hat Enterprise Linux (RHEL) outside of using templates and cloning features. I haven't scaled it out with OpenShift yet; it's something I want to explore, as I now understand what tools OpenShift can offer to scale out RHEL machines effectively.

My experience with customer service and technical support for Red Hat Enterprise Linux (RHEL) is mixed. On a professional level, they are very responsive, which is part of the contract, but on a personal level, responses can take forever, and I often get pointed to community posts.

We did not consider any other OS solutions while using Red Hat Enterprise Linux (RHEL), although there have been discussions about using Ubuntu. I don't think it will go that way because we are very satisfied with what RHEL offers overall.

The biggest return on investment with Red Hat Enterprise Linux (RHEL) is that every time I put an application or tool in there, it's going to work. I don't have to second-guess it or go back; I know it will be a polished application.

Regarding the experience with pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL), I would say it's beyond my pay grade. That said, it's not cheap at all. While it could always be cheaper, they provide substantial value for the money, and they consistently introduce new features that add value.

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

It's a great OS that has grown on me over time, and the more I use it, the more I understand its value and why it costs what it does.

My main use case for Red Hat Enterprise Linux (RHEL) is application servers, and it's all of our VMs. Most, if not all, of our physicals, on the Linux side, are Red Hat. The only thing that we run that isn't Red Hat is our Kubernetes nodes.

The feature of Red Hat Enterprise Linux (RHEL) that I find most interesting is image mode, which has ramifications far beyond just upgrading the OS. Speed to market and zero day could really be accelerated leveraging it.

Red Hat Enterprise Linux (RHEL) benefits my company at the end of the day by providing the foundation of Red Hat Linux, over 20 years and more. Coupled with the backing of a company such as IBM, you've got a company that can help solve pretty much any problem.

It's the flexibility, almost the one-stop-shop nature, that Red Hat provides, that really creates an administrative-friendly environment.

The package manager is pretty solid now with DNF, which is the industry standard.

Red Hat Enterprise Linux (RHEL) helps solve quite a few pain points; I would say that in RHEL 8 to RHEL 9, when they went to AppStreams, it really helped simplify the repository structure and made package management significantly easier.

I wasn't part of the discussion about whether security requirements were a consideration in choosing Red Hat Enterprise Linux (RHEL) for our cloud operations, however, my guess is that it had to do with being able to do configuration management across on-prem and cloud in the same manner in both environments.

We manage our Red Hat Enterprise Linux (RHEL) systems through Red Hat Satellite, which we do not use to provision but only to patch, while provisioning is done through vRealize Automation. That's how we provision all of our VMs and custom builds, though there is additional infrastructure behind that.

Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy as we are currently in the process of investigating different VM hypervisors, and as that investigation goes on, OpenShift is definitely at the forefront of the things we are looking at.

My number one request for improvement would be better Kickstart functionality, as I feel the Kickstart notation is outdated and it's not programmatic, so that would be my focus point, based on what I do.

From my perspective, I would prefer to see more of the knowledge base offered by Red Hat Enterprise Linux (RHEL) be freely available and not tied behind a Red Hat account, as there's a lot of common knowledge content that would be really helpful to many people. Now, I have a Red Hat account, so it doesn't matter to me. Still, that would be a great show of faith on Red Hat's part to open up many of those knowledge articles and make them freely available.

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

My thoughts on the stability and reliability of Red Hat Enterprise Linux (RHEL) are quite positive; my stuff doesn't go down, so I don't have problems.

It's one of those nice things, similar to your refrigerator—you don't notice it until it breaks. It just works, and that's really the key factor; I can't remember the last time we had a system go down and had to restore it due to a bad patch. Those things just don't happen. The way they have things set up with Fedora, CentOS, and all of that user testing and integrated testing feeds into a really good final product, one that's stable and that you can rely on.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my company effectively, as we are currently running approximately 11,000 Red Hat VMs, and we manage, patch, and do everything all the time without issue.

I've seen a significant decrease over my twenty-ish year career of needing backup tools to restore files since files just don't get corrupted the same way that they used to, making me feel Red Hat has really kept up to date with all of the intricacies and small components of the OS to provide a great ecosystem.

I cannot speak to the customer service and technical support of the platform, as I don't have to open tickets; there's a whole other team that does that. My understanding is that we have a regular cadence with our Technical Account Manager once every other week or once a month, and we've had good successes to the best of my knowledge.

While working with Red Hat Enterprise Linux (RHEL), we actually considered other solutions, specifically SUSE Enterprise Linux, which we were running for quite some time until their pricing model changed. Red Hat offered a better pricing model, a more mature product, and it was just overall better in my opinion.

I have been involved in Red Hat Enterprise Linux (RHEL) upgrades and migrations in my company, and it depends on what your approach is, however, we don't do in-place upgrades, as they're just dangerous, no matter what anybody says.

I always say a fresh install is always the best thing, so for us, it's a matter of leveraging Kickstart and Packer to generate the VM images or Kickstart to generate ISOs and install them on physicals. It's just a matter of taking and being able to easily set it up for repeatability, although it takes probably more time than I would prefer to get that consistency.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) for me is its close coupling with Ansible, which I am a big fan of. I've been here since the beginning, and Ansible is a great marrying tool with RHEL to really manage those systems at scale, allowing me to do pretty much anything, which I do every day; it's awesome.

Assuming you can leverage virtual data center licensing, I don't see the costs as being terrible. There are a lot of viable ways to decrease those costs while increasing the value you get from RHEL by leveraging CentOS and lower environments.

Overall, I don't end up having to write the check at the end of the day, however, I've heard that the licensing models have changed a bit since I've had to work with them directly and that they're less painful than they had been before, with a lot of moving licenses from one pool to another pool, which I've heard you don't have to do now, so that's nice.

On a scale of one to ten, I would rate Red Hat Enterprise Linux (RHEL) and eight out of ten.