Most of our servers are low latency, and it's easier to have low latency applications run on Linux. Red Hat Enterprise Linux's installation is easy. We don't have to reboot Red Hat Enterprise Linux like Windows, where there are a bunch of system updates that you have to do. Red Hat Enterprise Linux is just easier to manage.

Red Hat Enterprise Linux's most valuable feature is its stability.

We would like to have a better understanding of what to expect when we move to a different version of Red Hat Enterprise Linux.

A latency always gets introduced when we move to newer Red Hat versions. I wish we wouldn't see that as often as we do nowadays. It would be nice to know the changes upfront rather than when we have to open a case, go through a couple of months, and then find a good resolution. We want a better understanding of what we will see when we update the kernel from seven to eight.

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

Red Hat Enterprise Linux is a pretty stable solution. Its stability is a lot better than most other operating systems.

Red Hat Enterprise Linux's scalability is better than other competitors.

For the most part, Red Hat Enterprise Linux's support has been really good. Most of the time, we've had to escalate it to get a good response.

Neutral

Red Hat Enterprise Linux’s initial setup is pretty straightforward.

Whenever we see a compliance issue and need a patch, it's been relatively easy to get Red Hat Enterprise Linux to update it.

We have a mix of Windows and Linux. Around 80 percent of our systems are Red Hat, but we also have Windows. So it depends on the application.

Most applications are compatible with Red Hat Enterprise Linux. It's easier to tune on a Red Hat system than on another OS. We could pin applications to a core with Red Hat Enterprise Linux. In terms of tuning, Red Hat Enterprise Linux performs better in the long run.

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

We use the product as our server's operating system.

The enterprise support of the product is valuable to us. When stuff gets difficult, it's nice to have somebody to ask about it.

The solution should be updated more with the releases of programming languages. They’re lagging a bit too much. We have a lot of developers complaining about having releases that are too old. For example, if they want Python 3.11, Red Hat Enterprise Linux supports only 3.9. So the product is lagging behind a bit more than our developers would like. 

It would be nice if all the features that are available on the cloud, like Image Builder and Insight, would be available on-prem.

I have been using the solution for five years.

The product is very, very stable and tested. It is like everybody tested everything for five years, and every problem was fixed.

We have never had a problem with the solution’s scalability. We have around 6000 Red Hat Enterprise Linux servers in versions 7, 8, and 9.

Red Hat Enterprise Linux is a lot better compared to all other products. I rate the support an eight or a nine out of ten. There's too much information on the support page sometimes. If we log in to the support pages and try to find information, it's hard to get what we're searching for.

Positive

We had a lot of different Linux distributions. The pros of Red Hat Enterprise Linux are that it's the same platform for everybody, and it works for everybody. If you need something very special, you might get issues in Red Hat Enterprise Linux, but you can work around it. 

The biggest issue with Red Hat Enterprise Linux is mostly the old packages. It is a con if you have something that you know is a bug that hasn't really been released in Red Hat Enterprise Linux but has been released in the other products.

We do a template, and then we just use it. It's quite great.

We take 30 minutes to deploy the solution. It depends on the size of the machine.

I am using versions 7, 8, and 9. By implementing the solution, we wanted a unified server with a baseline platform that everybody uses. We wanted to have just one server that is enterprise ready.

We do not really have compliances in the same way as an American company has. It's nice to have IT security personnel. You get SELinux from the start. However, we get a lot of support cases because of it. The developers face problems with it. So, we get the security, but we also get lots of support cases. Usually, I end up in the middle of that because I work with support.

We run containers on OpenShift. We run only one platform, so portability isn't a concern. We only have Red Hat Enterprise Linux and OpenShift. We don't really need portability since we are government agencies. Nothing else other than on-prem is allowed for us.

The knowledge base offered by Red Hat Enterprise Linux is extensive. It is a bit hard to find information. However, when you find it, it's good. The packages are a bit old. We have a bit of an issue because of that. But other than that, it's a great operating system.

Overall, I rate the product an eight out of ten.

We use Red Hat Enterprise Linux for OpenShift. We run KVM and then deploy OpenShift under it. Additionally, these are my customer's use cases. 

We run it in-house for prototyping applications. Moreover, my customers utilize it to port older Solaris applications to Linux. I also use Linux on Z.

