Red Hat Enterprise Linux (RHEL) Reviews

All of our application services, application databases, and web services run on Red Hat Enterprise Linux. Everything is on there.  

Red Hat Enterprise Linux is certainly more secure than AIX, which is what we had. It's also better than Solaris. It has improved from that perspective. We can handle the vulnerabilities better. It's more secure.

Other than that, some of the products that we are using, we are migrating out of very costly license items. For example, we're using Fusion because we wanted to migrate, and then we started using Vision Manager. We did a POC a few years ago. We started using PAM because we wanted an engine in our workflow management system from that perspective. 

We are still exploring a lot of items, but it's been a decent journey. It has helped to set up modern technologies.

We use a lot of Red Hat products. We use Red Hat PAM, Red Hat Session Manager, and the operating system. 

We use the operating system the most because all our servers are on it.

The support is good. Red Hat provides use with a degree of training.

The adoption was slightly slow because the knowledge in the market is slightly less available. It's hard to find resources to actually support the product.

Some kind of training that can upskill the resource into this technology could certainly help.

I started using Red Hat Enterprise Linux version 6 in 2019. We have our own data center.

We used different solutions. We moved from AIX 7.1 to RHEL 6. Then we moved to 7. Now we're going to 8.

We chose Red Hat Enterprise Linux because we wanted to adopt newer technologies and we wanted to secure our systems. Red Hat Enterprise Linux was a good available option. 

It's on-prem right now. The deployment was straightforward. 

I manage the infrastructure team so all of these things are under my purview. 

We did hit some hiccups, but then RHEL's emergency support was available, and we were able to resolve it. 

We have an engineering team that analyzes different products. During the analysis phase, we look for all vulnerabilities.

Once it passes all of those things, it becomes available in our internal protocol. We have different names where it becomes available in our source space to get deployed.

Migrations and upgrades have been straightforward. For example, OpenSSL has different versions that are not supported on RHEL 7, which we have right now. There is a version that comes built-in. 

We faced some issues, but we worked it out with Red Hat. They gave us a patch. 

We're moving to RHEL 8 now. We moved to RHEL 7 last year; we're going to RHEL 8 now. Next year, in 2024, we plan to move to RHEL 8.

We saw a return on investment. It is helping the business. 

The pricing is competitive. It's not low, but it is in the market. 

Overall, I would rate the solution a nine out of ten. 

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

Its pricing is good and competitive.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We're using the product to test operating system stability and verify that it runs on the hardware that Trenton Systems produces. If it passes testing, it becomes a validated operating system that we can sell for the server. We plan to offer Red Hat in the coming months to anyone purchasing systems from our company.

The solution’s security feature is the most valuable feature for my company. We offer OS to military or government agencies. For these sectors, security becomes one of the highest priorities, especially the ability to wipe everything out if anything becomes compromised. Red Hat does a great job at that.

The product should be made more accessible to someone who isn't experienced with Linux.

I have been using the solution for four to five months.

The solution is very stable. Compared to many other OSs we test for our company, Red Hat Enterprise Linux has not crashed out on me or given me any problems. Anytime something goes wrong, after some research, I find that it's going wrong because I'm doing it wrong, not because the OS is fighting me in any way.

I haven't used support where I'm emailing or speaking to someone directly, but I've used a lot of the online support just by looking at different user guides, health guides, and things like that. Everything is really well documented. 

Sometimes there are posts about similar issues but with different remediation based on different circumstances. You might have the answer open in a tab, but you've got nine tabs open to find the right answer.

Positive

I have used Ubuntu, CentOS, openSUSE, and Mint. Red Hat Enterprise Linux definitely has an edge in security and the ability to control what the user at the end stage is doing. However, it is difficult to learn.

The licensing makes perfect sense for the number of features you get with the operating system.

We test Red Hat Enterprise Linux 9, the latest version. We do backtesting for versions 7 and 8 as well. The product is very secure. It took me a while to wrap my head around the whole Subscription Manager system and understand how that worked. Even at a base level, it provides a much higher level of security and the ability to take remediation steps if things go wrong. You can shut the whole system down and bring it back from the ground up.

From the keynote, it looks like steps are already being taken to make the solution more accessible to any regular user. 

The product does a really fantastic job of reducing the overall risk to the user. If a user is doing something they’re not supposed to be doing, it's very easy for the system administrator to walk them out of doing it. As for maintaining compliance, if a user is only meant to have specific packs and is only meant to perform specific tasks, it's very, very easy to lock it into only being able to do that one specific thing.

