My use case for Red Hat Enterprise Linux (RHEL) is for dockerization; I use it for Docker or Postman. We use it for microservices, for example, to install JBoss and deploy some applications and pipelines for processes such as CI/CD. A summary of what I do includes microservices for applications such as Tomcat or JBoss, or for microservices in Postman, and installing Jenkins and launching pipelines.

Red Hat Enterprise Linux (RHEL) has helped reduce downtime and lower risks for me. There are rarely crashes or errors.

Image Builder or system roles feature is beneficial because it is a feature that allows you to create small images for what you need. With these images, you can go to a registry or whatever with VMware or KVM, and you can deploy them very quickly and efficiently. I tested it because it's better than having to install another machine all over again and losing much time. With Image Builder, you can create a small image tailored to your necessities. It is a good solution; you have to embrace automation, and the Image Builder helps you automate the creation of servers and images.

I appreciate all the Red Hat products available and the support provided when encountering any issues or needing help. You can open a case, and they answer very quickly. 

The other reason is it is a very strong OS for your needs. For example, I work in a banking system and in a financial system, and all kinds of products that you have—the problems may come from development, not from the server or machine.

In the knowledge base of Red Hat Enterprise Linux (RHEL), I can find everything I need. I don't have to go elsewhere. There are some videos with practical advice, all in one place, and all for free. I'm very happy with this kind of resource and knowledge base.

I find Red Hat Insights very helpful and beneficial. In all IT departments worldwide, I find it important because when I call my colleagues or other companies, this is a very significant feature. Insights gives many opportunities, particularly regarding security, and provides more facilities to improve security in your servers. In my opinion, the most important security feature in Red Hat Enterprise Linux (RHEL) is Red Hat Insights. When you use Red Hat Enterprise Linux (RHEL), you can install an agent in your Linux, and this agent runs on your Linux and gives you all the CVEs or security issues you have. For me, as an administrator, this is very helpful because with minimal clicks, I have the solutions and instructions on how to solve them. You only need to connect to Red Hat, and they provide a deployment, scan your machine, or all machines with Ansible, and give you a summary of your vulnerabilities, and you apply the solutions they provide.

The areas that have room for improvement in Red Hat Enterprise Linux (RHEL) include having more case bases and possibly more forums or places. A community that is not just informal but rather official could be beneficial. Everything else is good.

I would suggest improving compatibility. Sometimes I find that Red Hat is not aligned with the rest of the world. They create their own solutions, such as Docker, Podman, Kubernetes, and OpenShift, which can be better than what others offer. This can be both good and bad, depending on the situation. On the positive side, their innovations can enhance the overall quality of the company’s offerings. On the downside, when you need certain images or components that deviate from industry standards, it can become confusing. I find it difficult to understand why they choose to differentiate themselves from the rest. 

I have been in IT for 24 years, working with Linux and Red Hat Enterprise Linux (RHEL) for about 10 years.

I would rate the stability of Red Hat Enterprise Linux (RHEL) as a nine out of ten.

Red Hat Enterprise Linux (RHEL) is scalable for my business. It is very important, and I cannot imagine working without it.

I would rate the technical support of Red Hat Enterprise Linux (RHEL) as an eight out of ten.

Positive

I have worked with Ubuntu and SUSE, but I prefer Red Hat Enterprise Linux (RHEL) because the support is better than others. All solutions, how the machine or OS works, and all the other products, for example, OpenShift, I appreciate. I feel very comfortable with Red Hat Enterprise Linux (RHEL) because it is a solution based on CentOS and Fedora, and since my early career, I studied and learned in this distribution.

The deployment of Red Hat Enterprise Linux (RHEL) is very easy.

Red Hat Enterprise Linux (RHEL) has saved me about 40% to 50% time.

