Red Hat Enterprise Linux (RHEL) Reviews

I use Red Hat Enterprise Linux for running applications and databases on them.

It has a smaller footprint, so it uses less storage. The product is optimized for resource utilization. Patching is very streamlined for the operating system compared to Windows. We prefer using Red Hat Enterprise Linux over Windows whenever we can. Patching is much easier, and it seems more mature. When we apply a patch, we're less likely to have problems after. It's more stable.

All resources should be available on the website.

I have been using the solution for about three years.

I rate the support a nine or nine and a half out of ten. I am not rating support a ten out of ten because if we were able to receive all of the resources that we could from the website, then we wouldn't need to reach out and contact support. It's a learning curve.

Positive

Previously, we used CentOS. We have also used Oracle Linux, which is based on Red Hat Enterprise Linux's kernel. Now, we're strictly trying to use Red Hat Enterprise Linux. We switched to Red Hat Enterprise Linux because it provides great support.

The products are pretty similar. A lot of the implementations, commands, and updates are very similar. Overall, we've had a more positive experience using Red Hat Enterprise Linux. We have a basic build routine when building new servers, updating, and installing add-ons. When we run those scripts, it seems like it's so much more streamlined with Red Hat Enterprise Linux. It could be because we're converting everything to Red Hat Enterprise Linux.

We're exploring more automation features. Three years is still relatively new for an operating system for our department. As we explore more automation-rich features and tools and subsets of tools, we'll be able to utilize the solution better. Red Hat Enterprise Linux may be very good at it, but our knowledge and experience are still growing. We need to take a deeper dive into implementing automation.

We use Red Hat Enterprise Linux with Microsoft Azure. We did not have concerns about using Red Hat Enterprise Linux in the cloud because we had spoken to other customers of Azure that had been running Red Hat Enterprise Linux. We can install Red Hat Enterprise Linux on our own, or we can use the custom-built Red Hat Enterprise Linux images available through Azure. It makes the deployment of a server much quicker and more efficient.

We have been migrating some workloads and applications from on-premise to Azure. However, we do not constantly move workloads back and forth between Azure. It's more of a one-way migration. We're trying to be less on-premise and more in the cloud. There's definitely a learning curve for the migration. There were some hiccups with learning how to do the migrations. We've done a handful of migrations so far, and each time, we learn from our previous experiences and mistakes. We use our lessons learned and have a better experience each time that we do a migration. It's getting smoother each time.

The knowledge base offered by the product is really good. There are a lot of resources available on the website. We have a direct contact for support, which we utilize on a regular basis. We have enterprise licenses, so we pay for support. We get support whenever we need it. I have been involved in Red Hat Enterprise Linux upgrades. It's pretty straightforward. We just convert from different Linux operating systems to Red Hat Enterprise Linux. My technical team has used Red Hat Insights, Image Builder, and Convert2RHEL.

We keep pretty close to the most current versions of Red Hat Enterprise Linux. There are many different versions of the product. Version 9 is the most current. We're trying to stay up with at least one or two versions close to the most current version to stay updated. We don't want to get to a version that would be at the end of its life.

The solution has helped us streamline and optimize our infrastructure for any applications or databases we run on a Linux operating system. They help us save on our physical resources because they're less demanding. Therefore, we don't have to spend as much money on a server that has a lot of CPU and a lot of memory. We can fit many more VMs on a single physical virtualization host because it's optimized. The support is great, and we can find quite a bit of information either directly through the Red Hat website or through the Red Hat community. We're able to do research on our own and find most of the information that we need. If we can't, support will assist us.

Overall, I rate the tool a ten out of ten.

We have a lot of Oracle databases, Tomcat, and Java microservices running on Red Hat Enterprise Linux.

A lot of our applications are like Java microservices. Deploying them on a Unix platform is so much easier. It's open-sourced and provides a lot of compatibility. It makes it easier for us to roll out applications. It is compatible with most Java microservices applications.

We like that Red Hat Enterprise Linux is a vendor-supported product. When we have problems, we just call Red Hat Enterprise Linux for support. The product employs a lot of automation tools to manage its OS. We love using Red Hat Satellite. We have close to 5000 servers. Managing individual servers would be a nightmare.

Red Hat Ansible Automation Platform and Red Hat Satellite help us automate our repetitive tasks. Every flavor of Linux distribution has its own specialties. The product offers a lot of integration within the Red Hat products suite. We use Red Hat products mostly, so it works for us.

