Red Hat Enterprise Linux (RHEL) Reviews

We're the largest financial institution in Africa, and we use various operating systems and technologies to achieve typical financial service goals. In the past, we were an ION-centric shop. However, in the past decade, we've been increasingly leveraging Linux's agility compared to traditional Unix operating systems. 

Generally, we deploy by cloud, but we use RHEL on-premise in our data centers and prefer SaaS for infrastructure as a service. Our primary cloud providers are AWS and Azure, and we also use smaller third parties for niche environments.

RHEL is spread across virtually all elements of the institution, including headquarters and various locations on multiple continents. In my environment, it is part of a global trading settlement system. 

The rollout for this particular solution was probably about 250 users of the application running on the initial RHEL. We're a global bank, so the user base is much larger worldwide. Users include business and feature analysts, engineers, and project managers. Our infrastructure engineers were the ones pushing for a switch to RHEL, followed immediately by application engineers.

RHEL enabled us to move away from reliance on ION. We're free to choose the best-of-breed solution at any given time while keeping the cloud-agnostic infrastructure at the center of our deployments.

Our operational expenditures decreased, and RHEL made our teams much more flexible. With RHEL, we can have multiple copies of an OS without making annual plans to license and acquire.

The benefits were instant from my team's perspective. For example, we were immediately more flexible and able to scale rapidly. However, if you're looking at it from an executive point of view, the time to value depends mainly on the product and the scale of the endeavor. It might take a few years to reap a return. Ultimately, you will see the financial benefit, but that's somewhat difficult to quantify in the short term. 

I don't think that it's enabled us to centralize development, but it has perhaps increased the breadth of development possible on our applications. In that sense, more development can be centralized on the operating system, but that's more of a byproduct.

We outsource cyber security to other teams, so I can't comment in-depth on RHEL's security features, but I can say it enabled us to understand our security posture more efficiently. This wasn't always possible using an AIX or Solaris in a more centralized fashion. The feature set is maybe not as important as having a single pane of glass and a single configuration to apply across our systems and infrastructure.

RHEL made life a lot easier in terms of compliance because you can more accurately gauge yourself against industry benchmarks with the tools provided and identify your shortcomings. You can interrogate what you've done through research from multiple parties rather than just a single source of truth, which may not be true.

You can compile and run applications on any operating system, but RHEL's advantage is flexibility. It is more supported and supportable in the enterprise sense than Ubuntu or perhaps a smaller distro, but it's also flexible enough to easily transport from platform to platform: ISA to ISA,  production to development, and vice versa. That led me to embrace the switch to RHEL from other operating system variants.

RHEL offers more portability than any other OS flavor apart from perhaps Ubuntu Linux. As a large bank, we run on IBM's architecture. We run Power, Spark, and Oracle x86 across multiple environments. It lets us choose the right environment for the application, which is essential from an operational efficiency perspective. These days, we're all trying to cut heavy infrastructure and move to lightweight agile infrastructure. There isn't a better option in the production world than Red Hat.

There needs to be a broader understanding of the RHEL suite's nuances like how the versioning works and implementing it on various kinds of infrastructure in use across the development landscape. There needs to be more training and education. It's difficult when you have a roadmap to deal with, but it is possible. 

Large application vendors may not have certified RHEL, or they have certified an older version. Most of the large application vendors are unfamiliar with the versioning that RHEL introduced, which I strongly support. They will support a given sub-version up to a point, not realizing that the sub-versions are essentially additive. 

This can be a real frustration when you try to deploy modern infrastructure. It allows tremendous flexibility because we can try things out across the cloud, virtual, and physical, but that's not always where the issue is. It's a matter of educating the engineers and developers on our side or enterprise vendors on the other. 

The licensing could also be simplified. While it makes sense from a theoretical perspective, it's a challenge to explain to the procurement team. Those with some technical expertise can understand how our licensing model works. However, it's still tricky because Red Hat is so different from traditional operating systems. It's another barrier when I'm trying to deploy it in an enterprise environment.

In terms of feature requests, I would point out that our company tends not to operate on the bleeding edge for obvious reasons. We look at what has already been released to define our roadmaps. There's nothing in particular that I would say needs to be included. However, I would like to see Arm playing a more prominent role in the cloud infrastructure and enterprise physical data center spaces. Red Hat supports this, but I haven't seen a clear roadmap for how that support should evolve within the Red Hat operating system environment. 

