Red Hat Enterprise Linux (RHEL) Reviews

I am a Federal Contractor. Red Hat Enterprise Linux is one of the FedRAMP-approved operating systems, so the government is comfortable with using it. That is why we use it, even though it is a bit outdated. Most of our software runs on Red Hat Enterprise Linux because we work in Identity Access Management. For example, Oracle Identity Stack runs on Linux, so we have to use Red Hat Enterprise Linux. We follow very strict security protocols, and we use Ansible to enforce them. Red Hat Enterprise Linux is the easiest way for us to do this.

Red Hat Enterprise Linux is a trustworthy and highly scalable operating system. The federal government needs an operating system that they can rely on, with enterprise support and long-term service. As well as being stable and well-known within the community.

I have not yet experienced a disaster recovery scenario, but resiliency is important, and risk is very reliable. The auto logs are very clear. Additionally, with those support communities, it is straightforward enough to understand what we are looking for and to eventually resolve the issue.

I actually like the in-place upgrade that Red Hat Enterprise Linux offers. It has made our upgrade process from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 much easier than we originally thought. 

I know that many people prefer in-house support, but I personally prefer Red Hat's support. It is easy to get in contact with their support team.

Even though it is not directly related, the fact that Red Hat Enterprise Linux and Ansible are closely related makes it easier for us to move forward.

The package management, repository, and satellite repository are easy to use.

I am a bit biased because my client is air-gapped. This means that we cannot connect to the internet, so all of our operations are disconnected. I would like to see better support for disconnected operations. For example, the in-place upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 initially relies on a lot of online resources. This makes sense, but it would be nice for a consumer or integrator like me to be able to say, "Hey, we need an offline solution so we can upgrade our government clients on-premises." Red Hat does provide instructions on how to create a repository, but the instructions are not very clear. This leaves us scrambling to figure out why we are missing a repository in our satellite image. Red Hat should provide a way to mirror repositories or at least provide a solution for us to bubble up packages throughout the entire process.

I have been using Red Hat Enterprise Linux for four years. We started with Red Hat Enterprise Linux 6, and we upgraded to Red Hat Enterprise Linux 7 in an airgap environment. We are currently in the process of upgrading to Red Hat Enterprise Linux 8.

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable. It is deployed in a 10,000-plus enterprise company.

The support team is always direct and easy to find. Their answers are so helpful that I have not yet had to call them. I also appreciate how they approach troubleshooting. They don't assume that you're doing anything wrong. Instead, they try to educate you on how to fix the problem. In my experience, the support team has always been very positive.

Positive

I have experience with most Linux operating systems, including distributions like Apache, Debian, CentOS, Fedora, and others. From my perspective, Red Hat Enterprise Linux is not necessarily the top standout product, but I know that it is a product that I can rely on. It is the standard image that enterprise users in the community will use. We can rely to a degree on the standardization of how packets are used to support it. However, it does not stand out to us as much as the other products. Nevertheless, I know that it will have a positive partnership with us. Red Hat Enterprise Linux is a more suitable operating system for enterprise environments in terms of stability and reliability.

We are currently in the process of reviewing our initial solution for upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. The in-place upgrade for the airgap environment is an area where we are still struggling to understand the documentation. However, Red Hat has been very supportive and has offered us pathways to move forward. We do not have much to say at this time, as we are still in the middle of the process.

When we upgraded Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7, it took us around six months due to external factors not related to Red Hat Enterprise Linux.

Our client has a direct subscription to Red Hat.

I give Red Hat Enterprise Linux an eight out of ten. I am not a firm believer that everything is perfect right out of the gate. Everything can be improved. I am a little biased. I wish there was better support for offline environments. I understand that I am in the minority in this case, as everyone is connected to the internet now. However, as a federal contractor and integrator, we have requirements that we must meet. It is not fun having to download binaries offline and then figure out how to set up our own repository. These are not straightforward tasks like Red Hat telling me what to do. We just wish it was easier to do things like patch management. Perhaps there could be more support for air gap environments. These are not environments where we can temporarily connect to the internet. They have never seen the internet.

