Red Hat Enterprise Linux (RHEL) Reviews

It is for binding servers. It is for web servers, such as Apache and NGINX, and KVM virtualization.

We have servers running all time. We have not had any issues with Red Hat Enterprise Linux. We have had issues with Microsoft products over time. Because of the updates, we had downtime, but that is not the case with Red Hat Enterprise Linux.

It has been very productive for our organization. We have an online client buying or purchasing products from our website, which is available 24 hours.

Red Hat Enterprise Linux is good when it comes to building with confidence and ensuring availability across the infrastructure. I would rate it a ten out of ten in terms of stability and reliability. In the case of our web server, I have had availability issues with Microsoft, whereas, with Red Hat Enterprise Linux, we have not had many such issues. There has been only 1% downtime, whereas, with Microsoft, we have had a lot more downtime.

We have support. If we have any issues with the distro, we can call their support team. We have reliable packages from Red Hat.

Network management can be easier. It is getting more complex. They can also give more customization for the CLI.

I have been working with Red Hat Enterprise Linux for six years.

It is very stable. We have three websites running on Red Hat Enterprise Linux.

It works fine. We have had servers running for ten years. We have been just updating them, and we have not had any issues or downtime.

It is scalable. We can upgrade it, and the upgrades do not impact the product.

We have a team of five people who are using this solution.

We have premium support. It is excellent. We have not interacted a lot with their support. We have almost five engineers working in the team, so we did not have to contact them a lot. We did have any major issues with the hardware or software. 

I also use CentOS for educational purposes. Support and regular updates are advantages of Red Hat Enterprise Linux over others. 

For directory servers, we always use Microsoft because it is easy to manage and easy to control. Implementing and managing domain controllers on Microsoft is easy, and we can apply policies by groups (GPO).

Its deployment is very easy. It does not take long. Its maintenance is also easy. We can expand the storage for the operating system or the web server.

To those looking into implementing Red Hat Enterprise Linux, I would advise making use of Red Hat's community. 

Red Hat Enterprise Linux has had some impact in terms of security, but we have other security measures and procedures. We have not used SELinux and other embedded security features of Red Hat Enterprise Linux.

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

We use Red Hat Enterprise Linux for servers. We have deployed application servers and database servers on it. We run Oracle Database, WebLogic, Apache, and JBoss on it.

Red Hat Enterprise Linux is very important for our organization. We are very sensitive to security.

It is not difficult to move workloads between the cloud and the data center using Red Hat Enterprise Linux. Mostly, our teams use file servers centrally, and then they use scripts so that it is done automatically in the background. Initially, they may get problems while connecting due to the security or firewall, but once the connection is established, we do not see any problem with that.

Red Hat Enterprise Linux has helped to avoid cloud vendor lock-in. I am not sure how much our organization has saved in costs by avoiding cloud vendor lock-in, but we would have saved a good amount.

It is very stable and robust. My team is very comfortable working with it for all end-to-end activities. They can work with it very easily. They prefer working through the console rather than the GUI.

Its resiliency is good. There is no doubt about that.

I don't prefer Red Hat Enterprise Linux for desktop over other options. 

I have been using Red Hat Enterprise Linux for a good amount of time. It has been eight to ten years.

It is very stable. I would rate it a ten out of ten in terms of stability.

It is very scalable. I would rate it a ten out of ten in terms of scalability. It is highly available and scalable for servers.

It is good. I do not see any challenges. I would rate their support a nine out of ten.

Positive

We choose an operating system based on the needs and the use case. We use different operating systems for different purposes, so they are not comparable. For example, for desktops, Linux is not the best. For desktops, Microsoft Windows is the best. Similarly, if you are using any Microsoft products, such as SQL Server, Microsoft Windows is the best option. However, nowadays, we also have Microsoft products installed on Linux.

I am not involved in its deployment and maintenance. We have a separate team with 40 to 50 people around the globe for that.

We most probably have both on-premises and cloud deployments on a private cloud, but I am not sure. Our infrastructure services team takes care of that.

We have got a good ROI, but I do not have the metrics. I would rate it an eight out of ten in terms of ROI.

Its pricing is good and competitive.