I have used Red Hat Enterprise Linux for more than 10 years.

RHEL's stability is good. 

RHEL is highly scalable and we plan to increase usage. 

I wouldn't rate Red Hat support as less than eight out of ten because I can't think of anything negative to say. I can't think of a time when I haven't been able to get it. Also, because RHEL is global and Linux is open-source, you can typically get the support that you need through research forums and the knowledge base. It's seldom necessary to involve third-tier support within RHEL.

We still use other operating systems. We've used just about every solution you could name in conjunction with RHEL. We also deploy Ubuntu. In some cases, our application vendor requires us to stick with a given solution. Sometimes it's AIX or Solaris, but mostly we can override that and move to RHEL. Red Hat is now standard for most future enterprise deployments, and we run RHEL on mainframes too, but in a very limited fashion.

The setup was complicated only because the applications we were trying to run were not certified to run on RHEL. It was version 6.8, so we worked with major global vendors to add the certification for the versions we were trying to run. That was the complexity. The application always worked beautifully, and the performance was excellent. It wasn't a question of getting the development to work; obtaining an issue of getting certification for the platform, which is required for any financial institution.

From a development perspective, we proved the concept and ran a mirror of production and development to demonstrate the improvements in OpEx and performance. Getting it up and running in parallel was the key to getting it all to work correctly, and it was instrumental in convincing any dissenting voices of the value. 

The deployment took less than three months, but the certification took nine.
The team supporting the first application numbered around 50, and the small group involved in the initial switch had about eight people.

The entire application is run exclusively on RHEL, so the whole operation team is probably around 40 or 50 people. It's worth adding that our overall group runs about 20,000 servers, so it's challenging to say overall what the RHEL footprint is.

After deployment, RHEL requires maintenance to keep the solution up to date. Security requirements tend to be more prohibitive or less encouraging of change. It's a question of changing mindsets and explaining that something doesn't have to be legacy-tested to update. The security benefits of updating are more critical than testing to ensure the update hasn't introduced more flaws.

I don't have the data, but we have significantly reduced operational expenditures since switching to RHEL. It was a reduction of more than 10 percent. 

The licensing is tricky to understand. Enterprises want to be beyond reproach when it comes to licensing. We would rather over-license than under-license. However, that can be complicated with a high-performance development team who may need multiple operating system instances or want to experiment with spinning up many machines to see if something works or sticks. 

We don't necessarily need support for those. Our procurement team is confused if we need a license for an instance that was only up for 15 minutes on Thursday. We need to make sure that we always have sufficient licenses. That misunderstanding of how cloud development works can sometimes slow down development. It inhibits the growth and success of Red Hat Enterprise Linux globally. So more education around that would be beneficial or at least will provide more clarity.

RHEL's total cost of ownership is difficult to quantify, but it's almost irrelevant. In cases where you don't care, you can always use an open-source OS. In other cases, you need the support and certification that comes with something like RHEL. I do not believe RHEL has any competitors in our use case.

I rate Red Hat Enterprise Linux nine out of ten. My advice to prospective users is to try RHEL out and see if your application works. In the long run, the benefits will outweigh the time and effort spent migrating. The important thing is to ensure you run programs in parallel so you can accurately evaluate the benefits and make a case for switching.

Our business is primarily focused on software development. We are doing development and deployment using containers. We are mainly using Docker, but we might also adopt Podman later.

Our business logic is mainly for our own software development. We mainly have Java applications, Java containers, Tomcat, and Java frameworks. These solutions cater primarily to our business-level operations.

We are using Red Hat Enterprise Linux on-premises.

Red Hat Enterprise Linux gives us a standardized way of handling various tasks. Everything is the same in our environment.

It gives a standard procedure to do everything. It also gives standard APIs and a stable environment.

It works very well for our business-critical applications because of its stability and support. We have some kind of support in terms of the life cycle of the operating system.

Its long lifecycles, updates, support, and documentation help with business continuity and compliance. With reference architectures, we can straightaway get working solutions.

We can rely on security features like SELinux and run several workloads for WordPress and so on. We can rely on Red Hat.

