I provide consultation to clients for their mission-critical applications. Its primary use case is running containers and microservices on Springboard.

My customers use versions 7.2 or 7.3. I have used versions 8.2 and 8.4. I have tried version 9, but I use version 8.4 specifically because it supports HighPoint RAID for storing the data, whereas the client applications run on the much lower version.

There are benefits in terms of price, security, and stability to reduce the risk of applications going down or something like that. A vast majority of systems are on Red Hat Enterprise Linux than on other distributions, which is another benefit.

Red Hat Enterprise Linux helps to achieve security standards certification. They use it in the PCI DSS segment, so it enables the applications to be compliant with all these security aspects.

Red Hat Enterprise Linux is very stable. It has been in the market for many years, and it is used by large organizations.

Their documentation and knowledge base are valuable. As an individual developer, whenever I have problems, it is easy to find the information. Their knowledge base is seamlessly integrated with the software. Whenever I have a question, it directly takes me to the knowledge base. It is well documented.

It supports scripting very well. Everything is scripted. A snapshot is taken in the VM, and the script is applied. It lends itself to better security and governance processes.

Its installation on a RAID or cluster system is something difficult. There are specific teams working on that. The GRUB configuration is also a little different from the other Linux distributions. 

In terms of additional features, as technology keeps evolving, the product will also have to evolve. For example, Microsoft Windows has come a long way. In Windows 11, there are so many features that are fundamentally the same as the oldest version, but there are other aspects or processes that have improved. macOS has also evolved over time. Similarly, in the Red Hat Enterprise Linux that I used in 2003 and the one that I am using now, some things are the same and some things have changed. Red Hat can continue to engage clients, understand the use cases, and update them.

I have been using Red Hat Enterprise Linux since 2002 or 2003. Red Hat has a vast variety of products. I have only been using Red Hat's operating system. I have not used Red Hat's other products.

It is very stable.

It is scalable, but I do not have experience in building hundreds of systems on a VM.

I have not used their technical support at all. I only use their documentation portal for self-support. Our production support team interacts with Red Hat's support team.

As a developer, I use both SUSE as well as Red Hat Enterprise Linux. My personal preference is Gentoo, but no one runs Gentoo on a production system. Gentoo is better in terms of customization. You can choose what you want.

I am not directly involved in its deployment, but I am planning to build an application. At that time, I will be deploying it myself. In the organization where I work as a consultant, there is a segregation of roles. There is a production support team, there is a development team, and there is a DevOps team. I am a part of the development team.

Its initial setup is straightforward. It is not complex. It also depends on the architecture, high availability, etc.

In terms of deployment, earlier, it was on-prem, but now, it is on the cloud. My client runs about 150 VMs on the cloud in the production, staging, and QA environments. Most of the things have been consolidated into VMs. The migration is complete. It was not that complex.

I have not measured that, but it should pay back for itself easily. The ROI should be reasonable. The cost over a period of time should be minuscule. As compared to other OSs, it is better to go with a big, known, and trusted vendor.

As a developer, I pay around 10,000 Yen, which is around $100 per annum for support. SUSE and Red Hat are typically the same without standard support. The pricing is not a big deal. Enterprise customers will pay for the support. Enterprises have the money for one or two products like this that are reliable and supported.

As a consultant, I advise customers to go for support. You mitigate risks by having support. For your personal usage, you can manage without support, but when it comes to the enterprise level, you need to delegate things to people, and it should be through the proper channel. You need a proper point of contact.

I would advise following the best practices recommended by Red Hat. It will minimize the downtime of the application or system. Partner with the vendor and get that support. Know the business case and build a strong relationship with the vendor. Trust them and tell them your use case, and they will come up with the best solution possible.

I am not a big authority on Red Hat or other Linux or Unix products. Only recently, I have been exposed to the concept called hardening and penetration testing. I do not know whether Red Hat provides a hardened version of the OS. My basic distribution is Gentoo which provides a hardened version of Linux. On the client side, the organizations we work with have different departments, such as the security department and the compliance department. For security, they work with various options that are available. For penetration testing, we engage a penetration testing consultancy company once a year.

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

My organization has different departments. In my department, we mostly work with containerization. I am using Red Hat Enterprise Linux as a part of OpenShift. I use the basic package and base image of Red Hat Enterprise Linux.