I would recommend Red Hat Enterprise Linux (RHEL) to other users; it depends on the company size. For medium and bigger companies, it is necessary because all the components needed, such as support and stability, are available. I cannot help much with the pricing because I do not work with licenses; this comes from another department. I discuss with my boss about how many machines or servers we need, and they coordinate with the commercials. I do not have information about whether it is cheaper or expensive, but I hear that they are very comfortable depending on how you deal with them. 

I would rate Red Hat Enterprise Linux (RHEL) an eight out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) are that it has been part of our core delivery solutions for many industries, mostly for telecom.

The features of Red Hat Enterprise Linux (RHEL) that I find most valuable include all of the features since system V. 

In my organization, Red Hat Enterprise Linux (RHEL) provides an agnostic interface for many storage vendors that we deal with, which helps us to have a wider spectrum of offerings in our consultancy offerings.

Red Hat Enterprise Linux (RHEL) can be improved by adopting a feature similar to YaST from a big European competitor, which would significantly enhance Red Hat technologies.

I have been using Red Hat Enterprise Linux (RHEL) since 2005 when it was in release four, which makes it 20 years.

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as favorable, noting that during the last five years, we've experienced fewer crashes and downtimes compared to other commercial Unix and Linux distributions in the market.

Red Hat Enterprise Linux (RHEL) scales excellently with the growing needs of my organization, and I would rate it ten out of ten.

I evaluate customer service and tech support as excellent; with either the partner portal or customer portal, we receive very good RCAs and analyses for any case we submit to Red Hat Enterprise Linux (RHEL). On a scale of one to ten, I would rate customer service and technical support as ten out of ten.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using Commercial Unix, Oracle Solaris. The factor that led me to change was that during the last decades, Red Hat Enterprise Linux (RHEL) has absorbed many features straight from Solaris, enabling us to perform effective migrations from Commercial Unix to RHEL.

At the very beginning, at the earliest versions of Red Hat since version six, there was a kernel that was not compatible with many cluster vendors, and that's why we were adopting another vendor of Linux. However, we've seen that during these past years, Red Hat has been experiencing a lot of enhancements overcoming these kinds of barriers. And now Red Hat has become more versatile in accepting more hardware that allows us to standardize our Red Hat offerings in our consultancy services.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL). For data points, in one of the key industries I handle, which is telecom, Red Hat Enterprise Linux (RHEL) has been one of the key strategic providers offering a good price to implement automation and containerization across all of the network elements we manage with several vendors, and in the latest five years, we have observed a good investment return in terms of ROI.

My experience with pricing, setup costs, and licensing is that I strongly believe Red Hat Enterprise Linux (RHEL) offers a good relationship between value and price, and despite it being quite pricey, it's definitely worth it.

Before selecting Red Hat Enterprise Linux (RHEL), I considered SLES, which is a competitor of Red Hat.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is to have a good plan and to establish the relationship as a key strategic reference for any upcoming migration. The partnership and customer support provided is a high-value option. Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk through high availability solutions and key features that enable network redundancy, allowing us to achieve this. 

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as excellent because it has become one of the key standards in the industry for following guidelines according to any topic in the RHEL environment. 

On a scale of one to ten, I rate this solution an eight.

My main use cases for Red Hat Enterprise Linux (RHEL) are Virtual Desktop Interface (VDI) for the server, supporting Telco work workflows, manufacturing software for manufacturing, and travel software. I have a huge base for what we're targeting around AWS or Red Hat solutions.

I favor the network manager feature of Red Hat Enterprise Linux (RHEL); I appreciate the versatility and flexibility of network manager. I appreciate that we can make super-fast modifications to networking solutions, and I value the support for IPv6. 

I also value the support for working with the community very specifically. Bringing the solutions we need for customer problems to reality tends to result from our conversations with Red Hat. Normally, if I need help making a customer experience better, I can have a conversation with the business teams at Red Hat, and then we can find a collaborative solution.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk; although it's hard for me to say that I really understand it outside of an analyst report, I can say that I truly believe it has increased uptime based on my experience. 