We have used Red Hat Insights for certain things, and it has been helpful.

Stability, support, and life cycle management are valuable. We get fixes quickly. We can rely on them for features and so on. We can rely on their support. In the case of an issue, we can get somebody on the phone.

Red Hat could offer a containerized version of the operating system, potentially moving towards a more containerized ecosystem. 

More flexible tools for dealing with complex things like SELinux would also be beneficial. Its built-in security features are good, but they are quite complex to manage at an atomic level.

I have been using Red Hat Enterprise Linux for 25 years. We are mainly using Red Hat Enterprise Linux 9, but we also have Red Hat Enterprise Linux 7 and 8.

Red Hat Enterprise Linux is very stable. However, sometimes, there might be some load balancing issues leading to performance issues, so we have to figure out all those. Usually, Red Hat tools are helpful for that.

With automation, we have been able to handle scaling efficiently. We are using an internal cloud, which suits our needs without relying on OpenShift or VMware.

The support from Red Hat is very good. We have collaborated with Red Hat remotely and have been satisfied with the assistance provided for our customers' cases.

Positive

The pricing is suitable for midsize to large companies, though small enterprises might struggle. It is comparable to Windows licensing.

I would advise considering the lifecycle and support that Red Hat offers. They provide long-term support and have best practices for addressing vulnerabilities and attack vectors.

I would rate Red Hat Enterprise Linux an eight out of ten.

We use Red Hat Enterprise Linux to provide a Platform as a Service for our customers in the cloud, upon which we have built additional software. This encompasses Red Hat and Synthos, including all Red Hat derivatives.

We also use it for our security-related applications primarily due to the robust enterprise support and comprehensive security features it offers.

Using Red Hat Enterprise Linux for containerized workloads has increased security, stability, and trust, ultimately simplifying our work.

Red Hat Enterprise Linux enhances the reliability and security of our hybrid cloud environment.

Red Hat Enterprise Linux performs well for our business critical applications.

We chose Red Hat Enterprise Linux for our environment due to its robust built-in security features, including proactive security fixes and an enterprise-class operating system with reliable support services that enhance security and reduce risk. Furthermore, the secure base OS Docker image strengthens our environment's overall security posture.

Red Hat Enterprise Linux helps reduce our total cost of ownership due to its security, stability, and enterprise support. The tightly integrated Red Hat portfolio simplifies working with their products and achieving the desired return on investment.

The most valuable aspects of Red Hat Enterprise Linux are the security and stability it provides.

I encountered an issue updating the time zone for one of my assigned countries due to a daylight-saving time change. Although we collaborated with Red Hat to build a package that addressed the issue, it wasn't delivered promptly, necessitating manual workarounds to resolve the problem.

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

Red Hat Enterprise Linux is exceptionally stable, minimizing the risk of outages or issues stemming from the operating system itself. This reliability allows it to run seamlessly in the background, freeing administrators from constantly addressing kernel bugs or faults in core system applications, ultimately saving significant time and manpower.

Red Hat Enterprise Linux offers flexibility to scale as required.

My experiences with Red Hat technical support have been mostly positive, though I've encountered some issues occasionally.

Positive

Red Hat Enterprise Linux is suitably priced with various support tiers to match organizational needs and environments.

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

When considering a Linux operating system, the choice depends on the intended use. For enterprise environments requiring dedicated support, Red Hat Enterprise Linux is recommended. Smaller projects or testing environments may start with a similar option and transition to Red Hat as the business grows.

We are doing image building. Our team focuses on the image of the platform and presenting it in a secure way for everybody to consume.

My organization had already been using it before I started, so I am not sure what benefits they got from Red Hat Enterprise Linux. They were already a Red Hat shop when I started.

We do not utilize Red Hat Insights as much as we would like, but we know that it is there. It provides the data, and we can act on that data, but we do not use Red Hat Insights the way we should. However, it does tell us when things are critical and need to be patched. If something is on there and it is critical, we can at least see that it is patched. The alerts and targeted guidance from Red Hat Insights have not affected our uptime so far.

It is open source. Most of the features are already there for you. They make solutions for challenges that we do not even think about sometimes, but we may consume them later.