For scale-up in our platform, we use CoreOS as the master, and for the workers, we use the Red Hat Enterprise Linux service. From OpenShift version 4.10 onwards, we cannot use Red Hat Enterprise Linux 7 worker nodes. We were using Red Hat Enterprise Linux 7 worker nodes, so we upgraded to Red Hat Enterprise Linux 8. 

For OpenShift, there are some recommendations from Red Hat in terms of what needs to be used for the control plane and what needs to be used for the worker nodes. When you are using CoreOS and Red Hat Enterprise Linux worker nodes, there are some difficulties in managing them. For example, when you upgrade OpenShift, you need to upgrade two times. The control plane is upgraded separately because it uses CoreOS. The control plane has a lot of certificate updates that will in turn be updated on the worker nodes, so you have one restart of all worker nodes, and then when you need to upgrade your worker nodes, there will be one more restart. 

Overall, you have two reboots in your production environment, which is an issue, but it is related to your choice of product in your environment. We have this issue because we opted to use Red Hat Enterprise Linux 7 or Red Hat Enterprise Linux 8 worker machines, whereas Red Hat recommends using CoreOS because it is pretty fast in terms of rebooting and functionality. When you upgrade the control plane, that itself will update the worker nodes, so you are done in one shot. When you need to upgrade your Red Hat Enterprise Linux machines, you need to use the Ansible Playbook. You can then upgrade to Red Hat Enterprise Linux 7, 8, or any other version. Regardless of the versions, you can upgrade the operating system and the OpenShift version. For this purpose and for some ad-hoc activities, we are using Ansible Playbooks.

For us, its security, management, stability, and hardening are most valuable. All of these features are better in Red Hat Enterprise Linux as compared to Microsoft Windows.

Red Hat Enterprise Linux is very good in terms of risk assessment. It is also good for maintaining compliance. It is better than Microsoft Windows.

From the administration perspective, I do not have any issues with Red Hat Enterprise Linux. For me, it is more convenient than Microsoft Windows.

My organization has been using Red Hat Enterprise Linux for a long time. They have been using it before I joined the organization.

It is pretty good in terms of stability. It is a stable product. I would rate it a nine out of ten in terms of stability because sometimes the packages can have bugs.

Its scalability is good. I would rate it a nine out of ten in terms of scalability.

We never encountered any issues while using OpenShift.

I have mostly been working with Red Hat Enterprise Linux. 

I have been involved in the deployment of OpenShift. It is pretty straightforward. We just need to get the licensing, and we just need to create a pool for our containers session in Red Hat Satellite. We can do the configuration from there. It does not take long because we are adding the nodes to OpenShift. During the scale-up process, we only need to subscribe to the nodes with the Red Hat subscription. It does not take much time. If we have a good spec, the scale-up would not take much time. It would take less than twenty minutes. It is pretty fast.

In terms of maintenance, when we have the bug report, we need to do the security assessments. Over time, there might be some bugs related to some packages. At that time, if it is critical, we will be scheduling a maintenance activity on our platform. 

Red Hat provides high availability from the application perspective. You get high availability when you are using OpenShift, so when you are doing a maintenance activity on the OpenShift side, there would not be any downtime. The high availability is very good. For the end-users, there would not be any application outages if you configure your application with proper replicas. They would not even realize that there is a maintenance activity happening to the underlying workers.

It was implemented in-house.

We did not evaluate other solutions. Red Hat Enterprise Linux is the choice of most of the companies.

If you want to integrate with OpenShift or build an OpenShift cluster with the master Red Hat Enterprise Linux and worker Red Hat Enterprise Linux, you can do that, but you need to plan your upgrade or maintenance activities. It would be better if you choose CoreOS for both. CoreOS would be a better choice in terms of maintenance activities or upgrade activities in the future. If you cannot afford that, you can go with the Red Hat Enterprise Linux operating system, but you need to do two upgrades. You first need to upgrade the control plane and then you need to separately update your worker nodes. That is the only thing you need to keep in mind.

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

We use Red Hat Enterprise Linux mostly for development.

We use Red Hat Enterprise Linux with Git apps in our closed environment to develop and run scenarios.