The vendor keeps rolling out many packets, which complicates our job. We keep patching our servers. CVEs come out all the time. However, having a solid and secure OS will make our life much easier.

I have been using Red Hat Enterprise Linux since 2004.

I never had any problem with support. I didn't have any issues that I did not get a resolution for. Sometimes, it takes a little bit of time, but eventually, it gets resolved.

Positive

I was using AIX, which is also an IBM product. IBM bought Red Hat Enterprise Linux. AIX was more expensive and required IBM System p. Moving to Red Hat Enterprise Linux was much easier because it is a lot more compatible with the regular hardware like HP and Dell that we buy on the market.

I have seen an improvement in our deployment. When we have applications running on Windows, it takes longer to get them set up and provisioned, and the security is different compared to Red Hat.

The pricing could be better. The tool is getting expensive. Before, we could license only the hypervisor where Red Hat Enterprise Linux is running. Now, if a customer has a 12-node hypervisor, Red Hat Enterprise Linux forces customers to license all 12, even though they use only six.

We evaluated SUSE. At that time, SUSE did not have good support. We needed good support worldwide.

We use AWS and Microsoft Azure as our cloud providers. We don't use the off-the-shelf product that we get from the cloud. We build around it because we have a standard template. When we deploy our solution in the cloud, all the security features we need are already within the OS, as opposed to using the cloud OS and applying all the changes we need. It's easier to get our template to the cloud and use it.

The licensing for the cloud environment is totally different than the on-premise one. We use the Virtual Datacenter license on-premises. I don't see any difference because Red Hat Enterprise Linux still supports it, whether on-premise or on the cloud.

Red Hat Enterprise Linux knows its product. Whenever I have an issue, an engineer gets assigned to me. I can always escalate if needed. We're not using every host that we license. We ensure that we can fail over smoothly on every single hypervisor. It's fair to license them. We're not using it, but we're still paying for it. I do not like it, but it is a business cost.

We migrate workloads to the cloud. I never upgrade an OS. I usually replace the old OS with a new OS and migrate the application. I use the OS versions 7, 8, and 9. The migration is pretty straightforward. AWS and Azure have a tool that we can use to integrate with our environment. It's a lift and shift. We grab the VM from our on-premise hypervisors and move it to the cloud.

We use Red Hat Ansible Automation Platform mostly for patching and upgrading to the next revisions. We don't upgrade from one OS to another. We build on a new OS and get all the applications running there. Once the application is running, we move all the workload from the old OS to the new OS. There's no impact on the existing system.

I don't do the day-to-day patching because we have a managed service. However, it does create interruption. When we do a patch, we have to reboot, especially when there's a kernel update. It causes an outage. I have used Red Hat Insights. It gives us insight into what's happening on every single Red Hat VM that we have. It tells us if it's behind or has some performance bottlenecks. It gives us visibility on the health of the whole OS.

People who are looking into the product must get a good account manager. We must have a good account manager who we can always contact and who gives us all the updates that we need. They keep us in the loop on what is happening in the Red Hat world. We are satisfied with the product.

Overall, I rate the tool a ten out of ten.

Our organization uses the solution as a scientific workstation for forecasting, data collection, data presentation, and delivery of products in the form of bulletins or images to the general public. 

We have five to ten scientists who work on installations at any given time. We need a pretty powerful but flexible cluster system to operate and develop applications for general maintenance. 

We have over one hundred sites so we need something that is efficient. We use Smart Management to distribute packages and Ansible for some of our remote, repeatable management tasks.

The solution is very good and the best choice for us because it is quite versatile and familiar to staff. It has its own quirks from time to time, but by and large, the solution has been very reliable and useful for our purposes.

We operate in a high-security environment and the solution's security profiles meet our standards.

The solution is very versatile with an intuitive, easy-to-use interface and a wealth of available applications.

The flexible and extensive system makes it easy to cluster, check redundancies, and perform data backups. 

The solution's open source aspect is appealing because it invites collaboration. 

The operating system might not be able to handle big scientific problems which require a highly parallel system and symmetric multi-processor to run logic streams simultaneously. 

I have been using the solution for twelve years.

I have used Linux since the 1990s. I started with Unix in 1979 as a student at Hopkins. I liked that Unix treated everything as a file and had a very consistent interface. 