There's a consistency, and my example is that I trust the kernel and the quality engineering, which leads me to more favorable results in places where other distributions might make changes that slow down my networking or storage network in unpredictable ways.

For a new release of Red Hat Enterprise Linux (RHEL), the main improvement could be in the pricing models, particularly understanding how to better present those pricing models in a more predictable manner. It is very difficult from a partner perspective to figure out how to position software to a customer when the pricing may or may not be competitive, so that's my biggest 'how could I fix this?' question.

I have been using Red Hat Enterprise Linux (RHEL) for 25 years.

When assessing the stability and reliability of Red Hat Enterprise Linux (RHEL), I can say that on every operating system, there are always exceptions and new issues to fix. 

However, if I have software validated for RHEL, I know I can expect a certain level of certainty that issues will be ones that have either never been seen before or are the result of our new approaches.

Red Hat Enterprise Linux (RHEL) by itself scales incredibly. However, the problem tends to arise where increased consumption raises total costs. 

As the total cost increases across the operating system distribution, my requirements for support decrease, making it difficult to gauge a return on investment, which complicates the situation for me as a representative of an entire fleet.

I would evaluate customer service and technical support as generally positive; I've never had a problem with my support. Sometimes, individual support agents might not know what they're discussing or misunderstand the question, possibly due to my clarity or other factors. I would say that it is at least at the same level or better than any support group I've ever engaged with in technology.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using another solution within the RHEL family. I often test workloads using Fedora or CentOS as a foundation and then move those production workloads to Red Hat.

My experience with pricing, setup costs, and licensing has been confusing; it feels different every time. The complications often arise from being unable to predict exactly what is necessary for a deployment, as the build-out and sales cycles are significantly more complex.

I have most definitely seen a return on investment with Red Hat Enterprise Linux (RHEL); I don't think my job would exist if there wasn't a return on investment.

By policy, I am required to use Amazon Linux for everything, however, by necessity, I am replacing that with Red Hat solutions where we have space during my evaluation process.

My business relationship with Red Hat is that I am a Partner.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is still hard to search, but I recognize that AI is probably making that easier during this period. I think Lightspeed is an important part of our structure for interacting with the knowledge base information, and I look forward to making that work better.

I typically advise other organizations considering Red Hat Enterprise Linux (RHEL) by asking how important their workload is to them. I question what happens if it goes down and how much time they have to spend fixing it. If they value that aspect, then it's their choice to determine their path. 

My biggest question often relates to how much they would pay to replace the community, and if they are willing to understand the significant number of partners and open-source champions contributing to Red Hat, they will see how that community cannot be replaced in terms of how software fits their business needs.

I rate Red Hat Enterprise Linux (RHEL) ten out of ten.

Our main use cases for Red Hat Enterprise Linux (RHEL) include having servers all around for storage and processing, specifically for compute processing.

The best feature of Red Hat Enterprise Linux (RHEL) that I appreciate is that it provides consistent configuration setups with step-by-step configuration, which is easier. When configuring a server, what previously took at least a 24-hour turnaround time now takes only 30 minutes to one hour.

I am satisfied with the management experience and normally choose Red Hat Enterprise Linux (RHEL) when there is an option between it and other solutions. I have been involved in RHEL upgrades or migrations from many years ago, approximately 14 to 18 years back. Currently, everything is easier as upgrades and patches come as a package.

Regarding built-in security features, maintaining compliance is handled at the architect's level during configuration setups. While the service provider handles access level security, configuration compliances need to be managed by the architect.

The upgrade and migration process in AWS is straightforward - I can easily increase the number of processors through hot migration, which can be done while the system is running without requiring shutdown. RHEL has helped mitigate downtime and lower risk with negligible system interruptions.

Red Hat Enterprise Linux (RHEL) could be improved with more shared storage capabilities. For example, I have multiple RHEL instances, and enhanced storage sharing would be helpful for transferring data between servers.

I have been using Red Hat Enterprise Linux (RHEL) for almost 12 years.

I assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as very stable, with negligible downtime, crashes, or performance issues.

Red Hat Enterprise Linux (RHEL) scales efficiently with the growing needs of my organization as it is one of the managed shared services. When we check the scalability option while configuring, it manages everything automatically without requiring separate actions. I have expanded usage, and the process has been smooth with zero downtime.

I haven't had the opportunity to evaluate customer service and technical support because we address any issues through AWS since it's a managed service.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was not using another solution to address similar needs.

I manage Red Hat Enterprise Linux (RHEL) systems for provisioning and patching through AWS, which handles the patching at the service provider level. Provisioning is easy because I can modify configurations, such as the number of processors and other parameters.

The deployment model for Red Hat Enterprise Linux (RHEL) is cloud. Security requirements were a consideration in choosing RHEL in the cloud, as AWS provides most of the security features.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL) as the prices have been reduced since we implemented a shared environment.

I cannot speak to licensing because we are using managed services from AWS. Regarding pricing, setup cost, and licensing, all costs come from AWS on a pay-as-you-go basis. We get charged when the service is up; otherwise, there is no cost.

Before selecting Red Hat Enterprise Linux (RHEL), I considered something similar to VMware. These were the two options I chose between.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is that it's easy to use and a reliable service. It has been consistently at the top in this industry for ages and has its own strengths. I would recommend it as a first choice.

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) as eight or nine out of ten.

We mainly use Red Hat Enterprise Linux (RHEL) to host containers. 

RHEL makes things easier for hosting containers and has really good integration with automation tools such as Ansible, which makes configuration management easier. Those were the two areas where RHEL helped us significantly. 

We haven't used Lightspeed yet; however, we are focused on containers. It's pretty seamless, and RHEL made it much easier for us to get things running when we moved. We were initially on PCF, Pivotal Cloud Foundry, and now we are on OpenShift. 

RHEL made development much easier, and we use it as a testbed to run our containers before moving them to OpenShift.

RHEL simplifies container hosting and offers excellent integration with automation tools like Ansible, making configuration management more straightforward. They have really good support, helping me adapt more easily because I already had a good understanding from working on open source technologies.

I find Lightspeed to be the most valuable feature about RHEL. It makes troubleshooting much easier. It's an LLM similar to ChatGPT, allowing me to query what my exact command is, and it provides me with that.

RHEL supports many different container runtimes and packages, making our job pretty easy to build images for developers to use on our container platform. Using RHEL as a base image simplifies our work compared to other options, as it comes pre-packaged with many necessary features. 

The fact that we also use a Red Hat-based container product platform, OpenShift, means it has everything needed to run on OpenShift.

RHEL is a pretty polished product, however, if it becomes more mainstream compared to other Linux distributions and if more people adapt it, it would be used as a much more universal product. This would make it easier for people to adapt to RHEL.

I have been using Red Hat Enterprise Linux (RHEL) for four years.

I would assess the stability and reliability of RHEL as good. I faced some issues due to the underlying platform on which they were hosted, but I didn't encounter problems with RHEL itself. Whenever we have issues, we have good Red Hat support, so it's very reliable.

I assess RHEL's scalability as pretty robust. Most of our footprint is on the cloud, and any new VMs we spin up happen quickly because of how easy it is to set up RHEL. Combining that with the capabilities of Ansible makes scaling up pretty easy on demand.

I evaluate customer service and technical support as excellent. 

They have a tiered structure for outage severity and type of environment, which is great. My experience has been positive, and we also had vendor engagements with Red Hat when implementing new solutions, with an engineer and architect helping us set things up. That was a really good learning experience for me as well, so my overall experience has been positive.

Positive

Prior to adopting RHEL, I used other distributions of Linux. I worked on Ubuntu and SUSE, and I even worked on some personal projects with Kali Linux. Every distribution has its pros and cons, but for an enterprise-level solution, I feel RHEL is a much better option because of the support it provides.