I would recommend it based on the use case and the budget. If it meets your needs and budget, Red Hat Enterprise Linux is the best option.

Overall, I would rate Red Hat Enterprise Linux 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.

I'm a consultant, and our customers use this product. I work for a company that works with this product. I mostly work with Red Hat Enterprise Linux. We do designs of infrastructure projects from the bottom to the top. We install Red Hat Enterprise Linux at the system level. Based on the application requirements, we design, configure, and update the systems.

Our customers use it as a basic operating system on which they deploy applications. They have enterprise application servers such as Tomcat or custom applications that need an operating system.

I've worked with it both on-prem and on the cloud. It depends on the client. On the cloud, the cloud providers are both AWS and Azure. This also depends on the clients, but it's mostly AWS and Azure.

Mostly, our customers use Red Hat Enterprise Linux because of its performance and security. They want to have an operating system that is supported and secure because they don't want to spend too much time supporting a Linux version that is not enterprise. They want an enterprise product that is secure so that they don't have to think about it all the time.

It isn't difficult for our customers to move workloads between the cloud and the data center using Red Hat Enterprise Linux. The integration from on-prem to the cloud is quite easy because the operating system is the same. The operating system works the same in both places, so it's easy.

It has helped our customers avoid cloud vendor lock-in because they didn't need to buy a specific subscription from a cloud vendor or use a specific operating system from a cloud vendor and change the code of their application in relation to that. It's important to have a solution that avoids cloud vendor lock-in because they can move freely from one system to another system without any issues.

It has saved costs for our customers because it's a stable operating system, and they have no problem with security, patching, and so on. The operating system and the environment are stable. It works everywhere without any issues, so the development of the applications is not impacted by the system. Red Hat Enterprise Linux is easy to use and well-supported.

Support is most valuable. If a customer has a problem with a feature or a bug, we can open a support case for that, and the issue is resolved or taken care of. That's the main benefit of the product.

The resiliency of Red Hat Enterprise Linux is quite good. 

Some low-level aspects, such as the file system support, can be improved. There are a lot of file systems that are supported by other Linux distributions. Red Hat Enterprise Linux is a little behind those. For example, BTRFS is a file system that is not supported by Red Hat.

Some of our customers use the image builder tool to build the golden image to deploy to the cloud or to build a custom image to deploy on the cloud or on-prem. The golden image created by the image builder tool is good. It's the golden image. It works without any issues. However, the build process of image builder could be improved because it's not up to the standard or at par with other tools that build the golden image. However, it's quite useful and quite easy to use. It's not a big problem, but it could be improved. There is not a lot of information about how to use it. The process is not as well documented as the other parts of Red Hat Enterprise Linux.

The knowledge base offered by Red Hat is very good, but it could be improved and made much easier to search. Currently, the best way to find an article in the knowledge base is by using Google Search. By searching on Google, we can find the right knowledge base article, but it isn't easy to find information by using the search option within the knowledge base.

I've been working with Red Hat Enterprise Linux for the last four years.

It's very stable. I didn't have any issues with the stability of the product most of the time.

Its scalability is very good. It scales very well in the right infrastructure.

Their support is good. It's one of the best support in the IT world for a product because you always get a response for every bug or issue. Overall, I'd rate their support a nine out of ten.

Positive

They were using Ubuntu.

It's straightforward. It's pretty easy to deploy Red Hat Enterprise Linux. It can be difficult based on the workflow of the client, but overall, it's pretty straightforward to deploy on the cloud environment because all cloud providers support the deployment of Red Hat Enterprise Linux. The golden image of Red Hat Enterprise Linux is compatible with every cloud provider. There is a feature in the cloud console for joining the Red Hat Enterprise Linux account with the cloud account, so you can create cloud images from the console. It's pretty easy from that.

Our customers have seen an ROI because after they choose Red Hat Enterprise Linux, they stay with the product and renew the subscription. It's a good investment for the IT department.

Its licensing is pretty confusing. There are a lot of subscriptions, and it isn't always clear which subscription is the best, but with their support, it's easy to find the right one.

Our customers sometimes buy it directly from the cloud provider, but most of the time, they have a hybrid infrastructure, so they already have some kind of subscription, and they use that subscription on the cloud.