The customers would benefit from quickly identifying vulnerabilities as they arise and being able to fine-tune machines if certain features are not properly fine-tuned. 

Since we use it for virtualization, KVM has been quite valuable. It's been very solid running OpenShift under KVM. The toolset has been pretty good.

By implementing Red Hat Enterprise Linux, the customers were getting off older hardware like Solaris. They're trying to migrate their applications off those boxes and also cost savings. They were migrating over to consolidate onto Z.

However, none of my current customers use Red Hat Insights. I'm trying to encourage them to adopt it, but since they operate in air-gapped environments, Insights needs an internet connection. I mainly work in the Federal space.

Personally, I like the terminal-based tool called Tusa for certain activities. Sometimes we just don't have a web interface available for repetitive tasks. It would be nice to have a web-based tool for Red Hat Enterprise Linux since we don't always have access to a web browser.

The stability of Red Hat Enterprise Linux is solid. It performs well and handles the workload effectively.

It scales well on my platform. We are running OpenShift and other machines on it, and it scales without any issues. Although, it's largely due to the platform itself.

The initial setup can be complex in certain cases, particularly when dealing with a fed customer that operates in an isolated environment. But, in other installations, it has been mostly straightforward. Red Hat Enterprise Linux could still work on making it a little more streamlined in terms of deployment.

There have been some issues we've had with portability, picking it up and moving it somewhere else.

In terms of simplifying risk reduction and maintaining compliance, Red Hat Enterprise Linux is good. The customers I work with don't use them extensively. However, during the machine building process, we apply some security features at build time rather than later on. We take measures such as applying a stake during the build process. While I keep pushing the customers to use the provided tools, some of them operate in air-gapped environments, preventing them from accessing the internet for the latest rules.

The portability of applications and containers built on Red Hat Enterprise Linux is pretty good. We actually build applications on one platform and successfully deploy them on another, so that's pretty good. Overall, using Red Hat Enterprise Linux is definitely a strong set for my customers.

My customers definitely see an ROI. Especially when running it on Z platforms due to fewer processors and, consequently, fewer licenses required. They have experienced a return on investment. 

When I previously worked in a Linux shop using Tusa, it was more expensive. But I think Red Hat Enterprise Linux has become more competitive, particularly for Z platforms.

One example is the consolidation of their infrastructure, getting off of Solaris, and not paying high maintenance costs. Consolidating onto Linux, specifically Red Hat, has been helpful for one of my customers.

There are not many choices available on the system they use, probably only two or three options. Red Hat Enterprise Linux is the preferred choice, especially since it is widely used in the enterprise.

The other two choices are SUSE and Ubuntu, which are commercially available systems. Honestly, no one is going to use Ubuntu because it's not popular enough. So it's really a choice between SUSE and Red Hat Enterprise Linux. SUSE has been around longer on my platform and system settings. But I think people are shifting over to Red Hat Enterprise Linux as it runs on Intel and is more enterprise-oriented.

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

Our customers use the product primarily for application servers, authentication apps, and tool servers. If a feature is available in Red Hat Enterprise Linux, they're most likely using it. The product allows us to use applications that run on open-source software. The product also provides on-site support that helps us if we have any issues.

The solution is stable and reliable. Being able to move back and forth between systems, products, and middleware is a huge boon.

The solution lacks proper documentation. There have been times when I found a document that was supposed to fix an issue, but I realized it was wrong. Then, I would send it to support, and they would fix it.

Our customers have been using the solution for six or seven years.

The product’s stability is good. It has minimal downtime when it comes to generic deployments. Once you start adding complexity, there are other issues.

The product’s scalability is good. Our customers are able to scale out thousands of instances in minimal amounts of time.

The support team is great. I have friends that work on the support side. I can count on one hand the times I've been dissatisfied with support. Usually, when that happens, it's because it's something that either couldn't be fixed or something too old. I rate the support a nine and a half out of ten.

Positive

My involvement in deployment depends on which systems are being deployed. My organization constantly rolls out new systems via OpenStack, on-premise, or other cloud providers. I help build their base images.

The product’s deployment is pretty straightforward. Everything we build is automated and kicked out from there. Once the base image is built, there's really not much to do.

My customers have seen an ROI from the product. They have an on-site support team that is able to help them with issues. It is important to them to have a good team of people to reach back to and to be able to work together.

