Red Hat Enterprise Linux (RHEL) Reviews

Red Hat Enterprise Linux (RHEL) is just a piece of an operating system for my company, and what we need the most is STIG compliance because we have a lot of different customers.

Red Hat Enterprise Linux (RHEL) has helped my company since, with it, we have gotten more customers. Now, our company can say upfront that we use Red Hat and are STIG compliant while also being security-focused, which really helps open up the door to people who want to get their stuff done.

The most valuable feature of the solution is its good integration with Ansible.

Red Hat Enterprise Linux has not helped centralize development in our company, especially since we deal with unique use cases in our organization. My company still develops locally on CentOS, but once our company actually completes the product for our customer, it gets shipped somewhere else and we can't centralize things since we don't have that much time to spare owing to which we stay disconnected after the aforementioned process.

My company plans to use the product for containerization projects, especially since we are in the process of converting to Kubernetes.

Based on my assessment of the the built-in security features when it comes to areas like risk reduction, business continuity, and compliance, I would say that I am a big fan of the tool.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, it has been pretty good since all the containers have been very portable without having to deal with any environmental issues.

If I had to give a suggestion to a colleague who is looking at open-source cloud-based operating systems for Linux instead of Red Hat Enterprise Linux (RHEL), I would say that one should look at AlmaLinux since it is the closest thing one can get to Red Hat.

The product's deployment model is usually in a single data center, and it consists of one machine at a time. Red Hat Enterprise Linux (RHEL) does not use a public cloud.

The documentation is an area of concern where improvements are required. Sometimes, I go to look at stuff in the tool's documentation to see how to configure something, and it doesn't make any sense. The tool's documentation is written by someone who already knows how it works for those who need to learn how it works. Everything else in the documentation is really good, though. I would describe the documentation as a kind of a hit or miss.

I have been using Red Hat Enterprise Linux (RHEL) for about six months.

It is a scalable solution.

I would like to expand the use of the product in the future, but our company's business model is contract-based and very slow, which makes it difficult to work with Red Hat Enterprise Linux (RHEL).

As per my evaluation of the technical support offered by the product, I would consider the support services offered to be at a 50-50 rate since everything really depends on who you get to talk to from the support team. Some of the people from the product's support team to whom we reached out didn't understand our use cases or our problems, so they couldn't help us at all. Some of the support staff members who understood what our company meant when it came to the issues associated with the product were able to help us in 30 seconds. My colleagues who contacted the product's support team were satisfied with the technical team's services. I rate the technical support a six out of ten.

Neutral

In my company, we used to use CentOS. Now that CentOS has reached the end of life phase, it doesn't meet our company's needs, so we transitioned to Red Hat Enterprise Linux (RHEL).

Previously in my company, we used to use CentOS. CentOS will reach the end of life phase in the upcoming month, which is the reason why my company had to choose another product like Red Hat Enterprise Linux (RHEL).

The solution is used on an on-premises model.

Deploying Red Hat Enterprise Linux (RHEL) was surprisingly easy. The installers were the same as the ones used for other solutions.

My company did not have a strategy to deploy the product since we just needed Red Hat to hurry up, put it on a box, and figure it out.

My company did not seek the help of a third party to help us with the product's deployment phase.

The biggest ROI I have experienced from the use of the solution revolves around the area of customer satisfaction. My company's customers who use the product have a lot less to be changed in the product and it has helped save a lot of development and redevelopment time for our organization.

The cost and setup are not areas that are transparent for me. The tool's licensing part has been a real pain because when our company sells a system to a customer, they take full control of it in their data center, and we are not allowed to access it, even though they bought it from us. The license transfer has always been really awkward because our company initially had the license until our customers tested it and accepted the product. I was hoping to find somebody to talk to about the license transfer part with Red Hat products, but I don't know where to find someone associated with the solution.

My company briefly evaluated a product named Debian, but after that, our company's customers specifically asked us to go for Red Hat Enterprise Linux (RHEL).

Considering that the licensing part associated with the product is a pain, I rate the tool a seven out of ten.

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.

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.

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.

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.

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

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.

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.

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.