Depending on our customer's environment, sometimes they have GovCloud, but we still use Red Hat Enterprise Linux images there. Sometimes the customer can't use that so we use the offering from CentOS. But we still try to match it with CentOS.

The reason why some clients don't use Red Hat Enterprise Linux on the cloud is not because of security concerns. I think it's more about cost and their current contract situation. They need a low-cost, open source alternative, and our recommendation would be CentOS. However, many clients are not ready to pay for the enterprise edition of Red Hat Enterprise Linux, so they may choose to scale back their plans.

I have not used the Red Hat Enterprise Linux knowledge base strictly. I have only used the Red Hat Enterprise Linux support.

Clients who use Red Hat Enterprise Linux on the cloud, typically use AWS GovCloud. As a government integrator, we strive to design our solutions in a way that does not lock our clients into any specific cloud provider. This is why we chose Linux, as it can be run on any cloud platform. This flexibility is important to our clients from a price contract perspective. For example, Amazon provides Kubernetes services, among other things. We try to figure out open source solutions or at least architecturally determine them and provide them to our clients. For example, we can tell them that they can move all of their GovCloud data to Azure or Google Cloud. Government agencies really like Amazon right now because it is FedRAMP. However, for other classes that are not government or commercial, we try to introduce them to the CentOS perspective so that they can get a taste of the upstream.

We do not use the image builder tool provided by Red Hat. Instead, we use the one provided by Amazon. We take a base image, coordinate it with Ansible, and provide it to any environments that have used the cloud. For on-premises solutions, we strictly use manual processes.

I don't have a perspective on the golden image, which is at least with our client. The parts that we use are always evolving, so we don't really maintain the golden image. We do have a relative backup of what we deployed to, but we don't necessarily have a strict golden image.

Migrating workloads between the cloud and the data center using Red Hat Enterprise Linux is not entirely applicable to us. We did migrate from on-premises to the cloud at one point, but migrating from Red Hat Enterprise Linux on-premises to Red Hat Enterprise Linux in the cloud was not a concern for us. We knew it would be stable and fine. The main concern was migrating our customer data from our enterprise to the cloud.

If someone is looking for an open source cloud-based operating system for Linux instead of Red Hat Enterprise Linux, I would like to eventually drive them over to Red Hat Enterprise Linux, but I would recommend starting with CentOS. CentOS is a good gateway OS because it is very similar to Red Hat Enterprise Linux, and the knowledge transfer between the two is very straightforward. This makes it a good choice for users who are new to Linux, or who are looking for an OS that is compatible with Red Hat Enterprise Linux.

I use it as an EC2 Web Server.

It was needed for FedRAMP Moderate compliance.

The ready-to-go AMI is a valuable feature.

It does not pass the RHEL8 STIG standards without a lot of extra work.

I have used the solution for one year.

I previously used CIS RHEL 8 Level 2.

Check it to verify costs.

I did not consider any alternate solutions.

It does not pass the RHEL8 STIG standards without a lot of extra work.

In the past, we ran almost everything on Red Hat Enterprise Linux, but now we use it for applications that are only supported on Red Hat Enterprise Linux, LDAP servers, and other stuff that runs better on Red Hat Enterprise Linux. We've migrated the rest to Ubuntu. We don't use it for containerization yet, but I'm learning about OpenShift. 

We are considering Red Hat Enterprise Linux for some AI projects at the university, some for researchers and research groups, and others for administration or student enrollment. There are many opportunities to use AI. 

Red Hat Enterprise Linux has made us more agile, and more applications were ready-made for Linux. It was also easier to maintain the environment. 

It enabled us to centralize development, but we had some issues with cost, so we migrated off. We use the Linux security heavily.  I'm unfamiliar with the new security stuff incorporated in Red Hat Enterprise Linux, but SELinux and all the security features are good. It doesn't particularly reduce risks, but there are some added layers of security for internet-facing applications we like