Our customers conduct market research before any purchase. Red Hat Enterprise Linux has consistently been a top contender for us and our customers. We usually support Red Hat Enterprise Linux because our customers choose it.

The biggest push towards Red Hat Enterprise Linux is the ability to have something that's supported and open-sourced. Having transparency is important to my customers. They want to see what they're putting into production, development, and testing. It is important to the customers to see what's going on and what workloads they're handling and to know that what they're putting the workloads on will be solid and secure.

Our customers use the solution on multiple cloud providers, mostly AWS and Azure. Our customers buy a yearly subscription for some equipment, and for short-lived instances, they do on-demand pricing within the cloud provider to buy the ones they offer.

I believe Red Hat Enterprise Linux has helped our organization avoid cloud vendor lock-in. We've been able to pretty reliably and easily lift, shift and redesign our application from on-prem to the cloud. It might not necessarily be a huge benefit for us. However, it is definitely a perk, especially in an environment where we have to go through a certain purchasing cycle and background reviews for everything. It does end up helping us.

As much as I've used Red Hat Image Builder, I really like it. Though, I've only had to build a handful of images out of it. We can't use something like Fedora, where you've got a nightly update. Red Hat Enterprise Linux is tested and reliable. Having something they can work on, develop, and use daily is helpful to our customers.

The sosreports and soscleaner developed in recent years are a huge improvement. My customers tend to be pretty fixed in their ways and what they use, so they continue to work and use things for longer than they should, but that's the beauty of Red Hat Enterprise Linux. It is supported, and we still have the necessary reach back.

Red Hat Enterprise Linux is pretty solid. It's been tested. It has its upstream counterparts that ensure that most of the bugs get worked out, and what makes it down into the final testing is strong and resilient. We've been working on moving workloads between the cloud and data center with the customers. Instead of lift and shifts, we try to redevelop their applications instead of spending $10,000 to give 32 cores in the cloud because they had 32 cores in the system.

We have a fantastic team that works with us and supports us. The team goes out of its way to help find cost savings for both us and our customers.

Overall, I rate the product a nine out of ten.

We use the solution in our company for normal application support and for databases.

In Red Hat Enterprise Linux, we use Red Hat Satellite as part of all the patching and deployment, even from on-premises and AWS, and that's been really helpful since it is one product that can be used in a hybrid environment. It's just one place to manage everything. It's good since you don't have two different products or places to manage, especially if you have a multi-datacenter and not a multi-cloud but a multi-location environment.

The room for improvement depends on how we use it. It's just a normal operating system. Considering an area where the solution lacks, I think we can look into a lot more automation and integrations with Red Hat Enterprise Linux and other products. However, I cannot say specifically where the improvement should be because it mostly depends on how we are using it. It just works the way it's supposed to work.

I have been using Red Hat Enterprise Linux on the cloud for six to seven years. Currently, we are using Red Hat Enterprise Linux Versions 7 and 8.

The product's stability is good, with 99.99 percent uptime.

Scalability is something my company hasn't delved into that much. Right now, scalability is mostly on the backend hypervisor or how we leverage AWS.

I would probably rate the support around an eight out of ten.

Positive

We have been using Red Hat Enterprise Linux since I've been with the company. Linux is our platform of choice.

I supported those involved in the setup phase peripherally.

The initial setup was straightforward.

Regarding the straightforward setup, building the base image and deploying it with our internal security standards was pretty straightforward.

We used to get our own license model. We purchased a license through Red Hat.

We haven't necessarily evaluated other options, but there are a lot of requests coming from other application developers that want to deploy other operating systems because they are much more common, especially in an open source environment. So we have looked into those options. However, Red Hat Enterprise Linux continues to be the main platform that we support. We are also looking into other solutions just in case a scenario arises where a vendor cannot support Red Hat Enterprise Linux for some reason and we will need a backup.

Regarding the problems we are trying to solve by implementing the solution, I would say that it is our operating system of choice. I think the support is good since we have Red Hat Enterprise Linux subscriptions. We get support for all the operating systems from them. It's great and stable.

Regarding the solution's resiliency, it is good. We've been running, and we have over 99 percent uptime all the time. We also do monthly patching and everything, so it works. Kernel upgrades also work as expected. So it has been pretty good.