Security requirements were 100% a consideration in choosing RHEL in the cloud. Our company has its own setup with images we use, with our own vulnerability checks before pushing it. RHEL qualifies as one of the software solutions that has been vetted, and we use it as one of our primary operating systems.

Red Hat Enterprise Linux (RHEL) has provided a return on investment of 100%.

I haven't worked on the RHEL side regarding pricing, setup cost, and licensing, however, I have worked on the OpenShift side. The pricing is competitive, especially when compared to our last vendor, PCF, which became quite expensive after being acquired by Broadcom. That's another reason why we started moving to RHEL.

In my current company, RHEL had a mature environment before I joined, but in one of my previous jobs, we chose between SUSE and RHEL. We felt RHEL was a much more polished option because of its larger user base and extensive knowledge catalog.

For other organizations considering RHEL, my advice is that if your organization is operating at scale and requires good support, RHEL is a great product. 

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) an eight out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) include workflow development. We are running the workflow in that.

The features of Red Hat Enterprise Linux (RHEL) that I appreciate the most include OpenShift. These features have benefited my organization through working on on-premise cloud migration. 

Some of the high sensitive data cannot go to the public cloud, so we are trying to use Red Hat Enterprise Linux (RHEL) for the internal migration. We got rid of the VM maintenance and related tasks.

Security requirements were a key consideration in choosing Red Hat Enterprise Linux (RHEL) in the cloud. We are from the financial industry, so customer data is one of our big responsibilities. When it comes to managing Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, we currently work with our middleware team for upgrades, however, the plan is to work with AWS or the Red Hat team for future upgrades.

My assessment of the built-in security features is limited as I'm from the development side. Our upgrade and migration plans to stay current involve recommendations from our vendors.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk. Our restart used to take considerable time initially, but through optimization, it now takes significantly less time. I would assess the knowledge base as good. We received dedicated training this summer from Red Hat Enterprise Linux (RHEL), with trainers coming to our office for two days, which was very beneficial.

The pain points that Red Hat Enterprise Linux (RHEL) helps me solve include the transition from a Microsoft background, where I had a habit of everything with a GUI. I see very few GUI elements in Red Hat Enterprise Linux (RHEL) and many command lines. I'm not proficient in that, which makes me struggle sometimes. Overall, we have the tools, however, there should be drag-and-drop, window-type functionality.

I've used the solution for 11 years. 

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as very good. As a developer, I have never seen any downtime, so it is working perfectly fine from the middleware side.

Red Hat Enterprise Linux (RHEL) scales efficiently with the growing needs of my organization. They consistently release new versions. The scalability has been going well. 

We have expanded usage, and the process was smooth. In the beginning, we had very few applications, and now I can see many applications running on that side. It is definitely expanding.

I would evaluate customer service and technical support as very proactive.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using Microsoft Windows Server. Now our focus is more on this area. The factors that made us want to change include transitioning from Microsoft technology, moving to Pega and Java side. This technology is much more supported on this platform.

The initial deployment was very good. 

I have been involved in Red Hat Enterprise Linux (RHEL) upgrades or migrations, and due to our many internal dependencies, it takes time, however, we successfully completed it.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL) because we have many critical applications running without any issues. There is significant ROI on that.

The other solutions I considered before choosing Red Hat Enterprise Linux (RHEL) include using three or four vendors as a business continuity plan. We have Red Hat Enterprise Linux (RHEL), AWS, Windows and others. We cannot rely on one vendor; we have to work with multiple vendors to maintain business continuity.

The advice I would give to other organizations considering Red Hat Enterprise Linux (RHEL) is that it's a really good tool to use if they have applications in Java, Pega, or IBM workflow or Lombardi. 

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) a nine out of ten.

We provide a hosting platform on which internal business applications will want to host their applications. Depending on what our internal app teams want to use to host their applications, some may want to host on Red Hat Enterprise Linux (RHEL). These are the main use cases that we deal with - app teams hosting their applications in our hosting platform for internal use.