I have not put in many feature requests. They have mainly been around small things such as monitoring with Ceph. I cannot remember the name, but monitoring was needed for a specific function. It was a pretty important function, but there was no monitoring set up. It took some extra effort. That was the only feature I asked for. I asked them if they could set up a monitor to make sure that the system was healthy or working correctly.

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

Its stability is fine. I have not seen too many issues with stability.

Its scalability is great. We can scale up or down.

I do not have any issues with the customer service or tech support. It is good. I would rate them a ten out of ten because they can usually resolve anything.

Positive

The deployment of Red Hat Enterprise Linux is pretty simple. There are not so many issues.

We are using it on the cloud and on-prem. We are trying to get to Azure. We are not using it in a hybrid cloud environment. I know we are setting up OpenShift in Azure and on-prem.

We have been using TerraForm to create images and Ansible to make sure everything is fine. We have some things on Azure, but we are trying to make it easier for people to consume Azure. We are trying to get that automation together so that it is a lot easier if anybody wants to spin anything up in Azure. They have a container to use that is secure. All of our business tools are on it.

We just use Red Hat. We do not use any integrator or consultant.

Our team does not use a lot of containerization, but we probably will be doing that soon with VMware changes. We are trying to get more of the monolithic stuff down to containerized workloads. We will hopefully see some return on investment after we get our VMware stuff out and get more things containerized. We are working with the OpenShift team, and we will be able to see some ROI.

That has been mostly handled by Red Hat. As we are a Red Hat shop, we have a lot of people around that already.

We do not use the security features of Red Hat Enterprise Linux. There are so many scanners out there. We do not use what is on Red Hat Enterprise Linux, but we do set it up. They are at least available to consume. We do not use them because we have so many security compliance tools. As a bank, we have to use those for auditing and other things like that.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to get something that is close to Red Hat. Red Hat is killing a lot of the downstream stuff. All my Linux is Rocky Linux because it is based on Red Hat Enterprise Linux. I would suggest getting something that is close to Red Hat Enterprise Linux so that if they or their company does not want to go for Red Hat, they would still have the same tooling and the same infrastructure.

I would rate Red Hat Enterprise Linux a ten out of ten. I have not seen a lot of issues with Red Hat Enterprise Linux. I am overall satisfied with it.

I use the solution in my company mainly for the operation system of the core business applications.

My company has experienced benefits from the use of the product, especially considering the agility that the tool offers in terms of the time to market in different areas of business and because of its compatibility with most of the applications in the market.

The most valuable features of the solution are the stability and scalability.

I run Red Hat Enterprise Linux (RHEL) on a hybrid cloud deployment, and it has impacted our company's operations, but I would say that it has been quite simple to implement, especially considering the security, which has been a considerable piece of the infrastructure.

Red Hat Enterprise Linux (RHEL) has helped centralize development in our company. The applications run with Red Hat Enterprise Linux (RHEL), and it became the standard for the operating system for the applications.

My company uses Red Hat Enterprise Linux (RHEL) for containerization projects with OpenShift. This use of Red Hat Enterprise Linux (RHEL) has had an important impact on containerization, as it is a simple process. Owing to the simplicity, we always involve the solution's experts and get faster solutions.

The built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance are very important because our company is always aware of all these security issues that constantly happen.

Though the product has many features, the tool's virtualization area has certain shortcomings that require improvement. The product should also offer more containers and probably some financial services.

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

It is a very stable solution.

It is a quite easily scalable solution.

The technical support for the solution is very good. I rate the technical support a nine out of ten.

Positive

Before Red Hat Enterprise Linux (RHEL), my company used to use Windows. My company started to use Red Hat Enterprise Linux (RHEL) after we found that it offers more stability, sophistication, and security and serves as a standard for many products.

The product's initial deployment phase was easy and quick.

My company did follow some strategy to deploy the product, and we also had the support from the vendor.

The solution is deployed on the cloud and on-premises models.

My company sought the help of a system integrator during the implementation phase of the solution.

In terms of ROI, I see that the tool offers stability, performance, agility, and resilience.

If I describe my experience with the product's price, I would say that we have to live with it for now.

My company evaluated other Linux products, such as SUSE Linux Enterprise Server (SLES), against Red Hat Enterprise Linux (RHEL).

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux since it is a tool with more market experience and offers more documentation and support from the vendor, which is not easy to acquire when it comes to open-source software.