Linux lived up to the spirit of Unix because of its core operating system that is modular with the basics and supports additional functionality as plugins. 

The solution is very stable. 

The solution is scalable. 

Technical support is responsive and very good. I rate support an eight out of ten. 

Positive

Ten years ago, I used VMS and AIX depending on the project. 

My job right now is on analytics-based systems so I use the solution. The organization has used it for twenty years. 

The setup was completed twenty years ago so I do not have details. 

The solution is easy to troubleshoot if you have familiarity with Unix systems. Any system of this scale will require maintenance but it is relatively straightforward. 

I rate the solution an eight out of ten. 

I use Red Hat Enterprise Linux to manage pre-configured web servers, troubleshooting issues such as "524 errors" and missing configurations in EMV files. Furthermore, I constructed an on-premises Kubernetes cluster on Red Hat Enterprise Linux 9 and configured it for ELK.

The Red Hat Enterprise Linux knowledge base is excellent. When I encountered an error, they were able to quickly identify the issue and guide me through the necessary steps to resolve it.

The Red Hat Enterprise Linux Web Console functioned properly throughout the lab courses.

Red Hat Enterprise Linux is excellent for commercial use and enterprise tools. It's best to use Red Hat for enterprises because it provides robust support available twenty-four by seven, which I have experienced.

To start working with Red Hat Linux was straightforward and user-friendly. I didn't encounter any complexities.

The most valuable feature of Red Hat Enterprise Linux is its comprehensive ecosystem. The detailed documentation eliminates the need to consult external resources, and the knowledgeable support team provides expert assistance with both technical issues and site navigation.

Improvement is needed for supporting Kubernetes clusters because it is less supported by Red Hat according to my experience. There are also some gaps in documentation which affect configuring Kubernetes clusters.

I have been using Red Hat Enterprise Linux for four to six months.

I have not faced any downtime or stability issues with Red Hat Enterprise Linux.

I have not encountered any scalability issues with Red Hat Enterprise Linux.

The technical support is excellent. They promptly addressed my concerns regarding permission issues when I contacted them.

Positive

I used CentOS for non-enterprise purposes but switched to Red Hat for enterprise applications due to its superior support and stability. However, Ubuntu is generally preferred for Kubernetes deployments.

Red Hat Enterprise Linux is nine out of ten.

Red Hat Enterprise Linux does not require maintenance.

Our mid-size organization has between 20 and 50 employees, including our DevOps team, who use Red Hat Enterprise Linux.

I recommend Red Hat Enterprise Linux due to its support and strategy.

In our environment, we primarily use Red Hat Enterprise Linux (RHEL) for managing customer environments and our own. The customer environments are mostly Apache web servers. Some customers have databases, like Postgres, running on Red Hat Enterprise Linux. Others run native Docker on it to manage application dependencies. 

We run containerization projects in the OpenShift environment based on Red Hat Enterprise Linux OS because that's more suitable for containerized workloads. You can do some machines on Red Hat Enterprise Linux, but not all of them. Your worker nodes need to be Red Hat CoreOS, but your master nodes can be Red Hat Enterprise Linux.

I was more experienced with other Linux distributions and Docker. It's open source, so you can fetch Docker and run it, but they don't have support if you have questions or if something isn't working as expected. Podman is similar to Docker. I don't primarily use Red Hat Enterprise Linux for containerization, but I set something up in Podman on Red Hat Enterprise Linux. It isn't used that much. Tinkering and development are the main reasons you would use Podman on a single centralized Red Hat Enterprise Linux machine. If you want to orchestrate on a larger scale, you use OpenShift.

Red Hat Enterprise Linux has made significant contributions to our business continuity and compliance efforts. If a critical vulnerability is spotted in the wild, Red Hat fixes it most of the time. It's usually within a day if it's a zero-day vulnerability. Log4J was a bit more difficult because it was not a single package, but it was mostly shipped with other products. It's hard to analyze which application is vulnerable and whatnot. The solution lets us centralize development. We use Ansible to orchestrate the tooling deployment or to fetch a lot of information. 

Red Hat always clearly describes the vulnerability on its security pages as a CVE score. You can fix errors by patching or mitigating them. If the patch hasn't been released, you can mitigate it to prevent the vulnerability from being exploited. Red Hat Enterprise Linux helps us guide the data and ensure it is correctly placed. I was monitoring it daily, but it was a bit too frequently. Now, we get vulnerability notifications weekly or monthly about a vulnerability or exploit that's been discovered. I also look on Reddit directly to see if there's a fix or a mitigation we can implement.