Regarding how easy or difficult it is for you to move workloads between the cloud and your data center using Red Hat Enterprise Linux, we don't use relative migrating solutions. It's considered a separate environment, but we use the same base image. 

I consider the solution to be the main OS because going with an open source solution like Red Hat Enterprise Linux, you have better support.

The support is great. We also have integrations with other products, especially with whatever Red Hat releases. We have all those integrations available and we can easily take advantage of it.

I rate the overall solution between seven and eight out of ten.

In our organization, we use the solution as our internet banking platform.

Some of the solution's features include scalability, lower footprints, and the fact that licenses don't really cost us much. Also, the upgradeability is fantastic. With Windows, you can't upgrade to certain versions. I haven't found that issue with Red Hat Enterprise Linux.

Working at a bank, I can say that lack of scalability is a big no-no for us since we deal with people's money.

It would have been nice if we had the ability to do updates without rebooting. If we can update certain parts internally without having to remove them from the entire server, that would be fantastic since, else, there will be downtime, and we will need to reboot. We have to schedule downtime. If we can do so, we will patch it and continue running. Even though the downtime is minuscule, having as little as possible downtime could be great.

Speaking about the downtime caused due to the lack of the aforementioned feature, we reboot about 40 servers every time there's a patch, and they're not staged all at once. The whole process will take an hour or so.

I have been using the solution since I started using Red Hat Enterprise Linux version 7.

Regarding stability, it's good since we haven't had a major outage.

I rate the support an eight out of ten, considering the callback feature and rapid response compared with Windows, where you need to wait for a couple of hours to get support.

With Red Hat, the community is so robust. Most of the time, while waiting for a Red Hat engineer to call us back, the solution to the issue is already provided. This is because it's an open source platform. 

Positive

Previously, we used AIX. Now, we still use CentOS and Rocky for development.

Though the solution is deployed on a hybrid cloud, I would say that ninety-eight percent is on-premises, and two percent is on the cloud.

Also, I am running my workloads and applications on the cloud.

We transferred our license to the cloud because we were originally a VMware on-prem shop. We're transitioning some of our workloads to cloud licensing. Also, I have opted for a subscription. I don't know where we got it from because when I came to the company, it was already in place.

Comparing Red Hat Enterprise Linux to other operating systems, it is a nice solution, especially considering the support we get from Red Hat. Not a con, but on Windows, the GUI or navigation can be a little bit tricky.

By implementing the solution, my organization is trying to solve the agility issue. Using Red Hat Enterprise Linux, we are not tied to Windows patches. Windows patches break sometimes, and then the application goes down, which is a big issue. With Red Hat Enterprise Linux, we have that reliability and robustness.

I am very impressed with the solution's resiliency.

Regarding how easy or difficult it is for us to move workloads between the cloud and our data center using Red Hat Enterprise Linux, I have found it to be very easy.

Regarding portability, it is easy. I was speaking to someone over there who benefits from containers. I mentioned it to my manager, and we are going to have a discussion about it.

In terms of my assessment of the solution's built-in security features when it comes to simplifying your risk reduction and maintaining compliance, I feel it is good. We haven't ever had an issue ever with the solution.

As nothing is perfect, I rate the overall solution a nine out of ten.

We use the solution for deploying middleware applications and many different applications that we have, like the ones we can use in the marketplace with different users. We use other kinds of solutions in many of the applications we develop. But in general, we use Red Hat Enterprise Linux.

Benefit-wise, the product is very stable. The product is also very compatible, and many people want to use it.

There are a lot of features in the solution. Red Hat Insights is one feature that we rely on currently.

The model, specifically the consumption model, is an area that needs improvement in the solution.

We had a really big challenge striking a chart between on-premises and the public cloud. The approach is that you pay as you go in Red Hat Enterprise Linux. In general, you pay for whatever you use instead of preparing for a full year.

At times, language is a barrier when it comes to support. That's one of the aspects I would like to improve about the solution.

I have been using Red Hat Enterprise Linux for six to eight years. My company has a partnership with Red Hat Enterprise Linux.

Red Hat's support is good. Sometimes cases take a little bit longer to resolve. If you are clever enough to upgrade the case and put it at a very high level of priority, then it gets resolved faster. In general, the support is good. I rate the support an eight out of ten.