We evaluated other options, but other options don't provide the support and stability that come with Red Hat Enterprise Linux.

To someone who is looking at open source cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that if they are looking for an enterprise OS on a cloud environment and they want to have some stability and security, Red Hat is the perfect match for that.

Overall, I'd rate Red Hat Enterprise Linux a nine out of ten.

We prefer Red Hat Enterprise Linux as our operating system due to its excellent support. If a business wants something, we deliver it and we prefer a Red Hat Enterprise Linux-based system because of the support. It can be a simple application to a big system. It doesn't have pre-defined roles. It's a go-to operating system. 

Our use cases for it vary from plain operating system management to handling specific tasks such as running Oracle databases or other similar applications. They include quite a broad spectrum of requirements. Also, they are not limited to predefined roles but encompass the entire operating system infrastructure.

The solution's SELinux feature is a gold standard for security. It also has the best ecosystem. 

In addition, its automation platform, ITM, is a good product and works well for us.

Some of the solution's features need to be automated. We encounter the hassle of registering the system and attaching a subscription. Our company has development teams, and we have to develop subscriptions for them. Here, having the solution up and running on the developers' machines is a bit of a hurdle. Although we can run it on platforms like Red Hat Connect but, it needs to be somewhat more accessible so developers can just download it and start with the work.

I have been using the solution for 10-15 years.

The solution is stable.

The solution is scalable when combined with automation features. I rate its scalability a nine.

The solution's customer service is good.

Positive

I have used Ubuntu, Fedora, CentOS, and macOS. Initially, I worked as a Red Hat Certified Administrator in RHEL 5. Later, I began to work for its partner company. That is how I switched to the solution. It was not a conscious choice. It just evolved that way.

The solution's initial setup process is straightforward. You have to follow the steps, copy the template and multiply it.

The solution's price is reasonable. If you have a license for the support, they provide excellent services. The support team is always available for help in case of errors or system downtime issues.

RHEL’s built-in security features for simplifying risk reduction and maintaining compliance are good. If you keep SELinux on, it is all good. If you have a system with SELinux off for a long time, it could get you in trouble. The system will make many changes, like restoring files could break your application later. In case you resolve the problems simultaneously, it is fine. 

The troubleshooting feature of Red Hat is excellent. It can solve many issues on the machine right away. In addition, if you have an external scene, then Red Hat Insights is on. I sometimes go to this feature to see its status and what is happening. 

I don't do this on a daily basis and only check it every two weeks, but it's nice to have. I mainly oversee the high-level view of all the systems. This way, I know if the clients' machines need a patch system. 

There are some missing modules for SELinux in Ansible, like the playbook. It becomes a genuine hurdle to manipulate SELinux at the moment. I have to go to the machine, take a file to the repository, and deploy it.

I rate the solution a nine out of ten.

Our use cases are pretty broad. We develop the automation that provisions the VMs, and then anyone in the company can request the VM for whatever intended purposes.

Red Hat Support is really good. Support has a fast response time. The product has good security. We deal with very urgent issues. The response time should be optimal if the issue requires Red Hat Support. 

My company is a utility company. Outages are a major issue for us. A faster response time is very important to get the applications back up so we can keep up with our production time. Red Hat's documentation is always really good.

As a software developer, documentation is very important to me. The solution should provide better documentation.

The solution is very stable.

The product is scalable. We're able to provide as many VMs as we like. We never run into an issue with how many VMs we are provisioning.

Support can always be improved. I rate the product’s support an eight or nine out of ten.

Positive

The solution can get pretty pricey depending on how many machines we're licensing but for a good reason.

We purchased the solution from Red Hat. We use Packer by HashiCorp to build our templates. I am a junior developer. I have been employed with my company for about five months. I don't know the initial issues that led to us choosing Red Hat Enterprise Linux as our Linux solution. I speak from a developer’s perspective because I deal with Ansible.

The product has really good built-in security. The product provides good support, which helps us manage downtime and get the service back up and running, thus producing more money.

Overall, I rate the product a ten 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 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.

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.