Most people in IT enjoy a little learning. Everything I've done so far with Red Hat has been installing, setting up the account, getting everything registered, and then worrying about testing to validate. It is difficult to start with, but the more you learn about it, the easier it gets. The more I use it, the more capabilities I find within the system.

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

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

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

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

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

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

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

The solution is scalable.

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

Neutral

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Red Hat Enterprise Linux is connected to our internal private cloud that is air-gapped.

We use Red Hat Enterprise Linux as the operating system on our network management and data management servers. It is our server operating system of choice for any type of hardware that needs to be reliable and stable.

Red Hat Enterprise Linux solved our need for automation and running containers. It is the most stable open source operating system available. When compared to other OSes, it is reliable and works well. This is important for my line of work, where I need to be able to reliably transfer files across thousands of miles. I need to do this quickly, and I have found that other OS solutions, such as Windows Server and Ubuntu Linux Server, are not as reliable or as quick. I have found myself constantly having to troubleshoot problems with these other OSes, and there is often not a lot of documentation available to help me.

The Red Hat Enterprise Linux knowledge base is awesome. Everything is documented, so I could easily find the information I needed to troubleshoot my misconfiguration issue. The knowledge base even provides suggestions for likely causes, which was helpful because most of the time, when something isn't working right on a Red Hat Enterprise Linux system, it's a configuration issue.

Security is one of the benefits of Red Hat Enterprise Linux. It is secure from the start, and it does not take long to configure it to meet government security standards. It also performs well during the staging process, and it does not break or cause services to be lost. In contrast, other operating systems often lock accounts, break, and cause services to be lost.

Simplifying risk reduction and maintaining compliance is straightforward and uncomplicated. There is plenty of documentation to help us, so if we get lost, we can refer to it to find our way.

The portability of applications and containers built on Red Hat Enterprise Linux makes it easier for our company to stay agile. We have found that our applications and programs run just fine on Red Hat Enterprise Linux, which provides a lot of supportability.

Red Hat Enterprise Linux's most valuable feature is that it comes with all the tools we need to set up and maintain an enterprise-grade system. Even if we install the minimal version of Red Hat Enterprise Linux, we will still have everything we need to get up and running quickly and easily. And if we ever need to restore our system from a backup, Red Hat Enterprise Linux makes it easy to do so, whether we are restoring from a scratch build or a backup that is a few weeks old.

A feature that I would like to see in the image builder is the ability to open the image in live mode and access a command line interface. This would allow me to immediately apply the necessary security settings required by the STIG. By doing so, I can deploy the image with the confidence that vulnerabilities present in the live network cloud service are closed before deployment, rather than applying the settings afterward as suggested in the example by Red Hat.

Ideally, I would prefer to deploy an operating system that already has all the necessary configurations in place. This would involve accessing a command line interface, adjusting configuration files as needed, setting up banners, and establishing user accounts. After making these changes, I would create an image and deploy it. I've noticed that the current image builder is primarily designed for commercial use, but as a DoD user, I have different requirements. Therefore, having an emulator or virtual terminal that allows me to interact with the kernel and make live changes, which can then be saved to create a customized ISO, would be an excellent feature to have. It would be great if Red Hat Enterprise Linux had a similar capability. Interestingly, Ubuntu Linux does offer this functionality with its "Custom Ubuntu Basic ISO Creator" (CUBIC).

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

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is a scalable operating system. Red Hat Enterprise Linux offers a wide range of options and features, and we are only just beginning to explore its full potential.

The initial setup is straightforward. I installed Red Hat Enterprise Linux using the stick method. I had to create nine different partitions, all of which were encrypted. This is where things got a little complicated. We need to decide whether to create a LUKS partition or partition and build our image on top of a LUKS partition. Initially, I was individually encrypting each partition using the "encrypt" option. However, this is not ideal because we cannot grow or shrink an LVM partition that is on an encrypted partition. Once the partition is created, it is set in stone. So, I needed to figure out how to encrypt just the partition and then create an LVM partition on top of the encrypted partition, such as SDA3. This was a bit of a challenge, and there is not a lot of documentation on how to do this. The documentation that is available is a bit confusing, and I got lost a few times. Once I figured it out, it was not too bad. The entire deployment process takes about 20 minutes.

We have seen a return on investment in all areas with Red Hat Enterprise Linux, including productivity. We use it in our daily operations in almost all of our systems. In one form or another, Red Hat Enterprise Linux is running on our systems. If we are not running Red Hat Enterprise Linux, our systems are unstable.

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