Red Hat Enterprise Linux been stable, and we could do anything we wanted with it. OpenShift is a concise environment, and it is one of the most stable Linux distros on the market. 

The only issue for us was the cost. Red Hat Enterprise Linux is expensive.

We have used Red Hat Enterprise Linux for a long time. We started using it on version 4, and now we are on 7, but we migrated most of our environment to Ubuntu a few years ago.

It is stable and mature.

Red Hat Enterprise Linux can scale to fit our needs. 

I rate Red Hat support nine out of 10. I was happy with it. Their expertise and technical knowledge were good. It was one of the best support experiences I've had. 

Positive

When Oracle acquired Sun, we migrated from Sun Solaris to Red Hat Enterprise Linux. It wasn't easy, but it was a light effort.

Red Hat Enterprise Linux is expensive.

I rate Red Hat Enterprise Linux nine out of 10. If you're purchasing commercial Linux, I would look into Red Hat Enterprise Linux because it's highly stable and mature overall. It's a true enterprise OS. 

I use Red Hat Enterprise Linux to control my Docker systems and build and run containers on them. I also use it for a tokenization project I'm working on.

Red Hat Enterprise Linux (RHEL) has improved the availability and security of our systems. The knowledge base, Wiki forums, and other resources are very helpful in simplifying my daily operations. We realized the benefits immediately after deployment. 

The most valuable features of Red Hat Enterprise Linux are the availability, file system performance, and overall system availability. The kernel is more secure than my previous operating systems, such as Windows.  Red Hat's knowledge base is helpful. I consult it several times in my daily work. I can ask questions on the forums and get help in my daily operations.

Using Red Hat Enterprise Linux's image builder is easy. I can use GitAI to pull any image I want to build on my system and reach into it using Red Hat. I use Convert2RHEL to publish my work on tokenization. I'm publishing more than 70 prints on my system daily, and saving this file. It's easy to use.

There are performance issues with the response time when accessing the console, but I'm unsure if that's Red Hat Enterprise Linux's fault or if it's due to the lack of CPU or memory on our machines. The enterprise interface could be improved. I can only use the keyboard to transfer files from one system to another. I want to use my mouse on the interface, not just scroll up and down. I would also like my logs archived as an RAR and sent to me. 

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

Stability is critical to us. Red Hat Enterprise Linux ensures our machine's availability and reduces the need for frequent restarts.

I have not contacted customer or technical support myself. Our infrastructure team handles any contacts with Red Hat support.

Positive

I have used Ubuntu before. Red Hat has a more robust knowledge base, and finding solutions to any problem is easier.

The infrastructure team handled the initial setup. I'm a software engineer working on my applications. The infrastructure team builds the machine, and I only use it. It was relatively easy, depending on the complexity of the deployment configuration. After deployment, we have maintenance on our machine if there are new patches to deploy. I have three machines, and each one is identical, with the same containers, so I don't need to do maintenance on our machines more than once monthly. 

It is important to use the knowledge base and familiarize oneself with key commands to gain more about Linux and ease its usage.

I'm using the Red Hat Platform with Open Stack and an RHEL product for storage. The use case is performance IOPS for Ceph Storage, which depends on a bare-metal RHEL server. 

For my security customer, we get greater than 90 percent uptime. RHEL helped us achieve security certification. It helped my end-user pass their security assessment. RHEL's built-in security features scan the third-party layer in the OpenStack and RHEL platform to assess the SSH and firewall security or patch updates from the RHEL platform and reset OpenStack. Security is the number one priority for my end user. They want to prevent hacker access from the outside. 

RHEL supports the hybrid cloud strategy. The goal of using a bare metal server has been to improve availability and database performance. The OpenStack platform uses network capability to improve database performance.

RHEL improves database and application performance for my end users. The application can collect regional and national data for my end user, a strategic customer in Indonesia.

I am confident in the managed services RHEL provides in terms of the OpenStack, Ceph Storage, and OpenShift container-based products. If there are any problems with the RHEL platform, Open Stack, Ceph Storage, etc., I can raise the issue to RHEL global support. 