Positive

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.

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.

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.

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.

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.

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.

We are a Linux shop, so a lot of our engineers are familiar with Linux. We try to push Red Hat Enterprise Linux instead of Windows. The reason for it in the beginning was licensing. Some of it was because of the way the contract was set up. It was cheaper, but we do use it now just for the ease of it. I do not know if it is because of Ansible, which we use for a lot of our day-to-day operations, that we tend to lean more toward Red Hat.

Red Hat Enterprise Linux has affected our system's uptime or security. I know Microsoft publishes zero-day vulnerabilities for Windows as fast as Red Hat, but we noticed that in terms of problems or alerts that we get for attacks or viruses, there is not anything on the Red Hat side. That is why we feel that it is more secure. It might be just the nature of Red Hat where all services and ports are off. It is not like Windows where everything is on, and you have to turn it on. I was having a conversation with one of the gentlemen who is also attending the Red Hat conference, and I got to know that there are built-in NIST features with Red Hat that we could turn on, so we do not have to try to figure out how to harden our system.

The testing of the updates or the packages of the kernel is valuable because I used to be a part of the Fedora project. I know it is all vetted out before it gets to production, but a majority of it is the support and the relationships I have with the Red Hat employees assigned to our account.

As they move over to newer versions, certain things change, which is expected as the technology matures or new things come out, but what really surprises me are the features that are there in the cloud, such as Red Hat Insights. They are not there on-prem. There are a lot of things on the cloud portal that I did not notice before, and I was surprised because we were unaware of them. Red Hat is doing a lot of investment in that sense.

The knowledge base offered by Red Hat Enterprise Linux is good. It is easy to parse through all of the knowledge base. I do not know if Windows does it because I have not looked at it, but in Red Hat's knowledge base, there are a lot of things. They fast-track a lot of things in their knowledge base, even when they are not yet official. Especially with the tie-in with Bugzilla, even though it is not a true KB, we can see and follow if other people in the world are hitting a certain problem or something similar to what we are experiencing. I like that.

It would be great to have an overview of how various Red Hat products work together. They can show how to tie all those pieces together and how to have the products that we work together for our day-to-day processes.

I started with the company around 2012, and they have been using it even before then. At that time, it was Red Hat Enterprise Linux 5, and now, we are up to Red Hat Enterprise Linux 9.

In 10 or 11 years of using Red Hat solutions, I have opened only one or two support tickets. It probably was something during a patch and during Satellite 5 to Satellite 6 migration. I would rate them a 10 out of 10.

Positive

In Linux, there are so many different flavors, but I am partial to Red Hat because I have been a part of the Fedora project. At our place, we have only two operating systems: Microsoft Windows and Red Hat Enterprise Linux. I know CentOS, but that is usually because the appliance from the vendor was set up using that. That is why we had a few instances of CentOS in the past, but nowadays, I do not see any other flavors of Linux.

For the majority of our use cases for Red Hat, we have on-prem deployments. There are some things that they are trying to spin up on AWS. I do not know if they are cloud-native apps or not, but I know our developers are now moving on to it.

I have been involved in the initial setup, upgrades, and migration of Red Hat Enterprise Linux. I did not have any problems while going from major OS versions. I always push new upgrades or homogeneous migrations, such as from version 6 to version 7 to version 8. There is probably an option to upgrade in place. Overall, with Red Hat OS, I have not seen many problems. A long time ago, when they went from Python 2 to Python 3, there were certain things we had to change in the script.

I know that Red Hat is moving to Wayland from X11, but I do not see any problems there. From Satellite 5 to 6, it was a bit hard in the beginning, but now, it is pretty self-explanatory. Overall, everything about which we had questions was very well documented.

In terms of our upgrade and/or migration plans to stay current, first, we look at the EOL and the roadmap of Red Hat because of security. We used to offer every single version before the said EOL happened, but now, we just do an n-minus-one. We try to maintain the newest and one level below version. SAP users are the biggest Red Hat Enterprise Linux users in our environment. They have a particular PAM and upgrade path that they have to do with Red Hat. We also wait to be certified to certain versions, but our main strategy is the newest and one major version down. We try to get everybody off the other versions.