Red Hat's portfolio has affected the total cost of ownership across our enterprise landscape by around 10 to 20 percent.

My company has the product in two data centers, but the production happens only in one. Mostly, my company uses the cloud services offered by Azure.

I rate the tool a nine or ten out of ten.

I use the solution in my company for regular servers with databases, load balancers, Apache, and so on.

The benefits of using the product revolve around the fact that it has made it easier to automate everything on it, which includes automating servers and so on.

The most valuable feature of the solution is that it is an upcoming, more stable product, like Oracle OS. The tool has everything that IBM Red Hat Redbooks has.

In terms of how I would assess the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) for keeping our organization agile and flexible, I would say that since my company is a service provider, we get the containers from the customers, which we don't use for our own selves, but we use Red Hat Universal Base Images (UBI) 9 for some things like to to get our own containers and so on.

My company has not tried to use Red Hat Enterprise Linux (RHEL) 9 since we are still using Red Hat Enterprise Linux (RHEL) 8. In the future, I am expecting to see Podman 5.0 released for RHEL 9.

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

It is a nice and stable solution. Some problems may occur with the product if you don't patch it after a year or two.

There are no problems with the scalability of the product, as it works fine.

Previously, my company used to use a simple version of RHEL and other tools depending on the needs of our company's customers.

Regarding my experience related to the deployment process, I would say that everything is automated now. You just fill out the survey, and then you just deploy the tool. The product's deployment phase is easy.

The solution is deployed on an on-premises model.

The team members can deploy the solution in my company.

If the customer wants to pay for the support and so on, then we can go for Red Hat Enterprise Linux (RHEL). Otherwise, one can go for any other open-source platform. With Red Hat Enterprise Linux (RHEL), you get the latest on everything. If you are running Oracle Linux, it gets hard to find some patches. It is easy to find new things like Podman or Red Hat Subscription-Manager, especially if you want to run something on Oracle OS, then you need to compile the patches yourself.

The product has helped centralize development in our company. In our company, we are mostly automating all the server installations on Red Hat template by filling in IP addresses with Postman.

We don't use the built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance since they are only available in Red Hat Enterprise Linux (RHEL) 9.

To a colleague who is looking at open-source cloud-based operating systems for Linux other than Red Hat Enterprise Linux (RHEL), I would say that previously people preferred CentOS until Red Hat stripped it apart. At the moment, it is like, if you want an RHEL-based tool, it is either Rocky Linux or Oracle OS because I think Fedora is too lenient, while CentOS is somewhere in the middle.

I would be spending the same amount of time on some other solution if I was not using Red Hat Enterprise Linux (RHEL) since everything is automated now, and in such a case, it will just be another image you use on some other product.

My company uses Ansible as a part of the deployment model.

The product is easy to use, and you can get support whenever you want. The solution also   the latest packages, which include Red Hat Subscription-Manager, Podman, Linux, and other such functionalities.

I rate the tool a nine out of ten.

I utilize Ansible to harden Red Hat devices across a multitude of disconnected environments.

One benefit of using Red Hat Enterprise Linux is that a lot of backend applications run natively on Red Hat Enterprise Linux as opposed to a Windows-based option. We are a partner with Red Hat. It essentially allows us to do a lot of our infrastructure stand-up and development.

It has enabled our team to centralize development. We have been able to centralize our automation, playbooks, and different collections we use within Ansible to create a centralized code base. We can use that to configure different types of systems with different requirements from different customers. Having a common platform across the entire enterprise has been very helpful.

We are using Red Hat Enterprise Linux very limitedly for containerization projects. It makes things very seamless. If we get a new developer, we can set up a brand new instance of a container for a dev environment or a test environment. It allows different developers to always have the same starting points with containers.

In terms of security features for risk reduction, there are SELinux and FIPS. Also, when you build a Red Hat Enterprise Linux machine, you can stick it right out of the box. It is very helpful. It is very good, especially for programmers and users who do not know anything about cybersecurity. It takes you 85% to 90% of the way. It has been very helpful and good.