For the past twenty or thirty years, Red Hat has reengineered its product from bare-metal on-prem to the cloud environment. Migrating an RHEL system from bare metal to cloud is somewhat difficult. They could add a fast boot. 

We deployed one side of RHEL in 2023, and we'll deploy the other side in 2025.

When I deploy RHEL for the first time, I try to learn about the performance and tune the performance. 

Scalability isn't an issue. Our customers haven't reported any performance problems from scaling up.

I rate Red Hat support eight out of 10. I have used Red Hat support since 2023. They escalate the ticket based on severity, and if they can't resolve the issue within the maintenance window, they will pass me to another engineer. 

Positive

We previously worked with Oracle Linux. My customer has two divisions. The network decision is focused on accounting database performance, while the IT division uses Oracle Linux. On the network side, the customer uses RHEL products like OpenStack, Ceph Storage, and OpenShift. 

My end user wanted to upgrade from RHEL OpenStack 16.1 to the latest 17.1.3 in April 2024. We also upgraded Ceph Storage and OpenShift. Now, my customer wants a testbed before upgrading to the RHEL version in live production. If there are problems, we open a ticket with global support and or two people will join our remote call. We have it deployed in Jakarta and plan to deploy it to Bandung.

I rate Red Hat Enterprise Linux eight out of 10. I recommend all the Red Hat products, including OpenShift and Ceph Storage. OpenShift Container is a mature product for RHEL portal customers.

The main use case is generating golden images. All the deployments of operating systems and virtual machines on the servers are based on the golden image. The developers and providers can run all the applications on top of those.

Whenever we need to remediate any vulnerabilities, patches are available. These patches are not only for current exploits but also for back-porting for bug fixes and security fixes. These patches are available from the most recent versions to the specific version that we are using.

Red Hat Enterprise Linux has enabled us to centralize development. We have a golden image of the operating system. That golden image sets the standard for all the security policies that we are applying to it. For example, the partition scheme and the best practices that we apply to the golden image are the starting point for all the developers to start working with all the applications and also executing appliances or applications from providers.

We are using Red Hat Enterprise Linux with Podman for containerization projects. Red Hat offers what is called UBI or Universal Base Image. That image is already configured to be secure and have good performance. To start working with containers, we just have to pull UBI as a base for our images and start working on those. It has impacted our containerization project because instead of using Docker, we can use Podman. There is a common container image that is used by the majority of the customers, but I forgot the name of that one. Instead of using that, which is like a very minimal image, we are using UBI because it is already secure. It has the majority of the benefits of our Red Hat Enterprise Linux image but in a container image.

There is portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. That is a very good option to have because you do not have to worry about the underlying system. You just have to worry about your application and have the application running on top of your image based on UBI. It is going to be so easy to have the application running either on a machine with Podman or have the same application running just on top of OpenShift. It is so easy to move a container-based application that can be executed on top of Red Hat Enterprise Linux with Podman or on top of OpenShift. 

Security, packages, and updates are valuable. There is also the possibility to do unattended installations. This way you can define how you want the installation to behave and be configured whenever you do the deployment.

One of the best features is having a tool called OSCAP, which is a tool that is going to allow us to apply security profiles to the golden image. This way, all the security features or policies can be applied in real time. This way, we can follow all the policies that are defined by our security teams.

There are not a lot of areas to improve because the majority of the time, Red Hat is constantly improving it. The only area would be in regards to being capable of running on other architectures like ARM. They are about to release a new version that is available to be executed on ARM architecture.

We have been using Red Hat Enterprise Linux for about a year.

It is very stable.

It is scalable. We have plans to increase its usage.

It used to be better. It is still good as long as you can get in touch with a level 3 support engineer. If you have a trained engineer who helps you with what you need and who understands how to ask for specific details of what you need, you should be good. But, unfortunately, if you start with a simple detail of what you are experiencing and what kind of help you need, you will receive the same response. For example, you are pointed to a knowledge base article, and that is it. The support engineer is supposed to help you with your issue or request, but unfortunately, that is not happening anymore. It used to, but I understand.