Sometimes, a customer doesn't speak English or we need people who speak Spanish for the case to be easier to understand. In those cases, we lose time. I can't push all my engineers to learn to speak English. My customers and our engineers speak Spanish.

Positive

We've been working with Red Hat Enterprise Linux since the beginning.

I was involved in the deployment a long time ago. The setup process is easy. The solution is also easy to use.

Regarding the time taken for deployment, we can do it with a machine at this moment using Ansible. In our orchestration, we passed more or less, creating one machine for Red Hat and the entire environment. It took us eight days and an hour. At this moment, we can deploy it on a machine in an hour with all the security. If a developer comes to us and tells us that they need a new machine or new instance, we can provide that in an hour on-premises. In the cloud, we have to use a lot of tools.

I have purchased the license via hyperscalers and transferred it as well. I purchased the license from the marketplace and also from Red Hat.

Pricing is something that can always be better.

We have not evaluated other options since we trust Red Hat Enterprise Linux.

I am running my workloads on-premises and on the cloud. I mainly use AWS.

Resiliency-wise, the solution is very good. It's good because we don't have a problem with our environment at this moment. When we don't have a problem, we don't need to explain what is to be improved in the solution. It is reliable and doesn't break or bring us any problems.

Regarding how easy or difficult it is for me to move workloads between the cloud and my data center using the solution, we don't have problems. In general, it's easy.

We are talking about moving applications from on-premise to the cloud. We need to see if that represents any cost savings. We would need to go through a migration process, and that would be an extra cost.We would need to see if that is beneficial.

I rate the overall solution a nine out of ten.

Internally, we use Red Hat Enterprise Linux for services and for applications that we run, especially Linux based-applications. We also have SAP solutions, which we sell to the customers as a total solution with Red Hat, SAP HANA, and also for our own cloud-based SAP HANA, which is under Red Hat's operating system.

Red Hat Insights is quite an interesting and valuable feature. Lately, we used the malware scan feature. The Cockpit feature and web interface were quite helpful. We have also begun with OpenSCAP, which used is to harden the operating system's security features.

The first area for improvement is documentation, and I consider it since I have been working in IT for more than twenty-five years. For twenty years, I have been working with open source, and I see that the documentation is lacking, so it needs to do more work on its documentation part. Most open source and upstreams from Red Hat products work from the open source solution and have better documentation than in the actual Red Hat products.

New products need better documentation. The websites also have a single sign-on to get you from one side to the other. As a partner, I had a problem finding out how I needed to connect and to which side of the solution. I consider myself an expert user of the internet and websites, but going from one side to the other, was quite problematic.

I have been using Red Hat Enterprise Linux on the cloud for four to five years at least. My company has a partnership with Red Hat, and so we have our own licensing for the product. We have customers whom we manage, and they purchased the licenses on the go from the cloud provider. We just sold them the managed services. But mostly through us, we should be selling the licenses.

It's a very stable product, and that is actually the reason we are forcing or pushing customers to go with Red Hat Enterprise Linux.

The solution is scalable.

I rate the support a seven out of ten. The support is knowledgeable but slow if we have to get answers.

Neutral

We use Red Hat Satellite for managed services for our customers. And, of course, we use a product of Red Hat Enterprise Linux for servers. We started with OpenShift in the lab at the beginning, but now I'm beginning to produce it for our own services. So, now I can offer these to the customers.

One of the discussions in my company at the beginning of this year was to see if we could test our services on-premises for the virtualization, specifically for the KVM virtualization. But since it was not approved, we'll have to see the next step.

I have worked with other open source distributors. I have worked with SCO-Linux and Unix, which is the base of Linux. I didn't personally make the decision to switch. The company decided to switch since we are partners, and we are focusing on putting in the best efforts in terms of the partnership and customers we have with Red Hat.

The solution is deployed on both on-premises and the cloud. We have customers on the cloud server platform where we run their network, and we manage through Satellite. We also have it on-premises.

I was involved in the deployment of the solution. We created some automation, so the setup phase is straightforward. We use templates for all of those, but to manage the templates, and what it will include, we use external tools to make it easier for the deployment automation.

Regarding deployment time, it can be done in seconds. It also depends on what application we are speaking about since for an OS or more difficult solution, like Red Hat Satellite, you need more time.