From a consumer preference perspective, we have folks who prefer options for teams to host their environments in the cloud. It feels there is more security with the product and more configuration customization that app teams appreciate. Certain vendors require that Red Hat Enterprise Linux (RHEL) specifically be used, which helps in those cases.

Red Hat Enterprise Linux (RHEL) provides a certain base set of security features and capabilities that we have found other flavors of Linux do not provide or are required by governmental agencies to meet CMMC controls. The security controls that go above and beyond other types of Linux, along with the manageability from an enterprise perspective, make it valuable.

One of the pain points we have found is that for Windows systems, it is pretty easy to domain join those in a federated model. It seems we have to either have a third-party product or it is not quite as straightforward to domain join Linux OSs. This would be something that could potentially be smoother in the future.

The knowledge base would be more helpful if it was more easily searchable. There might be opportunities to leverage AI for being able to search the knowledge base and articles more effectively.

We have been using the solution for about 12 years now.

Compared to other OSs, stability has been solid.

It has scaled very well. We have not experienced any scaling issues from our perspective.

I have not had to directly engage customer support. Mmy team has not provided any issues or complaints when they have had to reach out to support.

Positive

We tried using CentOS type Linux or Amazon Linux. However, Red Hat Enterprise Linux (RHEL) checked the compliance and security features much better than those product offerings.

We have been actively moving systems from on-premises into the cloud since 2017, including moving Red Hat Enterprise Linux (RHEL) versions to newer versions in the cloud.

It is pretty easy to deploy. The main challenge is domain joining it at the end, however, we have not had many issues with getting things STIG hardened, which is welcome when it comes to the OS itself.

We are deploying everything via automation using the Ansible product. Everything is deployed leveraging Ansible, and we have a desired state config post-deployment that provides post-permission hardening.

Based on our latest agreement, we are seeing cost savings and optimizations.

I wasn't too involved in those discussions. For the most part, our sourcing team carried the heavy burden of negotiating the licensing agreements and similar matters.

Depending on your use case and compliance requirements, take a good look at all the different flavors of Linux and you will probably recognize that Red Hat Enterprise Linux (RHEL) is going to check the boxes much smoother and easier than some of the other versions or implementations. It will save time. 

On a scale of one to ten, I rate this solution a nine.

I don't directly use Red Hat Enterprise Linux (RHEL). I advise our clients to select this kind of technology for their hybrid cloud requirements.

When looking at hybrid cloud, the entire ecosystem is very complex; public cloud, private cloud, everything comes together and becomes very difficult to manage. The best use case I can see when Linux systems are involved is to use one common platform to manage all the infrastructure and the platforms on top of that. Red Hat Enterprise Linux (RHEL) would be the best choice for that particular use case.

The ability to manage complex environments, especially when it comes to hybrid cloud, helps us significantly, along with the Linux environments which are natively in-built into Red Hat Enterprise Linux (RHEL). The reduction in complexity, ease of use, and managing the entire hybrid cloud landscape was easier with this software. Service mesh and Kubernetes support contribute significantly, allowing better handling of complex cloud-native applications efficiently.

We use third-party platforms to manage the risks and put the security guardrails in place, and Red Hat Enterprise Linux (RHEL) has its own native security guardrails as well, so we use both.

Indirectly, we help other enterprises implement this solution, and I can tell how other enterprises are benefiting. They reduce complexity and achieve faster time to market as they improve efficiency and use these tools to improve their development process. This helps them move faster and release their software as soon as possible.

We are trying to move most of our workloads to public cloud environments; however, not everything will go to the public cloud. We are trying to find a balance between on-premise, private cloud, and public cloud. Currently, the split is 50% on public cloud, 40% on private, and 10% on on-premise.

Since we started recommending and our clients started using it, I can see the cost-to-performance ratio go up by over 50%.

I would suggest focusing more on the cloud-native aspect. Kubernetes and microservices are built in natively; however, it would help to bring the service mesh and service mesh handling. That would be one of the improvement areas.

