Red Hat JBoss Enterprise Application Platform with Support by MidVision

My main use case for Red Hat JBoss Enterprise Application Platform (EAP)  is as an application server, and sometimes I have used it as a web server on a few servers as well. It provides great middleware technology to use as an application server and compensates for all my application requirements.

A specific example of where I used Red Hat JBoss Enterprise Application Platform (EAP)  as an application server is for my in-house applications that mainly utilize JBoss or WildFly, which is the new name for JBoss. I am using it for managing my applications and, as mentioned, also using it as a web server, so it helps in communicating and integrating with the database. I have used many applications currently with the help of just the JBoss application, and it is very easy to use. Until last year, I was using JBoss 7 version, and then I migrated to JBoss EAP  8 version, as the 7 version was at end of life.

I would say there are many advantages with Red Hat JBoss Enterprise Application Platform (EAP ) compared to Oracle WebLogic, which I previously used. After starting to migrate my applications from Oracle WebLogic to JBoss EAP  over the last three years, I find its main features to be very secure and highly compatible with other languages. There is nothing fancy I need to change in the code, and it starts working seamlessly. I can simply adjust XMS parameters on the fly, restart JBoss, and it performs very well.

The security features of Red Hat JBoss Enterprise Application Platform (EAP ) have been beneficial for my team, as many applications use JBoss while also employing other languages such as Perl, PHP, and Java-based applications. Most of them are primarily Java-based applications, so Red Hat JBoss's compatibility mainly facilitated my migration. During the migration, it was very helpful because Red Hat provided a useful tool for it; I simply downloaded it from their website and ran the script. Before migrating, I backed up my configuration files, and after a restart of JBoss, everything worked very well, with only the need to update the ports.

I have already covered the features of Red Hat JBoss Enterprise Application Platform (EAP), such as security and compatibility with other languages. The clustering feature is very good, and I can easily add other plugins to connect with databases such as SQL or Oracle.

Red Hat JBoss Enterprise Application Platform (EAP) positively impacts my organization by reducing the number of tickets I receive. When using other application servers, I faced many heap memory and security tickets, and those bugs generated a huge volume of logs that filled my application file systems, resulting in the application going down within a short time. Since I started using JBoss EAP, I have seen a significant reduction in both the number of tickets and logs. The support from Red Hat is very good; I normally do not have many tickets with them, but when I encounter issues or try new features, they are very helpful.

Red Hat JBoss Enterprise Application Platform (EAP) can be improved, as there are changes with the Java version, transitioning from Java to Jakarta since the last JBoss 8 version. I had to make several changes across my server to align with these updates, which was a challenging task for me as it took time. Additionally, in terms of security, there are still some concerns with hacking on Java versions and Java ports, and the XML libraries should be more secure, maintaining consistency to facilitate smoother migrations between versions.

My experience during migrations with Red Hat JBoss Enterprise Application Platform (EAP) was mainly smooth, but I encountered application-specific issues because some applications were not compatible with the new version. I had to roll back and troubleshoot these issues, reaching out to Red Hat for assistance, and they were instrumental in resolving those concerns.

I have been using Red Hat JBoss Enterprise Application Platform (EAP) for three or more years.

In my experience, Red Hat JBoss Enterprise Application Platform (EAP) is approximately ninety percent stable. However, I sometimes encounter issues where deployment fails after restart or JBoss restarts itself due to heap memory issues or configuration changes within the application, leading me to conclude it is ninety percent stable.

The scalability of Red Hat JBoss Enterprise Application Platform (EAP) depends significantly on the application and the amount of memory and CPU cores provided on the server. For instance, as I utilize Red Hat EAP in my Azure  cloud, I can easily scale based on server memory and CPU. If I notice potential issues, especially when running several instances of JBoss on a single server, I can increase the XMS parameters, restart the application, and it resumes functioning easily.

Customer support for Red Hat JBoss Enterprise Application Platform (EAP) has been beneficial as I use a subscription-based model, which carries an associated cost for standard and premium support. For production servers, I have opted for premium support, which has proven to be very useful. For high-severity cases, I receive twenty-four-seven support, and usually, my tickets get responses within one hour with easy resolutions. Occasionally, tickets related to new or migrated applications may take one to two days, but overall, the support from Red Hat is excellent.

Before Red Hat JBoss Enterprise Application Platform (EAP), I used Oracle WebLogic and IBM WebSphere on some servers, but they were not user-friendly or easy to work with. Therefore, I started employing Red Hat JBoss on my test servers, which turned out to be very simple for my application team and users, prompting my decision to adopt Red Hat.

I have observed a return on investment with Red Hat JBoss Enterprise Application Platform (EAP) since the time saved is directly related to the number of incidents that have decreased. I do not require as many personnel to manage all those issues now. Previously, I had to restart my application weekly, making it easier for me to set up those restarts, and there were no flaws requiring monitoring afterward to ensure functionality, which has significantly saved time.