Sometimes, when upgrading or migrating systems, there are differences in the repositories of the versions that aren't one-to-one replaceable. For example, there are significant differences in the repositories from version 7 to 8. We needed to upgrade Red Hat Enterprise Linux from version 7 to 8 because it had reached the end of its life. A Postgres database was running on it that used a Red Hat Enterprise Linux 7 package, allowing some database or reporting features. When I upgraded to Red Hat Enterprise Linux 8, it was not in the repository. I needed to install it with some workaround. Of course, it was installed with some minor incompatible dependencies. 

I have mixed feelings about the built-in security features. SELinux must be configured correctly for the port and directory, or applications won't run, so we primarily disable it. Sometimes, we enable it and tinker with legacy systems deployed long before I joined the company. However, chances are it will break something if you enable it. 

We have been using RHEL for three years.

Red Hat Enterprise Linux has performed very well for our business-critical applications, with minimal downtime.

We don't need to dynamically scale our application because of our workloads, as we mostly use Red Hat Enterprise Linux for our internal tools. We don't have much demand to scale out.  Containerization lets you quickly scale out your application with some bots if your hardware supports it, and you have enough resources. 

In VMs, we didn't need to dynamically hot plug some service to compensate for the load. It would be vertical scaling by adding more resources. Sometimes, we need to do that for databases that consume a lot of memory, CPU, power, etc.

I rate Red Hat support eight out of 10. It depends on the priority of the requests. We had to launch several P1 requests because something wasn't working in our OpenShift environment, and we were stuck. The support response was quick.

However, we were annoyed that most of the support was based in India. Sometimes, they don't know what the problem is and need to escalate it to an expert in the US or or Germany. It prolongs the ticket resolution, but once it gets to the expert, they fix the problem instantly because they know more. 

Positive

We previously used other Linux distributions with Docker. We prefer Red Hat Enterprise Linux because of its enterprise support capabilities, which open-source distributions like Debian or Ubuntu lack.

I'm unsure what the standard Red Hat Enterprise Linux license costs for one machine. We pay for premium support that guarantees a response in two hours. 

I rate Red Hat Enterprise Linux eight out of 10. If applications and package installations work correctly, I would give it an 8.5. It's a pleasing OS to work with, especially Red Hat Enterprise Linux 8 and 9, which are more polished than Red Hat Enterprise Linux 7. I briefly interacted with Red Hat Enterprise Linux 6, I'm 27, so I know I'm very young, but I know colleagues who worked with Red Hat Enterprise Linux 4, 5, and 3. 

Other open-source Linux distributions might work if they have high levels of community involvement so the community can identify and fix vulnerabilities quickly. Alma and Rocky Linux are all upstream from Red Hat Enterprise Linux. If you want to go with an open-source distribution, I will point you to Alma and Rocky because they are the one-to-one replacements from CentOS. You don't need a subscription. 

We are a big company with many customers, so we prefer a stable platform with support. You can't open a ticket for open-source distributions like Debian or Ubuntu if you have a problem, ticket. With Red Hat, you can open a ticket if you discover a bug. That's included in your support subscription. You also get regular patches, so we can show our customers we are compliant, etcetera. It's a no-brainer to use an enterprise distribution with support instead of something open source where you don't have a support subscription.

Most of our tech applications are based on Red Hat Enterprise Linux.

We chose Red Hat Enterprise Linux for most of our workloads and applications because it is an enterprise-grade operating system with regular security patches, reliable support, and a guarantee against hacking. Using a different OS would leave us vulnerable to security risks and complicate upgrades.

Currently, 70 percent of our Red Hat Enterprise Linux environment is deployed on-premises, while the remaining 30 percent resides in the cloud.

We utilize Ansible to automate the deployment of numerous Red Hat Enterprise Linux modules. This centralized approach, managed by a single Ansible engine, streamlines our development process.

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

Red Hat Enterprise Linux's built-in security features satisfy our security requirements.

Red Hat mitigates risk by rapidly releasing patches for identified vulnerabilities, which is crucial for mission-critical applications.

It offers stability that enhances business continuity, simplifying upgrades, even for minor releases. Its compatibility with OpenSCAP, which provides profiles for various compliance benchmarks, streamlines compliance testing.