As a whole, our organization is using it on Bare Metal on-prem and the private cloud, and then also in more than one public cloud environment. We probably have all three cloud providers. We definitely have Azure and Google Cloud. The environment that I support has about 40 apps in one cloud or another, but the organization as a whole definitely has hundreds of apps in Google Cloud or Azure. They're predominantly in Azure. The Google Cloud adoption is pretty recent compared to our Azure utilization.

I'm supporting a capital markets environment. A substantial portion of my environment is still Bare Metal at Colos. I'm sure on the application side, there's plenty of JBoss in our environment. There have been recent conversations around OpenShift on-prem that I'm working on, and our enterprise cloud teams are looking at or are using ARO in the cloud. In the next year, our use of the Ansible Platform will go from zero to full throttle as quickly as we can make that happen. We found the event-driven Ansible very interesting.

They've helped us work on employing technologies suitable to our various use cases. We're pretty slow adapters of containers, but that seems to be changing fairly quickly at the moment. That certainly gives us portability for workloads. They helped us with some aspects there, and they've helped us with a lot of automation conversation at the summit this week as well around Ansible.

When it comes to resilience in terms of disaster recovery, the operating system is robust. If it fails, it's probably an app issue. The majority of work in any of our DR scenarios is dependent on whether we have got cold standby or hot standby. If it's hot, the data replication is already there, and things are already spinning. Maybe it's on or you turn it on. Other times, you may have to start up something. Nearly all of those things are application architecture decisions as opposed to dependencies or things from an OS perspective, but in terms of the ecosystem for managing our Linux environment, using Satellite and so on has been very good.

I prefer it to Windows because of the level of configuration, level of control, and the ability to see the performance of processes on a given system. I prefer the control over logging and the ability that logging gives you to investigate a problem.

Its community is also valuable. It's open source, and Red Hat-supported streams are also valuable.

The level of communication we've got with them is fantastic. 

The integration with the apps and support could be better.

A colleague was talking about having some recommendations for the Ansible Cloud on the console and having some way of identifying your dev or prod path and whether you've got read or execute access to a playbook. There were different things like that, and they made a lot of sense, especially if you're in a dev or prod environment because mistakenly running something in prod would be a huge issue. There could be something that Red Hat configures, or there could be a text field where organizations can add labels to a part of the console to distinguish that for themselves. Those would be things that would be useful. I can't imagine it's hard to implement but being able to know which environment you're in matters a ton.

As a part of my professional career, I've been using it since 2004. I joined my current organization in 2018. It has been almost five years since I've been working with Red Hat Enterprise Linux in the security environment of our organization.

It's stable. We rarely have our systems crashing.

It's pretty easy and getting easier. It's not an OS issue. In terms of scalability, even while running our trading apps, we don't run into limitations related to the OS. Our limitations are more hardware-defined, and even then, we're running Red Hat Enterprise Linux on servers with eighty cores and almost a terabyte of RAM, and the OS doesn't have any issues.

Their knowledge base is great. There are lots of times when we don't even have to open a support case because we find what we're looking for.

I've spent a lot of time with the Red Hat account team over the past nine months. They've helped me understand products. They've helped develop the skills of my team. They've helped us with technology conversations with other parts of my organization. They've been hugely supportive of the technology conversation we're having with other parts of the bank.

They've been over and above the expectations in most cases. I'd rate them a ten out of ten. I don't know if it could be better. It has been extremely good. They've been extremely helpful in reaching out and figuring out what they can contribute. The account manager that they have working with us is a former colleague, so it's a really smart decision because we have a very good relationship with the guy. He knows our environment. It has been extremely positive.

It's a growing relationship with Red Hat. We have been using Red Hat Enterprise Linux for a very long time, and I don't know if we can even compare it to the other OS vendors, but having the account team working with us with that level of experience with our environment helps them work with us. It helps us accomplish what we're trying to do. It has been a very good partnership.

Positive

We get our licenses directly through Red Hat.

We haven't used the image builder tool or insights, but it's something that we might explore in the coming months. 

I'd rate it a ten out of ten. It's very customizable and very supportive. It never seems to crash. There could be better integration with apps, but from an OS perspective, it's excellent.