We are looking for a support engineer to go all the way. The only way for you to contact support is via the support case system or page. After that, you interact through the ticket or email. You do not have a chance to have a call. If we have escalated a case, it is usually better if you have a person for a proper understanding and proper advice on what you have to do and how to resolve the issue. It could be that you need a new product, subscription, or service, but you do not know that.

Neutral

When I got into the company, they were already using Red Hat Enterprise Linux, but back in the day, I used to have HP-UX. That was a very ancient system. It was Unix-based. It was a proprietary solution. HP-UX was a platform licensed based on the old Unix code that was tightly integrated into hardware built only by Hewlett-Packard. You could not run HP-UX in any other place. You could only run it on hardware created by Hewlett-Packard. The intention with that was to run only on the Itanium architecture, whereas Red Hat Enterprise Linux can run on x86 architecture. It is also open-source.

We have it on-premises. It is in different locations. We are following a strategy to publish the images of the operating system. This way, multiple teams can grab the images and have their own procedures to deploy within each separate environment. We have multiple teams working on developments and they need a base image to start working on all the development stuff. Because they are all independent teams, they have access to a single source of image. This way, they can start working on further customizations and whatever they need.

We implement it in-house.

The ROI is in terms of the time that I have to invest in doing customizations, applying security policies, and fixing the supply to the system, wherever I need those.

The reason for going for Red Hat Enterprise Linux is to improve the time to market. It is so easy to just generate a new image. We can configure it with all the security features and all the libraries and packages we need. We can also configure it with the ones requested by developers. We can do all of that. It is so much easier than what we can do with Windows, for example.

It is very straightforward. We do not have to think much about having to get all the subscriptions related to the Red Hat Enterprise Linux fleet that we have because all the subscriptions came in pairs of CPUs or even for an entire bare-metal server. That way you can partition your bare-metal server into multiple virtual machines, and then you are covered. As long as your bare-metal server is covered, you can roll out any number of virtual machines on top of it. It is very easy to get subscriptions for your bare-metal server, and you can utilize whatever you want.

We evaluated operating systems or Linux distributions created by the community or run by the community only. We evaluated them mainly because of costs.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that they would not have the same team supporting all the operations and all the critical features and patches that they receive with Red Hat Enterprise Linux. They can go with one of the clones, but unfortunately, at the end of the day, the clones are going to deviate from Red Hat Enterprise Linux. With Red Hat Enterprise Linux, you can also create support cases to receive back-ported bug fixes and security fixes, and you get very cool features such as Insights, Satellite, or system roles provided along with Ansible. 

We are currently not using Red Hat Insights but that is an awesome tool.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten. It is an enterprise Linux distribution. It was one of the first distributions to focus on the enterprise. There are others, but Red Hat is the main contributor to the Linux ecosystem. Because of that, it is so stable. It has proper support. It also provides the Linux ecosystem with new features and enhancements.

When we are looking for Linux servers or developers need Linux, we have standardized around Red Hat Enterprise Linux. We do not use Ubuntu or any random flavors of the day. If it is a Linux deployment, it is Red Hat.

It helps with standardization. If someone comes to us and requests a Linux server, we have one product offering. We have a couple of different flavors of it, but people know what they are getting from us. The consistency, reproducibility, and standardization of it have been fantastic.

We are using Red Hat Enterprise Linux on-prem and on the cloud. We have it in Azure, VMware, and on-prem. We have it on bare metal. It is all over the place. Our operations are simpler, more efficient, and easier to handle. Our Linux team now supports one OS rather than a whole bunch of flavors that everyone has brought in. It has just made things more efficient and simplified.