Regarding pricing, setup cost, and licensing for Red Hat JBoss Enterprise Application Platform (EAP), I believe the licensing cost is somewhat higher. However, I expect this given that it is now under IBM.

I would say that the licensing cost for JBoss is higher compared to other middleware technologies, but I accept it since it is now part of Red Hat. The support provided by Red Hat is very helpful and easy to use. The pricing is based on my core deployment, with fewer cores for test versions and many cores for production ones. The subscription model is straightforward, and Azure  has also been very supportive in the setup and cost reduction.

Prior to choosing Red Hat JBoss Enterprise Application Platform (EAP), I evaluated alternatives such as IBM WebSphere and Oracle WebLogic. However, those options did not meet my needs adequately; they were not user-friendly, and my applications struggled with compatibility, so I did not pursue any other solutions.

Red Hat JBoss Enterprise Application Platform (EAP) is deployed in my organization on both on-premises and public cloud environments. Initially, I used it exclusively on-premises and later adopted it for public cloud use, so I currently utilize both.

On a rough estimate, when I was using different middleware technologies about three or four years ago, I dealt with around one hundred to one hundred twenty-five tickets per month for production servers. After using Red Hat JBoss Enterprise Application Platform (EAP) and enhancing the configuration files, the tickets have been reduced by half. The logs still exist, but they are now useful rather than just vague numbers filling the file systems; the logs have decreased and provide good information.

My advice for others considering Red Hat JBoss Enterprise Application Platform (EAP) is to ensure that if you are migrating applications from any other middleware technologies, you should only use the latest version. Opting for an older version heading towards end-of-life leads to costly support from Red Hat. Therefore, I recommend starting with test servers to ensure compatibility with your applications; if they do not work properly with Red Hat JBoss, then it is better not to proceed.

I rate Red Hat JBoss Enterprise Application Platform (EAP) an eight out of ten because there are still some issues present; it is not perfect. I have encountered deployment failures, memory leaks, connection pooling exhaustion, and sometimes configuration issues with Red Hat. Thus, there remain opportunities for improvement.

Red Hat JBoss Enterprise Application Platform (EAP)  is used to deploy web applications and web services, which is the primary purpose.

Red Hat JBoss Enterprise Application Platform (EAP)  connectors are particularly valuable for connecting to mainframe systems. Previously, a Bull mainframe was used, and connectors were available for that system. The platform is also used for databases and management of connection pools for these types of connectors, as well as for security and securing access. The ability to manage multiple instances on the same server with different ports is a significant capability.

Optimization has been used only once to optimize the Java runtime. Pool and connector adjustments are sometimes made to achieve optimum performance.

Microservices have been used for specific tasks, such as a microservice dedicated to signature functionality for PDF documents. The plan for the future is to migrate all applications and implement microservices during the next refactoring.

Red Hat JBoss Enterprise Application Platform (EAP ) connectors are particularly interesting and valuable for connecting to mainframe systems, including those previously used, as well as for databases and management of connection pool for these types of connectors. Security features and the ability to secure access, along with the possibility to manage multiple instances on the same server with different ports, are significant advantages.

The management console is used in a straightforward manner for online configuration, hot configuration, and deployment across different environments such as test environments. The console is used for deployment in testing and development. For production, deployment is handled online or through other tools such as Ansible  for configuration automation.

Currently, Red Hat JBoss Enterprise Application Platform (EAP ) has been working well with no performance-related problems. However, there is concern about how the platform will be used when the organization switches to microservices, and it is unclear whether Red Hat JBoss Enterprise Application Platform (EAP) or only a lighter container will be used. No decisions have been made yet, but preparation for this migration is beginning.

Making Red Hat JBoss Enterprise Application Platform (EAP) work in a containerized environment, such as Nutanix or other container platforms, is a potential solution, although there has not been sufficient time to test it.

Red Hat JBoss Enterprise Application Platform (EAP) has been used since 2008 until now.

Red Hat JBoss Enterprise Application Platform (EAP) is very stable. Problems with Java runtime memory have been experienced occasionally.

Red Hat support has not been contacted for this product in a long time. The last support request was more than seven years ago and was related to memory or Java performance with Red Hat JBoss Enterprise Application Platform (EAP).

Return on investment with Red Hat JBoss Enterprise Application Platform (EAP) has not been measured. Other types of measurements are in place, but they are not related to the resources used. The resources used and the gains from those resources have not been correlated.

Scalability depends on the application type. For stateless applications, there is no problem scaling horizontally, and multiple instances of Red Hat JBoss Enterprise Application Platform (EAP) can be deployed. However, there are sometimes limitations in the possibilities available.

Red Hat support has not been contacted for this product in a long time. The last support request was more than seven years ago and was related to memory or Java performance with Red Hat JBoss Enterprise Application Platform (EAP).