Red Hat Enterprise Linux's documentation could be improved. Sometimes when you call up support to have that Red Hat answer, they send you back a Reddit or Google link. I can Google or go to Reddit, but I want an answer from Red Hat.

I have been using Red Hat Enterprise Linux since it started back in the 1980s.

I rate Red Hat Enterprise Linux a ten out of ten for stability.

I rate Red Hat Enterprise Linux a ten out of ten for scalability.

I rarely call Red Hat Enterprise Linux's support, but when I do, they send me a Google link.

Neutral

Since I've been deploying Red Hat Enterprise Linux for so long, it's not complex for me. Once we configure our kick start, we power up a new system, attach it, and it builds it.

We implemented Red Hat Enterprise Linux directly through Red Hat.

We have seen a return on investment with Red Hat Enterprise Linux concerning the ability to develop what we need, what we do, and our scenarios. The solution saves us man-hours, and man-hours equals money.

We cannot use Red Hat Enterprise Linux on the cloud because I work as a contractor for the government, and all our development is in a classified area where we can't touch the internet at all.

In the last quarter, Red Hat Enterprise Linux products like Satellite Server and OpenShift stood out because of their ease of administration. I do system administration. When my customers need something, assisting them with these products is easier than giving a long configuration of YAML.

I like Red Hat Enterprise Linux's built-in security features. We use their SCAP features when we do our kickstart and build it.

We were using Docker, and the Docker swarm was trying to get all the containment. We're now switching to Podman and getting our developers to learn that more so we can give them the ability to kick off containers.

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

We deployed Red Hat Enterprise Linux on-prem and in the cloud as a fallback.

We are a private cloud provider and we host Linux ourselves because they are tough to manage.

We offer our customers the option to host their Red Hat Enterprise Linux on Azure or on our private cloud.

Red Hat Enterprise Linux's built-in security features help simplify risk reduction. Red Hat offers a subscription service that provides critical security updates within 24 hours. The service also includes an excellent database of known security vulnerabilities. If a CVE identifier is known for a vulnerability, it can be entered into the web interface. The web interface will then indicate whether Red Hat Enterprise Linux is affected by the vulnerability and what steps need to be taken to fix it. The fix will be included in the next security update. This is a valuable security feature that helps organizations to stay up-to-date on security patches and mitigate risk.

The portability of applications and containers built on Red Hat Enterprise Linux is beneficial for keeping our organization agile. Red Hat Enterprise Linux 8 and 9 include Podman, a newer software similar to Docker. Podman was built to address the problems that Docker had with creating and running containers, and it also includes the support of Red Hat. There is a good synergy between Red Hat and Podman.

Red Hat Enterprise Linux has helped improve our organization. We provide a service to our clients, which they pay for each month. This service includes our support. Red Hat Enterprise Linux is a stable operating system, so we do not have to provide much support. When we do need to provide support, it is usually for an application, not for the operating system.

I can build with confidence and ensure availability across physical and virtual cloud infrastructures using Red Hat Enterprise Linux. I have been using Red Hat Enterprise Linux on-premises since 2008 without any problems. It is easy to automate. Virtualization is always present, so I work with virtual machines. Red Hat Enterprise Linux is very easy to deploy on a virtual machine. We can create a virtual machine, and if we are working with VMware, we can create a template to use for new systems. There is no need for a classic installation.

The updates are the most valuable feature. In the past, we had 800 or 900 Linux systems with Red Hat, and all of the systems were updated every night. In the 14 years, we have only had ten issues with the updates.

Red Hat Enterprise Linux has a good configuration.

Red Hat Enterprise Linux is secure but the security always has room for improvement.

Scaling can be complicated and has room for improvement.

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

Red Hat Enterprise Linux is stable.

I give the stability an eight out of ten.

I give Red Hat Enterprise Linux a seven out of ten. 

Updating Red Hat Enterprise Linux from version 8 to 9 is a complex and time-consuming process. It is often easier to install a new server with Red Hat Enterprise Linux nine and migrate our data and applications. However, if we only need to resize the CPU or memory of our existing server, we can do so using the hypervisor without having to reboot.

Red Hat support is fast, and they are capable of answering 90 percent of our questions.

Positive