Our provisioning is all done using VMware products. We have a vRealize automation, now called the Aria automation, to spin it up. Patching is done through Satellite. I do not do it, but when I watch them doing it, it seems it is just using remote SSH commands against the list of non-prod and prod servers. It is something simple. We do not seem to be doing anything complicated. I am wondering if there is a better way to do versioning control or patching and whatnot, but currently, it is very simple.

I am satisfied with the management experience not only in terms of patching but also the day zero to day one or day two stuff. We are interested in utilizing Ansible to eliminate human error and whatnot. During provisioning, we have Pearl scripts that we have to manually trigger. I know we can use Ansible for that, but it comes down to the cost of entry which is still very high. 

A lot of people are moving into the core count for licensing. We still have a few with one-to-one standard server licensing, but we are utilizing the virtualization host licensing. We license it based on the host, not based on VMs, which is cool. I was very happy that there was certain licensing with SAP to have access to SAP repos. Its cost was the same as the regular one, so I was happy about that.

The only pricing that bugs me right now is the Ansible pricing. We wanted to take a look at Ansible, but the biggest thing a year back with Ansible was that the management did not want to spend half a million on Ansible Tower. They wanted to see first if we would use it and not waste money. I do not know if things have changed now, but Ansible is probably still expensive. That is one of the routes that we want to go to. We will see if we can utilize Ansible Tower, so pricing-wise, that is the only thing that pops up. It is too expensive. The cost of entry seems quite high.

Overall, I do not see any issues with what we have spent on Red Hat. We also have learning subscriptions that we pay to Red Hat for the training, and I do not feel we have wasted any money.

Red Hat Enterprise Linux has built-in features, but we do not use them. It is one of the things about which I need to talk to our account manager. There are so many different ways to skin a cat. My department has so much money, so they bought everything, but a lot of the security features, such as SELinux, are disabled for us. We handle the firewall rules, access lists, and other things at another location rather than on the actual VM itself. It does not hurt to do it at multiple places, but operations-wise, it would be a nightmare, so we try not to do it. I know there are a lot of cool new things built in Red Hat, and that is something we should circle back and take a look at.

I have seen Red Hat Insights. I clicked on it one time when our account manager was showing us something. They have so many features in the cloud that we do not know we can use. Maybe it is wrong to assume, but the reason I do not look at Red Hat Insights is that a part of our patching is already included. We are not that strict about what we patch in terms of the versions. It is useful, but Red Hat emails us anyway. They tell about the severity of an issue. We do not look at Red Hat Insights. We see those emails and we see CVEs. If a package is installed and applicable to our VMs, we just use Satellite and patch that particular vulnerability. 

I have also tried the web console once. It looked interesting, but we do not have much use for it because a lot of our customers or application owners are server admins. About 99% of our Red Hat installs are all minimal installs. We do not have a GUI. There is just a terminal screen. Even though they could console in and do whatnot, it is all done via SSH.

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

Our memory-intensive applications run on Red Hat Enterprise Linux.

We opted for Red Hat Enterprise Linux for our workloads due to its stability and the comprehensive support provided.

Red Hat Enterprise Linux has enabled us to centralize our development to some degree.

We use it in containerization projects for workloads that need to run in private clouds, as it simplifies the process of shipping them as containers. The advantage of this approach is standardization, while the disadvantage is the necessity of shipping the container itself. Deploying containers on a platform like Kubernetes running on Red Hat Enterprise Linux may require some extra steps for scalability, but it is not a significant obstacle.

I appreciate that Red Hat Enterprise Linux, as a foundation for hybrid cloud deployments, is a commercial solution with reliable support.

Red Hat Enterprise Linux has performed well for our business critical applications.

We extensively use Red Hat Enterprise Linux's built-in security features because they are excellent.

Red Hat Insights has significantly helped us reduce risk in our environment by allowing us to identify which CVEs are impacting our systems.