Most importantly, since we deal with mostly Fortune 500 clients who are global in nature, as the data is siloed from multiple sources and has to be pulled in, it's very important that the data is secure and all the security guardrails are in place.

Since Red Hat Enterprise Linux (RHEL) 10 was recently launched, there were some bugs that needed to be fixed and performance issues. If those are cleared, then it would be a good fit for everyone.

There has not been much downtime with the system.

The scalability is above average. It has scaled up and created its portfolio in line with market demands.

The customer service was good. 

Positive

We did not use any previous solutions.

Deployment is fairly easy. The support that is required is appropriate for both full-fledged full stack developers and starting developers. The support overall is good.

We implement mostly through service integrators who help to do the groundwork.

Since IBM's acquisition, we thought there might be some changes, yet surprisingly, it was kept aside. IBM was kind enough to let them operate on their own, which is a plus sign. The stability has been good, and we have no complaints.

The pricing was good and did not affect much of the decision-making. It was appropriate, though I would suggest the team improve upon offering higher discounts on bulk purchases.

There are not many options available besides Red Hat Enterprise Linux (RHEL).

I am a principal catalyst who works with AWS, Azure, Google Cloud, the hyperscalers, public cloud, and private cloud, both on the client side and on-premise.

The ability to manage complex environments, especially regarding hybrid cloud, helps us significantly, along with the Linux environments which are natively in-built into Red Hat Enterprise Linux (RHEL).

I rate Red Hat Enterprise Linux (RHEL) a nine out of ten.

My main use case for Red Hat Enterprise Linux (RHEL) is when I was working with another company, where we used the Ansible Automation Platform provided by Red Hat and OpenShift, primarily for any code automations and server productions.

I have additional insights about my main use case for Red Hat Enterprise Linux (RHEL); we've used it as a standalone server for different products, more specifically as an Ansible server and key servers, just provided by virtual machines.

The best features that Red Hat Enterprise Linux (RHEL) offers include how comprehensive the enterprise packages are, as you can get stuff included with it and the documentation that follows, which I think is good even though it is a Linux distribution that you have to pay for.

I also appreciate Red Hat Enterprise Linux (RHEL)'s built-in security features, as they require less configuration and include compliance associated with it. More specifically, regarding the documentation, if I had any specific questions about Red Hat Enterprise Linux (RHEL), I could go directly to the website and find the answers there.

Red Hat Enterprise Linux (RHEL) has positively impacted my organization by providing a lot of security to run all of the systems we had in a particular environment, especially since I worked with more government operations, where security was the top priority, which Red Hat prioritized. We didn't have to worry about security configurations within the infrastructure, saving us time, and it was easy to navigate if you had a great background in Linux, plus Red Hat support was very helpful with any specific questions on the product.

I wish that Red Hat Enterprise Linux (RHEL) had more free options available; there are similar Linux distributions, but in terms of training and certification, I think it would be beneficial if there were a better free trial, allowing users to gain better experience with the platform itself.

That's the main improvement needed for Red Hat Enterprise Linux (RHEL).

I have been using Red Hat Enterprise Linux (RHEL) for about two years.

Red Hat Enterprise Linux (RHEL) is stable and handles growth and changes efficiently, specifically with new AI platforms being integrated.

I have not experienced customer support for Red Hat Enterprise Linux (RHEL).

Positive

I did not use a different solution before Red Hat Enterprise Linux (RHEL); it was strictly Red Hat Enterprise Linux (RHEL).

I cannot share any return on investment from using Red Hat Enterprise Linux (RHEL).

I never dealt directly with the pricing, setup cost, and licensing for Red Hat Enterprise Linux (RHEL) since that was managed by someone above me; it was more about day-to-day use cases for me.

My advice for others looking into using Red Hat Enterprise Linux (RHEL) is to be sure to look into the documentation and review the products because it is very customizable, and I would recommend using it for an enterprise.