The right commonality across the business or enterprise is always very hard to do, especially when different networks and different customers have different requirements. Being able to at least have continuity between those different environments has been helpful. If you have a system admin at a location and you put him or her at a different location, they at least can expect the same type of infrastructure.

When it comes to compliance, it takes you 85% to 90% of the way there. Different networks require different things. Some cannot implement specific standards for whatever reasons, but being able to utilize and leverage Red Hat Ansible to configure that and make sure those changes are made across the entire network has been very helpful.

Portability depends on the circumstances. Some things are more portable than others, such as containers. We utilize Ansible Core very extensively, but other things, such as AAP, are not necessarily as portable because some of our smaller environments do not have the bandwidth or the actual resources to support a big product like that.

In Red Hat Enterprise Linux, I am a big fan of the command line. I like the data manipulation and different commands that we can use. I use Ansible extensively to configure systems.

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

It is very stable.

It is easily scalable with the solutions and the options they have.

Their support is very good. They are very helpful. Some of them are more experienced in handling the niche problems that we have.

I would rate their customer support a nine out of ten because there is always room for improvement, but it has always been very good.

Positive

We have used Ubuntu and other Linux operating systems in the past. However, since I have been with the company, we have used Red Hat Enterprise Linux almost exclusively.

The deployment model depends on the environment. Some are using VMs. Some use containers, and some use bare-metal installations. It depends on what a particular program needs. I support small environments that are on-prem.

It is fairly straightforward to deploy different Red Hat boxes. I was just helping out a sysadmin the other day who had not done it before. It was super straightforward and super easy to deploy.

We deploy it on our own. 

The return on investment for us and our team is specifically automation. We are able to invest time on the frontend to create different automation playbooks, and we are able to push that out to not only a singular network but also to multiple networks and multiple different configurations. It takes a little bit in the beginning, but there are huge time savings in the end.

If a security colleague is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would be interested to understand what that colleague's objectives are and why they would consider something other than Red Hat Enterprise Linux. If it is something that fits their particular use case more, they can obviously go with that. Red Hat Enterprise Linux is a standard solution for Linux. If any colleague wants to go for another solution, I have to understand why. I would have to understand what Red Hat Enterprise Linux is not able to provide. However, this has not happened to me.

I would rate Red Hat Enterprise Linux a full ten out of ten.

We primarily use it for enterprise software, databases, and some custom applications.

We have a stable base to deploy applications. We need a minimal amount of effort to troubleshoot problems with the applications that are related to the OS.

We are using Red Hat Enterprise Linux in the cloud, in the on-prem data center, and at the edge. We are also using Red Hat Enterprise Linux in a hybrid cloud environment. It has had a positive impact. It is straightforward to deploy. There was no bottleneck.

Red Hat Enterprise Linux has enabled us to centralize development. The stable base that each developer can rely on is great. The consistent ecosystem of the repository makes it easy to rely on.

We use Red Hat Enterprise Linux for containerization projects. Red Hat Enterprise Linux is quick to containerize, so when it started becoming mainstream, it was easier for us to sell to upper management to start doing more containerization.

There has been a positive impact in terms of the portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. It is very portable. I do not have any issues with different ecosystems in relation to how Red Hat Enterprise Linux runs containers.

Our cost of ownership is not high. They are not very expensive. We are never surprised.

The repository ecosystem is valuable. 

I would probably focus more on a rolling release schedule. Instead of a long-term operating support of ten years, I would just have one release and keep rolling it.

In terms of security features, overall, it is lacking cohesion. There are a lot of different options, and it is hard to choose the ones that best fit our business needs without a lot of investigative work.

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

It is very stable.

It is scalable.

It takes a little bit to get to the true answer. I know there is a lot of triaging. I am sure we can improve on our end. When we open tickets, we can provide more information. There could be a way to get faster answers from Red Hat support, and we might not be providing the most upfront information needed for the ticket. I would rate their support a ten out of ten.

Positive

We were not using any other solution previously.

I know of only one other player, and that is Ubuntu. There is also OpenSUSE, but I have not yet seen that personally in my career.

We have cloud and on-prem deployments. We have the AWS cloud.

On AWS, we had an EC2 instance. I clicked, and it was online. For the initial deployment, we just used the Amazon Web UI, and now, we use Ansible for deployment.