I have seen a return on investment, especially considering the time taken to resolve the problem where we bought some support from Red Hat.

Regarding the prices, the new changes are actually not bad as it works for enterprise solutions. But it could have some other options for super solutions for the students in colleges, and they could actually win more customers from that. Of course, we have the test licensing and all that for the partners, where it's very useful for us to be able to test more of the products. But to win more would be much easier for us also if they introduce special pricing for students, universities, governmental institutions and all that. Most probably there is a price for them, but we haven't got that information. Also, Red Hat sometimes goes directly and not through the partner, but I'm not an expert.

I wasn't the one to make a choice, but I think my company evaluated other options, and it was their choice to go with Red Hat.

My company is a private cloud company. Mostly, we have our own private services, providing private cloud services to the customers. But we also provide public clouds like Azure and some Amazon clouds.

Regarding resiliency, it is a good standardized OS with stability. But sometimes, it is a little slow in reaction to problems that might appear. For example, we had this big Java Log4j bug where their reaction was very slow compared to other distributions. Of course, they found the solution when they had it, but it was quite a slow reaction. In general, it's a very stable OS.

Regarding how easy or difficult it is for you to move workloads between the cloud and your data center using Red Hat Enterprise Linux, I don't have any solution for that. I have to migrate it manually right now.

Regarding the cost-saving capability of the solution, I would say that it is possible to save on costs because of the automation we use through Red Hat Satellite for maintenance and how we have managed automation, time to spend on the service, maintenance, test, problems, etc. So, you can say that it's been a cost-saving procedure.

I rate the overall product a seven and a half out of ten.

We use the solution majorly for JBoss, Apache, Java workload, and Comcast. We also use it for Apache Sattelite to do all the patching and database management. We use it for almost everything. We were a pure RHEL shop, up until recently. 

The most valuable feature is Satellite. Its consistency in patch upgradation is great. For the ten-year lifecycle, we have been able to rely on it and not worry if the patch will break. We do not need additional patching features since it covers everything.

The Modules feature is awesome but it could be even better.

We have been using the solution for 25 years.

The solution is stable. I have never remotely questioned its stability. The downtime is rare. It is usually a vendor's application issue unrelated to it. 

My company only has one complaint; we have been using it for more than seven years out of its ten-year lifespan and have yet to receive any version update. The drivers have become stale. We are trying to upgrade them manually. It would be nice if they had updated the drivers. If they do not update them, the solution will end soon. They should prevent it from crashing every time we try to update it. We are still rolling Ansible to automate some of the functions but, it is complicated to process with a vast sync of firmware and drivers.

The solution is scalable. I am a Satellite owner and we've had scaling issues with it. Those issues are mostly because my company didn't make it scalable in the right way.

They have their own expectations of how to make something highly available. And Satellite doesn't fit into that. 

I rate the solution's technical support as nine out of ten, as there is always room for improvement. I never had an issue with the support services. It is good and worth the value. 

I don't usually put up a ticket for every minor error. I am an expert and know the technicalities required to resolve the issues. So, whenever I contact them, I expect it to get somewhere. Because most of the time, the executives put more than one problem in the same ticket unrelated to another. It becomes more complex and confusing.

Positive

Red Hat Enterprise Linux generates a return on investment. We have everything on it. We have Windows servers for SharePoint and multiple cloud providers as well. In addition, we have OpenShift and Docker Enterprise, and some other open-source applications.

The solution is a good value for money. They keep adding up essential features to the specific subscription plan. I am also not a big proponent of top-level open-source applications as they do not provide support services. Whereas, with Red Hat, I can call them for queries and get answers immediately. In comparison, open source doesn't have that facility. Even if you hire a support vendor, they just give their opinions and try to help but they don't own the project.

At the end of the day, we have a 999.99% reliability of only 20 minutes a year of downtime with Red Hat. It is impossible to get that with open-source vendors as sometimes the applications might break if it doesn't notify about the changes on time. Conversely, Red Hat Enterprise Linux has a ten-year life cycle assurance, so we don't have to worry much. Also, we are in a TAM program. Thus, we can call the support team immediately for any issue.

Our organization constantly evaluates other options, as Red Hat Enterprise Linux's cloud version doesn't offer new features. Other than that, we go back and forth using Centralized and Rocky Linux. We prefer the ones we don't have to pay for the licenses.