For those who are looking at other open source cloud-based operating systems for Linux, I would recommend Red Hat Enterprise Linux. It is well-documented and has a large pool of information available. We can also use CentOS content with Red Hat Enterprise Linux. The pool of information for Red Hat Enterprise Linux is far greater than some other open-source solutions.

The environment in which we deployed the solution is enterprise-level.

I work in the energy sector, so we use Red Hat Enterprise Linux for a variety of purposes. These include high-performance computing, running applications like SAP, geospatial applications, and Oracle. We rely on Red Hat Enterprise Linux for a wide range of applications, including those that require running Oracle databases.

It is important to our organization to have a solution that avoids cloud vendor lock-in. We just don't want to be locked into just one side or the other. We want to have the flexibility and availability to explore other options.

One of the main reasons we chose Red Hat Enterprise Linux was its reliability and stability. Compared to the Microsoft Windows environment, the Linux environment provided much greater stability. Therefore, we decided to use Red Hat Enterprise Linux for all our critical applications at that time, as they required a Linux-only environment.

We use Red Hat Image Builder as well. The golden images created by Image Builder are okay. In our organization, we prefer to create our own images because we need to incorporate our own security measures and harden the images accordingly.

Red Hat Enterprise Linux could do better in live patching. In this day and age, vulnerabilities are constantly emerging, I feel that Red Hat Enterprise Linux has fallen backward in terms of live patching, particularly live kernel patching. There are other products available that can perform this function, and they often follow their direction. 

Currently, my company has a live patch solution where we can patch the kernel without rebooting. This is essential because certain applications cannot tolerate downtime for reboots. However, there is a security concern when the patching process is delayed, as it exposes the system to high vulnerabilities and risks. So, when critical applications go down due to rebooting, it has a significant impact on both the financial and operational aspects. It requires a lot of money and manpower to schedule and execute the reboots, and during that time, the application downtime results in losing money. I believe this is an area that Red Hat Enterprise Linux should focus on to address this challenge.

I have been using the Red Hat Enterprise Linux operating system for around 20 years. We transferred our existing subscriptions to the cloud version. We are actually exploring hybrid solutions and availability options. As we transition to Azure, we are bringing our own subscription.

The scalability is good. We are able to scale efficiently. In our high-performance computing department, they handle a lot of scaling, and it's going well. Red Hat Enterprise Linux scales well.

I'm not particularly fond of the support. For example, when we have a server that's down, we raise a ticket indicating the severity of the issue. Then we receive another email suggesting things we can try to resolve the problem. I miss the days when we could directly speak to someone because sometimes, depending on the maintenance contracts and SLAs, it can take a lot of time without actually making any progress. Whereas speaking with a support representative could significantly reduce the downtime. So, I'm not really crazy about it.

The knowledge base is good. I would rate it a nine out of ten. 

Neutral

One of Red Hat Enterprise Linux's pros is that it has been around the longest. When working in a large corporate environment, reliability is crucial. In case something breaks, you want to have the assurance that there is a reliable support system to address the issues. Red Hat Enterprise Linux provides that level of support. 

However, it's important to note that even with a solid distribution like in Red Hat Enterprise Linux, the effectiveness may vary depending on the specific customer or scenario. It's about assessing how well the distribution handles issues when the next customer raises a complaint. So, we need to carefully consider the pros and cons based on our requirements. For certain workloads and development tasks, we might consider freestyle options that don't require paid subscriptions. In my company, we have a development program that greatly supports our decision to go with Red Hat Enterprise Linux.

Personally, I find the deployment process straightforward, but I've been doing it for quite some time. I can't speak for someone who is new to it. However, from my experience, it's relatively straightforward. I've been in this role for a while, so I'm familiar with the process.

Currently, we use Azure AVS, which allows us to migrate existing physical machines to the cloud until we can fully modernize them. It's much easier than it was a couple of years ago, but there is still some work to be done. Overall, it's manageable for us to move workloads between the cloud and on-premises or data center environment using Red Hat Enterprise Linux.

We have streamlined our deployment process within our guidelines. I can build a server in just three minutes. The time required depends on the type of server we need. If it's a more specialized server, it may take longer. However, it's nothing like the old days when it used to take several days. Especially in the cloud environment, it's quite fast. On-premises is a different story because we need to consider hardware availability, which can take longer. But once we have the hardware, the deployment itself typically takes less than an hour, especially when we leverage tools like Satellite for automation.