We previously used Debian, Ubuntu, and SUSE Linux. In our case, if we wanted a conservative Linux system that did not have the newest version, these were perfect systems. However, if we wanted to install them on our laptops or on our clients, they were the wrong solution. We switched to Red Hat Enterprise Linux for the Red Hat support. Debian also offers its own support. Ubuntu does not offer direct support, so we were required to order it through another company. SUSE had other problems that we did not want to deal with. Red Hat Enterprise Linux support has been very helpful to our back-end admins.

The initial setup is complicated, but with Red Hat Enterprise Linux nine, there is a graphical web interface where we can create a new image every week. We have created a golden template that enables us to update the image every month and upload it to both our private and public clouds for usage. 

The deployment time depends on whether we have a template or not. With a template, deployment can take between five and ten minutes. If we have to install the software, the time it takes depends on our internet bandwidth. Ten gigabits of bandwidth can take around 15 minutes to install.

The implementation was completed in-house.

As a provider, we must follow a different licensing model. We charge €2,000 per system for three years. Each month, we provide Red Hat with a number of new and old systems. Red Hat then invoices us based on the number of systems in use that month. This only applies to our cloud customers.

I give Red Hat Enterprise Linux a ten out of ten. Red Hat Enterprise Linux is the best thing I have.

We always install a minimized Red Hat Enterprise Linux system for our customers. If they require more features, we provide them as requested.

Red Hat Enterprise Linux is the most perfect OS I have ever worked with. It is nice knowing when we have to use the OS and when we don't.

All Linux solutions are open source, but Red Hat Enterprise Linux is a commercial product that includes support and frequent updates. Red Hat Enterprise Linux can be downloaded for free, but it is not recommended to use it without a subscription, as it will not receive security updates or bug fixes. Red Hat reinvests a portion of the subscription revenue back into open-source projects, making it possible for other organizations to use these technologies for free.

Maintenance requirements depend on our needs. If we only want to have a server and install updates every night, no additional maintenance is required. Red Hat Enterprise Linux does not require any special support. However, if we want to ensure that the system time is always correct, that all updates are installed within a month, and that the system reboots after updates are installed, we will need to perform some additional maintenance tasks. These tasks can be automated to ensure that our system is always running smoothly. We currently have three people for the maintenance. We currently have 900 systems.

I recommend evaluating multiple Linux solutions and conducting a proof of concept because, although Red Hat Enterprise Linux is a great operating system, it may not be the best choice for every organization. I do not recommend using Red Hat Enterprise Linux on a new laptop because the versions included in Red Hat Enterprise Linux are typically two to four years old. This is because Red Hat Enterprise Linux is designed to be a stable OS, and newer versions may not have been fully tested and may have issues. If we have a server or software that is certified for Red Hat, then I would always recommend using Red Hat Enterprise Linux.

My main and only usage of Red Hat Enterprise Linux is for the on-premise workload. We use it for running Red Hat Ceph Storage and running automation using Ansible. Other than this, I use it for doing any auto test that I would like to do on a Linux-based machine.

From a security perspective, the most valuable feature is SELinux. SELinux provides good security. It's doing a good job of protecting my real estate.

The portability of applications and containers built on Red Hat Enterprise Linux is great.

It has its own ups and downs. Most of the time, it's pretty stable, but sometimes, you'll find some weird bugs that could affect the availability of your running machine. Red Hat can improve its operating system by making it better from the quality assurance perspective. Users do find bugs, which they, of course, shouldn't encounter. A better QA would probably make the job a lot better. It would make the product a lot more stable than it's today.

I've been using Red Hat Enterprise Linux for over three years.

It has its own ups and downs. The operating system itself is pretty much stable, but there could be some bugs that could affect your availability. While running the Red Hat Enterprise Linux operating system, I did experience some bugs from time to time that did affect the availability on my machine.

Overall, it's pretty stable, but when you do something more hardcore or special, then its stability could be affected. I can't recall anything that I faced in the last few weeks or months, but as you go around production with Red Hat Enterprise Linux and have lots of machines running on it, you can get stability issues or kernel issues. A machine might suddenly be rebooted for no reason. That's my experience with Red Hat Enterprise Linux's stability.

It's deployed at multiple locations. Approximately, there are 200 people using this solution.

The support in Israel from the guys sitting in Israel is great, but when contacting the support engineers across the globe, the support level just decreases, and the reliability decreases as well. The support guys locally in Israel are great, but the support guys worldwide aren't that reliable. Overall, I'd rate them a seven out of ten.