Red Hat Enterprise Linux has enabled us to centralize development. Those developers are now developing on Red Hat Enterprise Linux. Previously, we had people who were developing on Ubuntu and trying to push Ubuntu to production, but we did not necessarily support it. Red Hat Enterprise Linux gave us a clear path to production. Our developers also get an easier experience. They know which OS to use and what they are using from day to day. There is less confusion for developers.

We are using Red Hat Enterprise Linux for containerization projects. It has helped with simplification. We do not have to create too many of our own custom container definitions and do our own thing. We use minimal images and whatever is provided is supported under our subscription. It simplifies things and puts guidelines around things.

Red Hat Enterprise Linux's built-in security features are good when it comes to risk reduction, business continuity, and maintaining compliance. We use Red Hat Satellite to manage our Linux. That makes it all very simple. There is a feature called OpenSCAP. We use it for security scanning. All the features that they provide on top of the base OS make it very easy to manage.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. We know we can rely on that middle layer. We can start with the container and then build on top of that. Having a solid and standard foundation makes it all easy to do.

The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them.

It is constantly improving. It is important to continue to improve. That is another reason I like it. They are using newer kernels, which gives us access to newer hardware. They are already doing that. I cannot pretend to tell them what to do better. They can just keep on doing what they are doing.

Personally, I have been using it for about 12 years. I have only been with my company for about four months, but I know they also have been using it for years.

It is stable.

It is scalable. They define scalability. I am a basic user. I just deploy more VMs if I need to. It is easy to do. Its scalability is great.

They are great. I would rate them a ten out of ten. A big selling point is that when you submit a support ticket, you know you are reaching out to experts. That is great, and that is one of the primary reasons we went with Red Hat.

Positive

In my company, they were using AWX for automation, and we moved them to AAP. For Linux, I was a part of a project to migrate some of the other operating systems over to Red Hat Enterprise Linux. I am on the tail end of the move or standardization to Red Hat Enterprise Linux.

There were a lot of Ubuntu operating systems in the environment, but they had challenges standardizing around it. There were different versions. There was also CentOS, but it was old CentOS. They are naturally moving that to Red Hat Enterprise Linux.

The support and the standardization around it were the main reasons for going for Red Hat Enterprise Linux. CentOS is more of a community thing now, whereas we can call Red Hat and they help us with everything. The support and the enterprise features we needed pointed at Red Hat Enterprise Linux rather than CentOS. It is a better choice for production.

We deploy them from AAP and then we deploy them into VMware. We deploy them into Azure, which is our main provider. We do that all orchestrated through Ansible and Satellite.

We have outsourced support. TCS is a general contractor, but for Red Hat deployments, we generally go with Red Hat Consulting. We just finished a consulting engagement with them for that. I know they have used them in the past prior to me being here. We generally just use Red Hat Consulting.

We have standardization. I know what I am walking into every day. I know there is support behind it. There is the support of Red Hat and the community behind it. I feel confident using Red Hat Enterprise Linux. I might use other Linux operating systems at home, but a lot of the time, there is no documentation for them. There might be three guys in a forum from ten years ago who may have talked about my problem. With Red Hat Enterprise Linux, when I am going to work, I know what I am walking into. I can feel safe and assured using something industry standard that works, and I can get help with it very easily. It makes life a lot easier.

Our total cost of ownership across our enterprise landscape has gone up because we were using a lot of mixed and free open-source solutions. However, there was an extra cost of operations and extra cost of hiring for specialized skills and things like that. With the Red Hat portfolio, I feel that we spend more on subscriptions, and we save in terms of efficiency and operations. I feel that we spent some money to save money on the backend, and I hope that is how it ended up.

I do node counts for the Red Hat Enterprise Linux system. I am gathering data for our decision-makers about how many nodes we need and how many things we need. Once or twice a year, they ask us to true up and find out how many nodes we are using and what the actual consumption is. I then report that, and then the account team usually works on the money part of it. I just work on the count.

We use Red Hat Insights a little bit. I am more of an Ansible guy, and we use Red Hat Insights for our licensing and a few other things. We have not been using Red Hat Insights as much as we wanted to. I know that on the Linux side, they are using it a lot for license count, monitoring, and other things.