We have indeed realized a return on our investment. If we hadn't, we wouldn't still be using Red Hat Enterprise Linux. However, we are always striving to improve our return on investment. That's why we continually conduct due diligence and explore other operating systems to ensure that we're not blindly sticking with a particular company. We want to find the best solution that can potentially save us more money while delivering an equal or better return on investment.

Red Hat Enterprise Linux is starting to realize some other companies are gaining some footing in the industry. Red Hat's pricing still needs to get a little bit better. When you look at what you pay for a subscription compared to what you can pay with some of these other companies that do offer a lot of technical backing behind them, it starts turning heads.

Red Hat should focus on making enhancements and providing better support in that arena.

Before choosing Red Hat Enterprise Linux, we did evaluate other Linux-based solutions. When we initially chose Red Hat Enterprise Linux, we had options like Solaris and SGI. However, even recently, we have continued to evaluate other distributions because the Linux landscape is constantly evolving. There are new solutions emerging, so we have to perform our due diligence and assess what they can offer.

For customers looking for alternatives to Red Hat Enterprise Linux, my advice would be to choose something that aligns with your requirements and that you are happy with. Don't just pick something because it's cheap. You gotta look at the long term. Also, know what is needed for your project. For example, if you have issues, can you get those issues resolved in a timely manner? If you run into an issue, you're stuck, and they can't help you out, this means your project will be delayed. You will need to weigh that out.

I am an administrator for Red Hat Enterprise Linux. We use Red Hat Enterprise Linux in a hybrid environment running off of on-prem servers and also AWS. 

I use Red Hat Enterprise Linux for a variety of purposes. For example, we use it in cloud control systems at our factories. We also use it for test systems, data acquisition, databases, and web services.

The biggest problem we were trying to solve by implementing Red Hat Enterprise Linux was scalability. I have found that since implementing Red Hat Enterprise Linux, we get a lot more value for our money from our hardware. Red Hat Enterprise Linux has also increased our utilization of Windows as a solution.

I am not the one who moves workflows between the cloud and our data center using Red Hat Enterprise Linux. However, we have tested it and I believe it is seamless. It just works. This is one of our disaster recovery methods. We will have images, and we use Veeam for this. Veeam actually takes the image we have and moves it to the cloud. We then fired it up and did not have any problems.

The most valuable feature is the reliability of Red Hat's support.

Red Hat Enterprise Linux analytics are cryptic. While it is user-friendly, it is also very picky about who it takes for a user. It is rock solid, but it can be difficult to find things in there. Google is probably the best way to find information, but solving a problem can be difficult if we don't know what flags or permissions we need. We need more transparency or ease of use.

I have been using Red Hat Enterprise Linux for almost twelve years. 

Red Hat Enterprise Linux is scalable.

I can always get a hold of someone when I call, and they always resolve my issue. I only have to call them once or twice a year, because things just work.

Positive

I have used Fedora and Oracle Linux. I have some systems that run CentOS. 

Our organization requires us to use different solutions. We have had instances where products were developed on Oracle Linux. These products are medical, and switching to a different platform is not a simple task. I am encouraging the organization to switch everything to Red Hat Enterprise Linux because, although Oracle Linux is a fine platform, it is eight months behind Red Hat Enterprise Linux.

The main benefit of CentOS is its cost. Both systems are reliable, but Red Hat Enterprise Linux has a major advantage: Red Hat support. With Red Hat support, we have access to top-level Linux experts. If we need help with anything related to Linux, we can call Red Hat and they will connect us with an expert who can help us.

The first time I deployed Red Hat Enterprise Linux, I was swapping floppies. It has gotten a lot easier since then. The deployment process is straightforward. I usually map an ISO, and then check a bunch of boxes and let it run. I can have a server up and running in about fifteen minutes. After validating the system and installing the necessary software, I can deliver it to the end user in an hour. I know that if I automate the process, I could probably reduce the time to six minutes.

I give Red Hat Enterprise Linux a nine out of ten because there is always room to grow.

Someone looking at an open source, cloud-based Linux OS instead of Red Hat Enterprise Linux should consider what is being used in their customer base. If they are putting something up there as a proof of concept, then dabbling in open source is fine. However, if they have customers relying on them and they want minimal downtime, then they need Red Hat Enterprise Linux.

The knowledge base can be a bit cryptic at times. We can go in there and read the same information that's in the documentation, but sometimes it's not clear enough. So I'll often go to a half dozen other websites that tend to give us examples and other helpful information. The knowledge base is a good place to start, but it's not the end-all-be-all.