Red Hat Enterprise Linux provides regular security patches and proper support, allowing me to focus more on application management than worrying about the operating system.

It helped us avoid emergencies caused by security issues. The CVE reporting and knowledge base are valuable resources.

Red Hat Insights provides the tools for proactive environment management by identifying potential vulnerabilities, such as CVEs before they become a problem. This allows for advanced knowledge of system vulnerabilities and provides specific remediation guidance, which is more efficient than relying on regular scans.

Red Hat Enterprise Linux has helped reduce our total cost of ownership.

Red Hat Enterprise Linux is an enterprise-grade solution where we receive regular security patches and proper support.

Red Hat Enterprise Linux was not used for containerization due to its mutable nature, unlike CoreOS, a lightweight and immutable Red Hat Enterprise Linux variant designed explicitly for containerization and optimized for running authorization.

I am testing AI workloads, and I'm not sure if Red Hat Enterprise Linux is fully equipped. It might not accommodate AI workloads as effectively as needed.

Some Red Hat applications, such as Ansible for automation, are considerably more expensive than the average open-source solution.

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

Red Hat Enterprise Linux is stable, and I have not encountered issues compared to other applications.

Red Hat Enterprise Linux is scalable.

Red Hat's stability has meant I haven't needed their support for years, but when I did contact them previously, their response was quite fast. While their support for OpenShift is acceptable, I do have some concerns about it.

Positive

A stable OS allows me to focus more on applications, lowering the cost of managing the infrastructure.

Red Hat is stable, and we always opt for the lower-tier subscription, which is affordable. It doesn't have unexpected issues that require a premium subscription.

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

It is important to assess the risk and use case before choosing a third-party Linux OS. For mission-critical applications, Red Hat Enterprise Linux provides insights and rich features like the patching cycle.

We use Red Hat Enterprise Linux as our server operating system to install and configure various applications. Its uses include system troubleshooting, DNS configuration, and many other tasks, especially in a mixed environment with Ubuntu.

Patching Red Hat Enterprise Linux in our environment is a straightforward process that utilizes Red Hat Satellite. We identify necessary patches for production servers in the content view and notify customers two days in advance via email. Before patching, we verify the Nagios servers for identification purposes. We then execute a pre-configured Ansible playbook to efficiently patch our 300 servers. This playbook was already established, and our only interaction with it is to run it.

The web console is handy, especially for tasks like command line operations. Its secure environment allows for the safe execution of queries.

Red Hat Enterprise Linux is most valued for its reliability, as evidenced by my daily use.

The documentation needs improvement. Providing more detailed explanations would make it easier to work on projects.

I have been using Red Hat Enterprise Linux for my entire career, which spans over eight years.

Red Hat Enterprise Linux is stable. There has been no significant issue regarding lagging or downtime.

Red Hat is highly scalable and essential in the industry. I would rate scalability nine out of ten.

The customer support from Red Hat is good. They are always there to help when needed.

Positive

I have used Ubuntu, and Kali Linux alongside Red Hat.

I have been involved with migrations to Red Hat Enterprise Linux, which are not complex. For example, migrating to Red Hat Enterprise Linux 7 or 8 is easy, requiring only the installation of necessary dependencies and the creation of a file to sync files to the new system.

I typically work as part of a team rather than implementing integrations on my own.

Red Hat Enterprise Linux is quite expensive, particularly its technical support, which can cost $500 per hour.

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

Realizing the benefits of Red Hat Enterprise Linux took time, as post-deployment troubleshooting was often necessary. This included tasks like opening ports and verifying functionality, which were sometimes prerequisites for the system to operate. These requirements varied depending on the specific application used and its security needs.

We perform maintenance on Red Hat Enterprise Linux every weekend, including backups. Incremental backups are done daily, while full backups are completed every weekend.

We are using the solution for automation. Mainly, we're doing a lot of automation with it. One of the projects, for example, is for ensuring payments processes on forms. We streamline and optimize the insurance claims process using OpenShift. This has enabled us to do faster claims processes and make resource utilization more efficient than it was. Everything can be done online. There are no papers involved. 

It is mainly just cutting out redundant tasks. The focus was mainly driven by driving costs down and efficient resource utilization. We wanted a solution that could make deployment easy and ensure scalability.