Red Hat Enterprise Linux contributes to business continuity and compliance efforts by simplifying OS migration. Its generational upgrade path allows for easy transitions between versions, streamlining the process and reducing potential disruptions.

The time saved during audits and the ability to map CVEs using Red Hat Insight are valuable security benefits.

It helps avoid emergencies stemming from security issues, non-compliant settings, or unpatched systems.

Red Hat Insights provides the tools for proactive environment management. For example, it simplifies patch verification by confirming the desired automatic patching functioned correctly in one fleet, suggesting its likely success in the next. This clear visibility makes it easy to monitor ongoing operations.

Red Hat's portfolio helps lower the total cost of ownership for our enterprise landscape by providing reliable documentation that simplifies troubleshooting and reduces the need to resolve issues from scratch. 

Red Hat Insights provides good visibility and proactive management of our environment.

The primary issues are related to integration. Red Hat Insights utilizes several APIs that lack proper communication, resulting in inconsistent results.

I have been using Red Hat Enterprise Linux for about four years.

Red Hat Enterprise Linux itself doesn't have issues. It performs well for our business-critical applications.

Red Hat Enterprise Linux scales quite well, allowing us to adapt as needs change.

While the support is generally good, prompt attention often requires escalating issues or marking them as high importance.

Positive

Red Hat Enterprise Linux saves time with good documentation and other benefits.

The licensing is a bit odd because we need to procure the licenses from a third party. We prefer a pay-as-you-go model with monthly increments instead of buying licenses in bulk that expire in a year.

I would rate Red Hat Enterprise Linux an eight out of ten. While it has occasional bugs and software flakiness, updates are regularly released to address these issues.

To ensure your operations are compatible across different operating systems, prioritize OS agnosticism. Unless modifying the OS is a core function, consider a commercial solution like Red Hat. Although cost-effective, Red Hat may not be suitable for all companies.

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.

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.

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.

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

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

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

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.

Positive

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.

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

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.

In my latest job, I was working with microservices where the decision was made to use Red Hat Enterprise Linux (RHEL) for its core functionalities. I played a role in setting up the OS and was responsible for the initial installation, defining pods, and network configurations.

Red Hat Enterprise Linux (RHEL) offered robust support and stability, providing full alignment with manufacturing hardware which ensured the drivers and other infrastructure were highly compatible.

The support and escalation process for Red Hat Enterprise Linux (RHEL) is excellent. It offers more stability compared to other distributions like SUSE. Red Hat's compatibility with manufacturing hardware ensures smooth operation. Their knowledge base is particularly useful for troubleshooting and training, and their built-in security and compliance features simplify risk reduction. It is a mature and improved platform for corporate functionalities.

The performance of Red Hat Enterprise Linux (RHEL) could be improved, especially under high load scenarios or when running applications involving AI. Providing support for AI in the knowledge base could be beneficial.

Red Hat Enterprise Linux (RHEL) is known for its decreased downtime and stable performance.

Red Hat Enterprise Linux (RHEL) allows for disaster recovery planning across different states to ensure synchronized performance.

Customer support for Red Hat Enterprise Linux (RHEL) is rated as a ten out of ten. From the beginning, their support has been excellent.

Positive

The setup was smoothly conducted. The feedback received indicated that the installation was seamless and without interruptions.

I was responsible for the initial configuration and setup of Red Hat Enterprise Linux (RHEL), working closely with other teams.

Though a bit expensive compared to competitors, Red Hat Enterprise Linux (RHEL) is still recommended because it works effectively and delivers value for its pricing.

The differences between Red Hat and SUSE, or Red Hat and Ubuntu, are that Red Hat is more mature and has better corporate-oriented functionalities.

I rate Red Hat Enterprise Linux (RHEL) overall as a ten since it provides the necessary resources and support.

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

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

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

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

Our workflows have been seamless with our hybrid environment.

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

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

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

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

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable.

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

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

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

The upgrades were done in-house. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

I rate Red Hat Enterprise Linux nine out of 10.

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