Before Red Hat JBoss Enterprise Application Platform (EAP), other products were used for deploying applications, though it is uncertain if they still function. WebLogic, Jonas, and an open-source Apache option were used, though the specific name of the Apache product is not remembered.

Red Hat JBoss Enterprise Application Platform (EAP) was selected in 2008 when the organization switched from Jonas. Since then, no problems have been experienced, and the platform has supported applications that require 24/7 availability and millions of transactions per second. It has performed well, and it has not been changed until now. The next move to containers is something that must be tested and compared between available projects.

The installation of Red Hat JBoss Enterprise Application Platform (EAP) is straightforward and not a problem. It can also be installed with other tools such as Ansible  or Terraform .

The price of Red Hat JBoss Enterprise Application Platform (EAP) varies. A request for proposals is made each time, and two or three offers are received before one is selected. The offer includes not only the product but also configuration, deployment, and multiple other services.

No other solutions were discussed as alternates to Red Hat JBoss Enterprise Application Platform (EAP).

Microservices have been used for specific tasks, such as a microservice dedicated to signature functionality for PDF documents. The plan for the future is to migrate all applications and implement microservices during the next refactoring.

Other products have been used for deploying applications, though it is uncertain if they still function. WebLogic, Jonas, and an open-source Apache option were used, though the specific name of the Apache product is not remembered.

When comparing Red Hat JBoss Enterprise Application Platform (EAP) to WebLogic and other products, particularly open-source products, there are no significant differences observed.

Docker  is being used with Red Hat, which shares the same Linux core.

Work is being done with different products. Currently, only simple framework open-source solutions such as Docker  or Kubernetes  are used, but only for small projects.

Red Hat JBoss Enterprise Application Platform (EAP) is only deployed on-premises. Cloud deployment has only been tested for personal purposes on AWS .

The enterprise works primarily with Microsoft, and no services have been purchased from the AWS Marketplace .

This review has been given a rating of eight out of ten.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP)  is the deployment of our specific applications.

A specific example of an application I have deployed using Red Hat JBoss Enterprise Application Platform (EAP)  is some application pages about educational support from the government that stands out.

Red Hat JBoss Enterprise Application Platform (EAP ) fits into that process by helping with scalability, which is the most important factor because the product gives me scalability opportunities, such as G-group or load balance or other options.

The best feature Red Hat JBoss Enterprise Application Platform (EAP ) offers is G-group.

When I mention G-group, I am referring to clustering or grouping servers for high availability, which ensures that our application can support load balance and maximum uptime.

Red Hat JBoss Enterprise Application Platform (EAP) has positively impacted my organization by minimizing the downtime of applications, which gives me respect from users.

With time, we get results showing how much downtime was reduced. Clustering is the main standout feature for me.

I think documentation may need improvement for Red Hat JBoss Enterprise Application Platform (EAP).

Additionally, the support feature can be improved.

I have been using Red Hat JBoss Enterprise Application Platform (EAP) for five years.

I previously used Apache before Red Hat JBoss Enterprise Application Platform (EAP).

I gave this review an overall rating of eight.

I am working with Red Hat JBoss Enterprise Application Platform (EAP) , which is an application server used by Red Hat, but it is not used too much in RBC. It is a low-level application server in the same class as WebSphere or WebLogic, and Tomcat  is the same, but it is a low-level application server and not a high-end, super professional one.

Red Hat JBoss Enterprise Application Platform (EAP)  is very easy to use. I would say that even a high school individual can become accustomed to Red Hat JBoss Enterprise Application Platform (EAP ). It does not take too much to learn, so the learning curve is not steep.

Regarding support and better documentation or customization, I like what I have seen. However, I saw some areas of improvement in the documentation. From a support point of view, whatever support we get from IBM for Red Hat JBoss Enterprise Application Platform (EAP ) and for Red Hat, we are fine. We are a bank, and there are very specific agreements to have this support. I do not want to say 24 hours, seven days, but we need it right away. So nobody is fooling around at this level because we are a bank.

I have dealt with Red Hat JBoss Enterprise Application Platform (EAP) for around 10 years.

I think Red Hat JBoss Enterprise Application Platform (EAP) is stable.

I find it easy to stretch it out or shrink it regarding scalability; it is manageable.

I do not think it is expensive to have this, but I suppose the bank is paying a lot for maintenance and for customer support. Because if we have issues, we get a timely answer, and if you want a timely answer, you have to pay some premium.

I suppose if you are a small customer, things are seen from another angle regarding pricing.

I cannot answer regarding areas that Red Hat JBoss Enterprise Application Platform (EAP) can improve because I do not have an answer.

As for satisfaction with Red Hat JBoss Enterprise Application Platform (EAP), I am speaking from satisfaction, not from high availability because you cannot compare Red Hat JBoss Enterprise Application Platform (EAP) with WebSphere, for example, or with WebLogic, but from a peace of mind, it is fine. My overall review rating for Red Hat JBoss Enterprise Application Platform (EAP) is eight.