The biggest benefit has been the automation. It affected our delivery schedule. Instead of doing something in two weeks, we do it faster. We've cut down our production time. And people are able to focus on other tasks since they're automating a lot of things. Even with our clients, when they have issues, we have created a system where they can send out a ticket. And from that ticket, we can diagnose, and it's easier to solve the issue at hand. 

In terms of cost per head, we've seen a drastic drawdown from that. It is mainly optimizing a lot of our systems and resources.

The high availability is great. It's available most of the time - even when we're doing upgrades, provisioning, configuration, and patching. It made things easier for us. 

The automation is great. I'm a big fan of offering convenience to people and making systems easier for people to understand and use. 

There are good features, such as proactive monitoring as well. It offers predictive analytics, which helps you identify issues before they impact operations. We can foresee several problems. On top of that, this is how we can combat those problems. These types of features are really valuable when considering a company's strategy and when it comes to the impact of operations. 

We are able to move workloads between different clouds or our data center using Red Hat Enterprise Linux.

The knowledge base on offer is quite extensive. We started learning from a third-party provider since we've had a lot of use cases. Maybe you are installing something, or maybe during virtualization, you have to do something, and you need more information. The Red Hat OpenShift community is quite huge. Even a resource such as YouTube has people releasing videos on common problems. Even outside of Red Hat itself, the Red Hat community is very good. The information is extensive. The knowledge base is there. There's a lot of information sharing. People do not try to gatekeep information. 

When it comes to provisioning and patching, so far, we have not had a lot of issues. We currently are using a subscription model. In terms of getting security patches and updates, they support us quite well. There's a 24-hour support base and they're quite good. 

I've tried the Leapp and Red Hat Insights features. It helps with proactive monitoring. It did analyze the system configurations and compares those against databases of known problems and fixes. Basically, there's a pool of data that has common issues and it analyzes how you've configured your system and then compares them. It can come back to you and say, "Hey, this is your problem. Why don't you try the solution?" It's like a good AI tool. It gives us a lot of help. It's quick. Thanks to this feature, we sometimes find that we don't really need to open a ticket for support.

We realized the benefits of using RHEL in months. We were told when we were doing the onboarding, we'd see benefits in six months. For us, it took a little over eight months. That was due to some of our internal processes that we had to do, some sign-offs, et cetera. Still, it took us less than a year. Over time, we are down 20% to 30%.

In the beginning, we didn't start on the cloud. Only now are we fully transitioning to going off-site. There are still some clients who are a little resistant to going to the cloud. It's nice to be hybrid, to accommodate both. We've done a lot of virtualization and server consolidation. So far, everything is running smoothly. 

When moving workloads between different clouds or data centers, it's not that simple. There are a lot of things that you need to consider, including prerequisites and things like hardware, network, operating systems, et cetera. Once you get the hang of it, it becomes easier. However, in the beginning, it was very, very challenging. Coming from a development background, I found it easier to use command lines.

I've hit some snags doing updates or changing things for clients. 

It would be nice if they improved vulnerability management. They could add more security tools and tools for provisioning. 

I've used the solution for two years. 

The stability is good. We don't really have any downtime. I'd rate stability nine out of ten. 

We've had no issues with scalability. It's quite user-friendly. 

During the implementation, we did have to open a support ticket. They assisted us effectively.

Positive

I've never tried other solutions. I know of other solutions, such as Ubuntu. However, my interactions with that solution have been minimal. 

The initial setup was a little bit complex. The instructions, however, were very clear, and our deployment strategy was clear. Still, for the technicians doing it, it was complex.

The setup took about a week and a half.  

I've been involved with two upgrades so far. They were challenging. There were a lot of teams involved. There needed to be a lot of migration planning. We had to use the Link Utility and we did a lot of testing first. We spent a long time verifying the applications and checking dependencies. It was quite a learning curve.

There is some maintenance needed in the form of system updates. 

We did get a lot of help from RHEL. We had senior engineers guide us through the setup.

We've seen an ROI of around 30%.

When we went through IBM, it was quite expensive. Now, we are going through AWS, which is less pricey. 

We started off as a partner to IBM, and IBM opened up the opportunity for us to build certifications for Red Hat through the certification program. Then we became support specialists, taking on RHEL projects. We are in the process of becoming a reseller. 

I'd rate the solution eight out of ten. We're doing a lot of big data infrastructure and they are giving us good stability and performance.