We have seen an ROI. It is fairly easy to deploy. We do not have too many issues with setting up a new environment in relation to the operating system. The bottlenecks are more related to the hardware or even setting up the cloud.

When I came in, Red Hat Enterprise Linux was already being used. It has always been there.

We have not yet fully leveraged Red Hat Insights. We are working on that. It might help with cohesion and security.

I would rate Red Hat Enterprise Linux a ten out of ten. It is reliable for deploying applications. It has a lot of different features. I can find solutions to all my problems, and the industry support is there.

We are a brokerage firm. We use Red Hat Enterprise Linux for trading purposes. We develop our applications on it.

By implementing Red Hat Enterprise Linux, we wanted a stable server and OS.

There is an in-built feature for shell scripting, so we can automate things that have to run on time in production. We created a script for the setup and configuration of certain things, such as disabling the firewall, network manager, and other things.

I am able to handle some of the daily issues automatically by using batch scripting and cron scheduler. I have also been able to debug some of the issues with the help of logs.

It is open source. We can customize it as per our requirements. We can change or optimize it as per our requirements.

Their support needs improvement. It should be faster for priority tickets.

Some of the tools can be improved and made user-friendly. The OpenStack and OpenShift tools can be better.

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

It is stable. I would rate it a 9 out of 10 for stability.

It is scalable. I would rate it a 9 out of 10 for scalability.

We have about 100 servers, and we have about four people working in the IT department.

Their support needs to improve. If we create a priority ticket for Red Hat, they revert within four hours. They should respond within half an hour so that the issue can be resolved as soon as possible in the real or live environment, and the company has less downtime.

We are using Red Hat Enterprise Linux and Windows operating systems.

Upgrades and migrations are easy with Red Hat Enterprise Linux. We are currently working on upgrades from RHEL 7 to RHEL 9.

We use open source. We only have a subscription for support.

For security purposes, we use the SSH key algorithm, MD5, and SHA256. We have set up a firewall in our network, and all servers are password-based. We also block some common ports that are open when we install the OS. We also have monitoring tools to ensure uptime.

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

We have almost thirteen servers. There are SaaS applications installed on this server. We leverage Java and the functionality during installation. We install it on the platform and configure it there. Some are custom applications. Our database is also in the Red Hat Linux environment. 

The solution offers users easy access. It's very simple to have and use, from an admin perspective. 

The offering provides me with all I need to serve the operation in terms of usage and capabilities. 

The general user commands are good. They are helpful for starting and stopping applications and restarting and editing files. The maintenance of user-level processes is easy. 

We're not using it in a graphical environment, we're only using command line mode. There may be a lot of features, however, I don't use everything since I don't need to. 

There are millions of commands you can use, although we use only five or ten.

Likely the solution has helped our organization save on costs. I'm not sure by how much, as I don't have visibility into that aspect.

It's very easy to use across physical, virtual, and cloud infrastructure. Specifically, on the cloud side, I have noted it's quite easy. Also, on a virtual machine, you can create a cloud version of your infrastructure in a minute. 

For my work, the solution is not missing any features. We;re only using the command line and that is enough for us. 

Maybe they need to make it easier to apply patches from different resources. That said, at my level of usage, I never have to apply patches. 

I've used the solution for almost ten years. 

It's a stable product.

While I'm maintaining 30 servers, there are hundreds of servers in use. 

The scalability is good. We are able to increase capacity and functionality based on our demands. 

I'm not sure if the company has plans to increase usage in the future.

I don't directly deal with technical support. I might send a ticket to my side, and if they have to, they would be the ones to reach out to Red Hat. 

We used Oracle Linux before we moved over to Red Hat Linux. We likely switched due to costs and licensing. We also use Windows extensively. Since we used the same architecture, we didn't need to use any third-party applications.

As an admin, I was not involved in the setup process. 

If there is any maintenance needed, we get support from the Red Hat team.  If anything comes up on the operating side, our team will take care of it. 

I'm only using this solution as an admin and, therefore, have no visibility on costs. 

We did not evaluate other options before choosing this solution.

I'm an end-user of the solution. I had admin-level access to the product.

Red Hat Enterprise Linux does not enable us to achieve security standard certification.

I'd rate the solution ten out of ten.