Neutral

I used Ubuntu and Fedora, but mainly Ubuntu. Ubuntu was a great operating system. We had to change from Ubuntu to Red Hat Enterprise Linux due to subscriptions. The enterprise had more and more need for container orchestration, so we ended up purchasing the Red Hat OpenShift container platform, and the use of Red Hat Enterprise Linux in the organization grew significantly.

The security features of Red Hat Enterprise Linux are aligned with the entire industry. They do not have any higher advantage over other competitors, such as Ubuntu from Canonical, so security-wise, it's okay.

It was pretty much straightforward. Deployment of the Red Hat Enterprise Linux operating system didn't take longer than two days.

It was deployed in-house. Three to four people were involved in its deployment.

In terms of maintenance, it just works unless you do anything special with it.

It's pretty expensive, but I'm not familiar with the pricing of other vendors for their operating systems. I'd rate it a seven out of ten in terms of pricing.

Red Hat Enterprise Linux's main advantage is the support that you get by purchasing their subscriptions. 

We looked at OpenSUSE, but we eventually ended up with Red Hat Enterprise Linux because of the support that Red Hat has in my country. In Israel, Red Hat is a lot bigger than OpenSUSE, so we ended up going with Red Hat Enterprise Linux because of the available support in the country.

If you're evaluating this solution, I'd recommend having your own architects discuss your architecture with the local Red Hat personnel in your state. Red Hat Enterprise Linux is a good product, and it could be even better if you know how to integrate it based on the preferences of your organization. So, my advice would be to have your guys discuss your IT architecture with the local Red Hat people and then decide how to specifically integrate your IT infrastructure with the Red Hat software.

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

We are running databases and applications on it. We are also using the Squid proxy server, NGINX, and Apache, so we are running multiple services on the servers.

We are using Red Hat Enterprise Linux eight and nine. We also use Red Hat Satellite and Red Hat Ansible Tower.

I've mostly worked with the telcos and banking sectors, and they mostly have on-prem setups. We do have a hybrid environment where we have multiple machines running on AWS. I am based in Saudi, where they are using another cloud called Din. They are running Red Hat Enterprise Linux on Din as well.

Their trainings should be free.

It's more stable than the other operating systems. That's why everyone is using the Red Hat Enterprise Linux platform instead of Windows on the server side.

They regularly send us updates regarding patches and security vulnerabilities. We patch our servers quarterly. Mostly, we do patching every three months. They always send us updates on our official email, so it's quite good.

It would be very good if we can easily migrate from CentOS to Red Hat. We are about to move from CentOS to Red Hat. It would be great if they can give us a free version. Otherwise, we need to purchase licenses, which are quite expensive.

I've been using Red Hat Enterprise Linux for five to six years. I have only been working with Red Hat Enterprise Linux over these years.

Its stability is quite good. I'd rate it a nine out of ten.

I'd rate it a nine out of ten in terms of scalability. It's being used in the banking center, and they are running their applications and databases on it. 

We have LVM configurations, so according to the application, we can increase the disk size. The environment is quite good for my use.

Their support is quite good, and they're responsive, but they first send us to the platform to check the issues. They don't provide direct support immediately. For a new engineer, it can be quite difficult. It would be good if they put us directly on the call in case of an emergency.

Some of the newer engineers require support in a quick manner. Those of us who have experience of six to seven years don't require the support, but in the beginning, we required support, and their support was quite good.

Positive

The product selection depends on the company. Telco companies have the budget, and they are using licensed products, whereas small companies usually use the free versions of Linux. They go for Oracle Linux, CentOS, etc.

We are using CentOS and Ubuntu on some of the machines. The company wanted to go for a free product, but I told them that for any support in the future, we need a licensed product, and they are now migrating to Red Hat Enterprise Linux.

It's best in terms of security features. We configure the templates and then we implement the CIS controls, security features, and complete patching of the server.

In terms of maintenance, Red Hat provides us with the details about the security vulnerabilities, and the engineer needs to implement all the security on the servers.

We did it on our own.

We haven't seen an ROI.

From a management point of view, it's quite good, but everyone is complaining that it's more expensive than the other operating systems.

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

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.

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.