It has a strong security posture. I did a SELinux contract for my current company. Compared with open-source alternatives, Red Hat Enterprise Linux provides better support services and reliability. Also, we are rolling out a new Ansible platform for insights. It gathers information about how many jobs we have, how long they take to complete, etc.

We need to manage vulnerabilities for a massive base of clients' systems. We don't use open-source apps for it like Red Hat. We have a third-party tool as we straddle different compliances. However, Red Hat is great about security announcements. I can call them anytime for an update as well. But it is challenging to work with the vendor for scanning machines. It does not know how to work with Red Hat packaging version numbers.

I rate the solution a nine out of ten.

RHEL is a phenomenal operating system for three primary reasons: 

• Support compared to the rest of the Linux ecosystem
• Cohesive ecosystem 
• Application platform

The combination of these three aspects has proven to me from an advising perspective that it is key in decision-making.  

Our clients purchase the use cases via cloud provider and hyper-scale. It's a combination of both. Mostly, new clients prefer going for hyper scalers. Whereas the clients with Red Hat licenses, predominantly those from the banking sector, transfer the licenses to the cloud depending on their hyper scaler plan.

The main benefits my clients have seen are the supportability, maintenance of the operating system, security, and the ecosystem that ties it all together.

The solution has a phenomenal operating system. Its support features are best compared to the rest of the Linux ecosystem. Generally, applications don't rely on operating systems per se. When combined with the container ecosystem, security is the paramount feature that is most asked for.

The problems our clients try to solve by implementing Red Hat Enterprise Linux vary. The main ones include containerization, cloud transformation, and visual transformation in terms of how you get to the cloud in a hybrid mode. The key aspect that I give advice about is how for the operating system in terms of the scalability to bridge the cloud to the on-prem world, so where they could have the OpenShift ecosystem that it runs into and helps them manage both systems together. 

The solution's operating systems are phenomenally resilient and stable. The good part is that Red Hat has backing and support. Also, combined with IBM, it gives more confidence to my customers.

The solution's ecosystem is good but it would be better to create cohesive components in all of the development tools. 

A developers' hub feature would help. 

OpenShift already provides excellent visibility, but bridging the gap with Kubernetes would be key because Red Hat Enterprise Linux drives OpenShift.

I'm a big open-source user. I've been using different forms of Linux for quite some time. For my enterprise purpose, I use the RHEL for other purposes and a few other different Linux operating systems. We have been using Red Hat Enterprise Linux for more than ten years.

I have experience working with Ubuntu, Fedora, Canonical, etc. From that perspective, the solution's stability is good. The security feature plays a key role in terms of the pace at which it receives updates for operating systems to maintain it.

In terms of the architectural perspective, the nature of the solution is scalable.

The solution's technical support is very good. My clients generally manage it, and I have received positive feedback. They have a responsive support organization to communicate with.

I have used Canonical and Ubuntu. In comparison with Red Hat Enterprise Linux, Ubuntu's ecosystem consists of multiple operating systems and container platforms like MicroK8s. The partnership with hyper scalers in terms of deployment is one of its benefits as well. On the flip side, it has some drawbacks regarding licensing and export control, where Red Hat shines well.

The solution's pricing and licensing are good. Although the open-source space is becoming more competitive, Red Hat brings value in terms of support. At the same time, different operators like Canonical Kubernetes are catching up. Thus, the price would become the differentiation factor regarding packages for support, and container ecosystem combined with Ansible. All these key elements would add more value to the pricing.

The solution's key element is its cohesive ecosystem between hybrid and cloud environments. It helps clients such as giant banks create a single space for managing workloads in different hyper scalers. This way, it helps in cost management and visibility. It creates a single platform to manage work. It helps in saving costs, especially with subscription plans. It provides them with a consistent cost structure. Also, being an open-source solution has benefits that fit within the ecosystem.

I rate it an eight out of ten, primarily for the support and licensing terms. It helps some of our enterprise clients navigate open-source licensing and export control complexities.

There are areas of improvement, such as the cycle of updates and the ecosystem as a whole. Also, the elements like Ansible are priced separately. For automation, there is an opportunity to combine everything. Even though they are different products, they shouldn't be charged separately from the ecosystem perspective.