I feel we are underutilizing Red Hat Insights. Our account executive has shown how it works and where it is, but we have not committed to it yet. That is coming soon. As we gain more Red Hat products and standardize more, we will have to rely on a single pane like that, so we will be using it more. I know that Red Hat Insights provides vulnerability alerts and targeted guidance, but we are not utilizing it right now.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to go for whatever they find to be the best. My standard for an enterprise solution is Red Hat Enterprise Linux. It works very well, but they have to make sure that it fits their use case. Fortunately, Red Hat Enterprise Linux fits most use cases. They might end up there, but if there are licensing or cost restrictions, there are other free options, such as CentOS. The ecosystem of Red Hat Enterprise Linux is healthy, so I would recommend it, but if they want to use something else, they need to come up with all the standards around that.

I would rate Red Hat Enterprise Linux a ten out of ten. It is my preferred enterprise operating system. Everywhere I go, they are using it. It has been great. There are no complaints.

I work as a consultant for a bank. They were using another type of Linux and facing some scripting issues. We are using Ansible for infrastructure, but they depend on different languages. In this fintech use case, the bank performs transactions between two banks. The transactions were getting stuck, but they detected that the money had been transferred. 

The money comes from the bank. They transport it from the cloud and deliver it to the channels like Visa, MasterCard, etc. The national bank is also involved at that stage, so there is a pause. When we are using auto-scaling, it requires a small amount of time, so your application will have an error. This is a millisecond process. That is the duration. We were looking for issues like bank fraud. You need to conduct an analysis and restart the service. The data is on Red Hat Linux, and we use EKS for containerization. 

We have a hybrid solution combining AWS with an on-premise environment. Moving data to the cloud requires a stable connection because we have multiple systems on-premises and on the cloud. This platform helped us communicate among multiple clouds and our private cloud network. 

Using Red Hat Enterprise Linux enables us to subscribe to other Red Hat services from our portal. We can connect to Satellite with single sign-on logins. We can use the Spring CLI call and the Docker hub. We have a direct subscription.  

Red Hat Enterprise Linux has helped us avoid cloud vendor lock-in. We could easily migrate between cloud services from AWS to Azure if we wanted to. Everything is an SCL, so we could deploy the same thing on another cloud. It's highly useful. We can make a script and move the entire infrastructure. 

The Red Hat Linux comes with Anaconda, a fascinating tool that is useful if I need to connect multiple systems. I also like role-based access. 

Red Hat Enterprise Linux is a little expensive for some customers who don't have the budget. It depends on the client. They can save money by not purchasing some of the added packages and services.  If the client has a budget of $10 million, we can go for the whole bundle. 

I have used Red Hat Enterprise Linux for four or five years.

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable, but it depends on the deployment. 

I rate Red Hat support 10 out of 10. I'm a big fan. 

Positive

I have used Ubuntu, which has its own cloud service. Red Hat Enterprise Linux is a better option if the client has a budget. Red Hat Enterprise Linux can be certified and meet compliance requirements. 

Deploying Red Hat Enterprise Linux is straightforward, but the complexity and time required depend on whether we are deploying on a virtual machine or a desktop. If we have the correct documentation, the total process can be completed in three to five days.

I have used the Image Builder Tool, but in the latest deployment, I pulled down the repository from the Docker hub. We use our own XML file and create the repository. It's a two or three-day design process for Red Hat Linux. We need one data resource for that process and a second engineer on the support side if we want to set up more servers from their on-site services.

It's affordable, but everything costs money. At the same time, everything adds value for our clients.  For example, I was working on a machine-learning project, and they needed more team resources, and all the projects used computing power. By running multiple clusters, the client exceeded the rate for that data. We buy services from AWS, the Azure Marketplace, or directly from Red Hat. 

I rate Red Hat Enterprise Linux nine out of 10. I recommend buying the services in a package if you can afford it. If the client doesn't have the budget, we can find alternatives. It depends on the client's needs.