I choose a rating of seven for Red Hat Enterprise Linux (RHEL) because it is not a solution I use every single day. I rate it higher because it is applicable across multiple infrastructures Azure and AWS Cloud, but it is not universally used in particular environments, especially the one where I currently work, which is not really code-dependent.

I was offered a gift card to do this interview regarding Red Hat Enterprise Linux (RHEL), but that's the only business relationship my company has with this vendor.

My main use case for Red Hat Enterprise Linux (RHEL) at work involves using the EKS Kubernetes cluster on AWS, which is hosted on managed nodes based on Red Hat Enterprise Linux (RHEL) 9.4.

On a daily basis, I manage these nodes, execute commands to check connectivity, investigate network issues, and gather metrics such as CPU and RAM usage. Red Hat Enterprise Linux (RHEL) is integral to my daily work, as I regularly log into these nodes to execute commands, check network issues, and monitor capacity.

One of the best features Red Hat Enterprise Linux (RHEL) offers is the premium support, which is particularly noteworthy in version 9.4. If we encounter an issue, we can contact the support team anytime, and a technical support representative works with us to find the root cause. The support team helps us find and solve issues quickly and effectively.

While many features in Red Hat Enterprise Linux (RHEL) are common to all Linux distributions, RHEL stands out due to its vast community and comprehensive feature set. Red Hat has the largest market share among Linux distributions, and its exceptional support distinguishes it from other distributions. Additionally, it is renowned for its stability, security, ease of use, and community engagement.

Red Hat Enterprise Linux (RHEL) has positively impacted our organization by improving our environment, enhancing security, and enabling the implementation of best practices. We chose RHEL 9.4 for its stability, security, and excellent support. When running our Kubernetes cluster on AWS, RHEL proves to be an excellent choice for deploying our applications in a secure environment.

Using Red Hat Enterprise Linux (RHEL) 9.4, we enhance our security through features such as SELinux, which significantly improves our environment's security and stability. We have used RHEL-based nodes since the inception of our organization and the My Vodafone app project in Greece, contributing to improved security, performance, and stability throughout our operations.

The primary area for improvement in Red Hat Enterprise Linux (RHEL) relates to accessibility and training resources rather than the operating system itself. Red Hat should provide more training opportunities and make learning materials more accessible to users and customers.

Specifically, the documentation should be more accessible, and Red Hat should consider offering free training or virtual machines beyond just ISO files. A free virtual machine on the cloud would be valuable for people to try and become familiar with RHEL, as installing a virtual machine from an ISO can be complex. A pre-installed RHEL virtual machine would make it easier for people to learn and experience the distribution.

I rate Red Hat Enterprise Linux (RHEL) eight out of ten because while it's an excellent score, there is room for improvement in accessibility. Unlike other distributions such as Ubuntu or Arch Linux that are readily available, Red Hat should create more opportunities for users to try their system through easily accessible virtual machines on their website or other public platforms.

I have been using Red Hat Enterprise Linux (RHEL) for eight years, starting before my career as a DevOps and system admin engineer.

The scalability of Red Hat Enterprise Linux (RHEL) for my organization is exceptional, and it handles growth and increased demand effectively. The support system particularly enhances its scalability capabilities.

The customer support of Red Hat Enterprise Linux (RHEL) deserves a perfect 10 out of 10, as it is one of the most valuable aspects of the system.

Positive

I did not use a different solution before Red Hat Enterprise Linux (RHEL). We started with RHEL 7, upgraded to 8, and are now using version 9.4.

The pricing, setup cost, and licensing process for Red Hat Enterprise Linux (RHEL) is straightforward, and I have not encountered any challenges in conducting these operations.

My advice for others considering Red Hat Enterprise Linux (RHEL) is to strongly consider it as one of the most secure, stable, and efficient options compared to other distributions. I have always chosen RHEL as my first choice without evaluating other options. I rate this solution 8 out of 10.