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.

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

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

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

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

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

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

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

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

Neutral

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

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

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

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

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

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

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

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

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

I have been using the solution for five years.

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

I supported those involved in the setup phase peripherally.

The initial setup was straightforward.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

I am very impressed with the solution's resiliency.

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

Pricing is something that can always be better.

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

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

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

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

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

I rate the overall solution a nine out of ten.