Red Hat JBoss Enterprise Application Platform with Support by MidVision

Red Hat JBoss Enterprise Application Platform (EAP) is primarily used for enterprise-level Java applications. Enterprise applications, Java applications such as banking and financial applications, insurance portals, government, e-governance applications, internal employee portals, customer self-service portals, ERP and HR management applications, and REST-based web services are deployed on Red Hat JBoss Enterprise Application Platform (EAP). These applications are typically built using Java EE or Jakarta EE technologies and packaged as a WAR or EAR file, which are deployed on Red Hat JBoss EAP. Due to a confidentiality agreement, the exact application names cannot be shared. However, they are enterprise business applications that support critical business operations, and the role involves ensuring that they are deployed, monitored, patched, and running reliably on Red Hat JBoss EAP.

Red Hat JBoss Enterprise Application Platform (EAP) is primarily deployed in a hybrid environment within the organization. Deployments are running on on-premises infrastructure as well as cloud platforms, depending on the application and customer requirement. Some workloads are hosted on cloud environments such as AWS and OCI, while others require on-premises deployment. This hybrid approach provides flexibility, supports business continuity, and allows the organization to meet different security and compliance requirements.

The experience with Red Hat JBoss Enterprise Application Platform (EAP) has been positive overall. It is a stable and reliable application server for enterprise workloads. It provides good performance, strong security features, and integrates well with enterprise environments. From a middleware administrative perspective, it is straightforward to manage deployments, monitor server health, and perform maintenance. The vendor documentation and support are also helpful when resolving complex issues. Overall, it has met the organization's requirements effectively.

The best features of Red Hat JBoss Enterprise Application Platform (EAP) are its stability, reliability, and enterprise-grade security. It provides excellent performance for Java enterprise applications and supports high availability, which is essential for production environments. The centralized management capabilities, easy deployment of WAR and EAR files, robust logging and monitoring, and seamless integration with Red Hat products and enterprise systems are also appreciated. A major advantage is the long-term support and regular security updates provided by Red Hat, which makes it a dependable platform for business-critical applications.

The features valued most are centralized management, robust logging, stability, and security on Red Hat JBoss Enterprise Application Platform (EAP). Centralized management helps administer multiple JBoss instances from a single interface, making configuration changes, deployments, and monitoring much easier and reducing administrative efforts. Robust logging is very useful for troubleshooting because it provides detailed application and server logs, allowing quick identification of the root cause of issues and reduction of downtime. The platform's stability is also appreciated, as it can reliably run business-critical applications for long periods with minimal issues. Strong security features, regular patches, role-based access control, and SSL support help maintain a secure environment. Additionally, the support for clustering and high availability is valued, as it helps ensure applications remain accessible. Even if one server experiences a failure, the ability to deploy applications without significant downtime and compatibility with standard Java EE and Jakarta technologies are valuable in day-to-day operations.

Red Hat JBoss Enterprise Application Platform (EAP) has had a positive impact on the organization by providing a stable and reliable platform for hosting enterprise applications. Its high availability has helped minimize downtime, ensuring that business-critical applications remain accessible to users. From an operations perspective, it has simplified application deployment, server administration, and maintenance, which has improved the team's efficiency. The robust logging and monitoring capabilities allow for quick identification and resolution of issues, reducing the mean time to resolution. Regular security patches and enterprise support from Red Hat also help maintain a secure, compliant environment. Overall, Red Hat JBoss EAP has improved application reliability, reduced operational overhead, and increased confidence in the production environment, allowing the organization to deliver better services to end users.

Overall, there is satisfaction with Red Hat JBoss Enterprise Application Platform (EAP), but there are a few areas where it could be improved. The initial configuration and setup can be complex, especially for new administrators, so a simpler installation and configuration experience would be helpful. The management console could be more modern and intuitive with better dashboards and built-in monitoring capabilities. Although logging is comprehensive, troubleshooting complex issues can still require significant analysis, so enhanced diagnostic tools and more actionable error messages would be beneficial. Better integration with modern DevOps and cloud-native tools out of the box, along with more automation for routine administrative tasks, would make the platform easier to manage and reduce operational effort.

Deeper integration with modern DevOps and cloud-native platforms would be valuable, such as improved support for Kubernetes and OpenShift, along with built-in automation for deployments, patching, and configuration management on Red Hat JBoss Enterprise Application Platform (EAP). Enhanced monitoring and observability with richer dashboards, predictive alerts, and easier integration with tools such as Prometheus and Grafana could also be beneficial. AI-assisted diagnostics that can help identify the root cause of issues more quickly would also be appreciated. Additionally, a more intuitive management tool and simplified upgrade process would make administration easier, especially for larger enterprise environments.

Red Hat JBoss Enterprise Application Platform (EAP) has been used for three years.

Red Hat JBoss Enterprise Application Platform (EAP) is very stable in the production environment. It has consistently delivered reliable performance for enterprise applications. Once it is properly configured and maintained, it runs for long periods with minimal issues. Very few unexpected crashes are experienced, and scheduled maintenance, patching, and upgrades are generally smooth. Its support for clustering, high availability, and enterprise-grade security also contributes to overall stability. From experience over the past three years, it has been a dependable platform for running business-critical applications.

Red Hat JBoss Enterprise Application Platform (EAP) scales well for enterprise workloads. It supports both vertical scaling by increasing server resources and horizontal scaling by adding additional JBoss instances in a cluster. As application traffic and business demand grow, the environment can be scaled without significant changes to the application. It also integrates well with load balancers and high-availability configurations, which helps distribute traffic efficiently and maintain performance. From experience, the platform has been able to handle increasing workloads reliably while maintaining good application performance.

The experience with Red Hat's customer support has been positive overall. The support team is knowledgeable and responsive, especially for production-critical issues. When support cases are raised, they provide clear guidance, troubleshooting steps, and when necessary, patches or recommendation fixes. The documentation and knowledge base are very helpful for resolving common issues and understanding best practices. While response times can vary depending on the severity of the issues, overall the support has been reliable and has helped maintain a stable production environment.

Red Hat's customer support is rated at nine out of ten. The support engineers are technically knowledgeable, responsive, and provide efficient solutions for production issues. The documentation and knowledge base are comprehensive, and timely guidance is usually received for troubleshooting and best practices. One point was deducted because response times can occasionally vary depending on the priority and complexity of the case, but overall the support experience has been very positive.

During the time in this role, Red Hat JBoss Enterprise Application Platform (EAP) has been used as the standard enterprise application server. Another application server in the production environment has not been personally used before Red Hat JBoss EAP. Therefore, a comparison cannot be made based on personal experience.

Overall, there is satisfaction with Red Hat JBoss Enterprise Application Platform (EAP), but there are a few areas where it could be improved. The initial configuration and setup can be complex, especially for new administrators, so a simpler installation and configuration experience would be helpful. The management console could be more modern and intuitive with better dashboards and built-in monitoring capabilities. Although logging is comprehensive, troubleshooting complex issues can still require significant analysis, so enhanced diagnostic tools and more actionable error messages would be beneficial. Better integration with modern DevOps and cloud-native tools out of the box, along with more automation for routine administrative tasks, would make the platform easier to manage and reduce operational effort.

A positive return on investment has been observed from using Red Hat JBoss Enterprise Application Platform (EAP), mainly in terms of operational efficiency rather than reducing headcount. Red Hat JBoss EAP's stability and reliability have helped reduce unplanned downtime, while its centralized management and robust logging have made deployments and troubleshooting more efficient. As a result, issues have been able to be resolved faster and less time has been spent on routine maintenance. Although exact financial figures are not available, approximately thirty to forty percent improvement in deployment efficiency and a noticeable reduction in the time required to diagnose and resolve production issues have been observed. Overall, this has helped improve productivity and service availability without requiring additional administrative resources.

There is not direct involvement in pricing, licensing, or contract negotiation, so exact costs of Red Hat JBoss Enterprise Application Platform (EAP) cannot be commented on. From an operational perspective, the licensing process has been smooth, and regular updates and enterprise support from Red Hat are provided. Overall, the value comes from the platform stability, security, long-term support, and reliability for running business-critical applications, which justifies the investment for enterprise environments.

Although AI capabilities with Red Hat JBoss Enterprise Application Platform (EAP) have not been used in the environment, they would be expected to be highly accurate and reliable, especially for enterprise use. AI features would be expected to provide precise root cause analysis, intelligent log analysis, proactive recommendations for performance tuning, and accurate security insights with minimal false positives. Since enterprise environments require high reliability, any AI-generated recommendations would be expected to be transparent, explainable, and easy for administrators to validate before taking action. If Red Hat delivers AI capabilities with that level of accuracy and trustworthiness, they would significantly improve operational efficiency.

The advice would be to clearly understand application requirements and infrastructure before implementing Red Hat JBoss Enterprise Application Platform (EAP). It is an excellent choice for organizations running enterprise Java applications that require high availability, security, and long-term stability. Following Red Hat's best practices for configuration, security hardening, and patch management from the beginning is also recommended. Investing time in proper monitoring, logging, backup, and performance tuning will help get the most value from the platform. If modernizing the environment is being planned, it is also worth considering integration with cloud platforms and automation tools such as Ansible and OpenShift. Overall, for organizations looking for a reliable, enterprise-grade Java application server with strong vendor support, Red Hat JBoss Enterprise Application Platform (EAP) would definitely be recommended. This review has been given a rating of nine out of ten.

The typical use case is to deploy Red Hat JBoss Enterprise Application Platform (EAP) on premises, which is your on-premises native platform. You can manage everything, and you have a lot of freedom to do deployments and create new inventions such as integrating Red Hat JBoss Enterprise Application Platform (EAP) with GitHub, then integrating with Jenkins to collect day-by-day logs or previous day's logs with the help of a pipeline, and we can do small deployments with the help of GitLab plus Jenkins.

The best part is the deployment because we do the deployment very easily. We cannot take any help from other people, and when we get stuck anywhere and the deployment fails, we read the log to figure out what kind of issues happened. Most of the time, we do not face critical issues; it's the code-based level issues we faced at that time.

The installation part is very easy, and regarding high-level availability, once we understand how that high availability works, we can configure it very easily. Otherwise, it is a little difficult to configure.

We faced the limitation of Red Hat JBoss Enterprise Application Platform (EAP) version upgrades, which require developers to improve their code as well. Java is a dependency of Red Hat JBoss Enterprise Application Platform (EAP). Once we upgrade or install any new Red Hat JBoss Enterprise Application Platform (EAP), our Java version also gets upgraded.

We face issues with coding and deployment due to Java upgradation, and a developer needs to change his code based on the Java version. Configuration can be tricky.

I have been using this solution for six years in total.

Red Hat support is good, and I am giving it a nine out of ten.

I am continuously working on the Red Hat platform.

We are not upgrading that Red Hat JBoss Enterprise Application Platform (EAP) into version 7.4 from an existing installation. We freshly installed Red Hat JBoss Enterprise Application Platform (EAP) 7.4 into a new Linux machine, and then developers provided us with WAR files that we deployed into the new version. We are also facing challenges regarding the code, so we sit with the developer and figure out what kind of issues we find.

For my side, it was my manager and three to four members in my team at that time. Overall, five people were involved in the deployment from my side.

The licensing part is handled by the manager and other teams, so that does not come to me.

We have not tested other third-party tools; we directly implemented on the vSphere VM server.

I have not had any kind of subscription with Red Hat Learning Subscription. In a previous company, I worked on Red Hat JBoss Enterprise Application Platform (EAP). Currently, I am working on Red Hat OpenShift platform. Last year I utilized Red Hat JBoss Enterprise Application Platform (EAP), but currently I am working on Red Hat OpenShift platform.

When I was in a previous company, for the last six years, we worked on Red Hat JBoss Enterprise Application Platform (EAP) through the client. We did a small project for the Mahindra & Mahindra company, migrating Red Hat JBoss Enterprise Application Platform (EAP) into new Red Hat JBoss Enterprise Application Platform (EAP). They were using version 7.3 and wanted to upgrade Red Hat JBoss Enterprise Application Platform (EAP), so we planned to install new Red Hat JBoss Enterprise Application Platform (EAP) version 7.4 at that time.

We have worked over a year on the deployment of Red Hat JBoss Enterprise Application Platform (EAP). We took a year to give that solution, and even though they are migrating, they are migrating 70 to 80 VMs into the new Red Hat JBoss Enterprise Application Platform (EAP) platform.

Resource utilization depends on our application traffic because of how that application works and how much traffic comes in one millisecond or two milliseconds. Based on this, we calculate the 5 or 15 minutes traffic, and after that, we allocate the resources of Red Hat JBoss Enterprise Application Platform (EAP) servers, giving 32 GB RAM and 8 to 12 core CPUs to each Red Hat JBoss Enterprise Application Platform (EAP) server at that time.

We use the HTTP connector and configure it inside the standalone.xml file. If one of the instances stops, the traffic automatically routes to another instance, so with the help of that HTTP connector, we manage high availability.

At that time, we used the AMQ server to push the messages whatever messages are coming. We used the AMQ server for enterprise class messaging.

I need a hint of which third-party tool you mean for integration. I have no idea because we only use the WAR files, and based on this, we monitor the transactions through PL/SQL, how many transactions are coming and how many transactions are lost. Based on this, we can rectify.

I gave this review a rating of ten out of ten.

I assessed the modular architecture in terms of enhancing resource utilization as very scalable. I used this solution because we had almost around 450 APIs running in that organization. I wanted to compile all those APIs into one place, and therefore I used this particular tool. This was a very good Java application server which is commonly used to deploy and run Java-based applications. Our application was also Java-based, therefore it was a very good operating system for us.

The cloud-native design definitely helps with DevOps integration. Migrating to cloud-native architecture helps with DevOps integration because when migrating large applications and large monolithic applications, sometimes Red Hat JBoss Enterprise Application Platform (EAP) gets a little expensive and also risky as well, because sometimes you tend to lose some of your data from it. But apart from that, it was pretty good.

The implementation of highly transactional applications on Red Hat JBoss Enterprise Application Platform (EAP) definitely improved our customers' reliability. When we embedded our APIs into the system, we removed the methods in our code and replaced them with the caches. Once we did that, our application experienced a surge of around almost 64% or 65%, an increase in the transaction speed and also in the customer onboarding journey. I would definitely rate that a solid 10.

I found this solution valuable and it was a pretty good solution.

I believe that Red Hat JBoss Enterprise Application Platform (EAP) still counts weaknesses and disadvantages, such as there could be better memory management. That could be addressed in this, or probably the deployment downtime. Sometimes it usually takes somewhere around a considerable amount of time. That was our challenge that we faced when we were actually integrating it in our system.

I used Red Hat JBoss Enterprise Application Platform (EAP) for almost about four or five years.

The initial setup was not pretty complex. It was not the setup which was difficult. The integration complexity was not that big of a challenge for us because we had good resources. My actual challenge was that when we were troubleshooting the production issues, the logs from Red Hat JBoss Enterprise Application Platform (EAP) usually took some time for us to check and determine what exactly the issue was about. In terms of scalability and other complex features, it was a very robust solution. I would definitely rate it to anybody who would want to use this application for their banking servers.

The last experience I had with Red Hat was in November 2025. I did not utilize the high-availability clustering feature myself. I had a technical resource who was basically integrating that feature, and I introduced that and they were using it for operations. From my perspective, I would rate the product from 1 to 10 somewhere around a seven or eight. We basically worked with Red Hat JBoss Enterprise Application Platform (EAP) as our vendor, taking the subscription, and we were working as a customer for their services rather than as an exact partner. I would rate the product overall as a seven out of ten.

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.

My main use case for Red Hat JBoss Enterprise Application Platform (EAP) is for a web application for any customers we have on my main apps.

A specific example of how I use Red Hat JBoss Enterprise Application Platform (EAP) with my web application for my customers is that I customize a payment link. We call it on other platforms, and we can process the monthly payment.

Red Hat JBoss Enterprise Application Platform (EAP) offers excellent features, and it is very intuitive.

The particular feature of Red Hat JBoss Enterprise Application Platform (EAP) that I find especially useful is the main console, which is very flexible and easy to use.

Red Hat JBoss Enterprise Application Platform (EAP) has impacted my organization positively because it is a powerful platform and we can develop powerful applications very quickly.

An example of how being able to deploy powerful applications quickly has helped my organization is that for the most recent deployment, we were able to deploy this application in three weeks, which is very fast for us.

I cannot speak to how Red Hat JBoss Enterprise Application Platform (EAP) can be improved.

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

Red Hat JBoss Enterprise Application Platform (EAP) is a very stable platform in my experience.

Red Hat JBoss Enterprise Application Platform (EAP) is very fast and very strong in terms of scalability.

I have had one or two experiences with Red Hat JBoss Enterprise Application Platform (EAP) support team, and I found them very good.

I find this interview to be very good. The process is very easy and quick, and it is more comfortable overall. I would rate this product a 10.

My main use case for JBoss is the administration of the application mostly.

My use case implies installation, configuration, and setting JBoss EAP on different systems such as Linux, Windows and configuring the standalone or domain. This implies working with the web console, automation tools, and CLI. Additionally, it involves securing it, implementing authentication, RBAC or Role-Based Access Control, SSL, TLS, and so on. Performance tuning, thread pool management, logging, and clustering are mostly what I have done with the product.

JBoss has positively impacted my organization by enabling deployment with enterprise extensions that were needed, particularly for integration with directory services. The difference came in implementation, and it offers a significant role in deployment that is scalable, especially when using a clustering way of working with it.

Specific outcomes include improved deployment times due to modular architecture leveraging lazy loading, which affects the time taken to deploy archive, war, or ear files, and the deployment success rate without server restarts. This impact has significantly enhanced stability and reduced downtime. Lower memory consumption during deployment has been apparent thanks to subsystem isolation, while asynchronous deployment handling has reduced spikes and led to fewer errors with better validation overlay support in cases of failed deployments or rollback events. Additionally, I have enabled quick fixes without full redeployments, particularly with frequent overlay-based updates.

In my experience, the best features JBoss offers include the modular architecture where the services are loaded when needed, and the cross-platform compatibility that allows it to run on any operating system that supports Java. The high availability and clustering, distributed support, session replication, and load balancing using Infinispan stand out. The security enhancement such as native support of OpenID Connect or JAS for flexible authentication is another outstanding feature. Others include flexible deployment modes and control of session affinity, which is fine-tune control over load balancer stickiness strategies for managing web sessions. Furthermore, global directory support allows for easily adding shared modules to deployments without class path. It stands out because it is a full-stack platform for building today's cloud-ready Java applications that are scalable and secure, blending enterprise-grade features with open-source flexibility. It is the top choice for organizations that need reliability today.

For underrated features, server group in domain mode allows grouping servers and applying configuration or deployments across them simultaneously. Not many people know about the CLI scripting with batch mode or Vault and Credential stores, where sensitive configuration values can be stored without hardcoding them into XML files. Additionally, built-in metrics and subsystem isolation, where every subsystem logging, messaging, or web services can be tuned independently, provide fine-grained control over performance and behavior. This is why subsystem isolation is important, and many administrators have not utilized it that way.

JBoss can be improved significantly, especially regarding deployment overlays that need updates to apply quick fixes or environment-specific changes without redirecting the archive. Enhancements in CLI scripting for automatic deployments or rollbacks and having an automated way of updating in the future for pack changes and version transitions are critical. More details about the update progress of package installations, artifacts downloading, as well as automation for modules and configurations applied are needed. Additionally, features for drifting and reverting would be worthwhile. We leverage domain mode with server groups to enforce synchronized rollout strategies across clusters without downtime or config drift.
Subsystem isolation doesn’t just reduce memory usage it allows us to apply GC tuning and diagnostic tracing at the service level, not the container level.
Our CLI scripting has been backed by pre-validated batch execution pipelines, eliminating human error during hotfix rollouts and version transitions.
Using overlays in conjunction with marker files, we've created an audit-friendly patching workflow that doesn't require full archive redeployments.
Changes in the future need to align with today's directions regarding the most evolutionary topics of Jakarta EE progression. As Jakarta EE progresses, newer specifications such as Jakarta Data and Jakarta NoSQL or AI-assisted diagnostics are necessary.
We’ve integrated JBoss metrics output with Prometheus exporters, enabling real-time subsystem-level observability and predictive scaling alerts.
By aligning with Jakarta EE's modular progression, we've positioned our stack to adopt emerging specs like Jakarta NoSQL without disruptive upgrades.
JBoss’s flexible threading model allowed us to apply workload-specific executor policies, preventing starvation in high-concurrency deployments.
More straightforward updates and rollbacks need to be done with the CLI, alongside improved observability, such as native support for OpenTelemetry or enhanced DevOps tools with command-line interfaces and automation features. Support for YAML-based configuration is crucial, especially in a GitOps deployment style, along with cloud-native enhancements such as integration with Kubernetes, OpenShift, or newer technologies.
I would like to see JBoss reassess its executor configuration controls and consider offering default workload profiles such as I/O-bound, CPU-heavy, or async-first—to optimize threading strategies out of the box.
On the cloud-native side, it’s important to validate container readiness and expand operator-driven automation for Kubernetes, especially focusing on CRD evolution and stateless rollout support. I would also recommend improving workflow transparency by providing clearer feedback during pack updates, including artifact download status, config sync logs, and rollback outcome visibility.

I have been using JBoss for more than 10 years.

JBoss has remained reliable and fully functional across workloads, and I haven’t encountered any critical failures that would impact operations—especially when compared to prior solutions like Oracle WebLogic. Its resilience continues to make it a dependable backbone for enterprise middleware needs.

JBoss's scalability is effective. Its architecture is elastic, meaning it can handle growing workloads smoothly, whether it's scaling up for high demand or scaling out across clustered nodes. This elasticity makes it ideal for dynamic environments where resource usage can vary.

With newer Java versions, memory management has become noticeably more efficient. Improvements in garbage collection and memory recovery mean the platform performs well under load, with less risk of memory leaks or bottlenecks. This leads to better application stability and faster response times, especially during peak usage.

I would describe the experience as reliable and professional especially valuable when you're running JBoss in production and uptime matters. My experience with JBoss customer service and support has been dependable overall. When using the Red Hat-supported version, the service team was responsive and knowledgeable. For issues involving configuration, security realms, or integration quirks, I usually received clear guidance and practical solutions. The response time was more reasonable than questionable and in most cases, the support escalated technical problems efficiently when needed.
That said, for more complex or niche setup scenarios, I sometimes had to dig through documentation or lean on community channels like forums or GitHub discussions.
The support is solid, but having technical familiarity helps speed things along.

Before JBoss, I used Oracle WebLogic. I switched primarily because Oracle changed their solution's availability as well as the way they handled licenses, which became unfriendly for customers, leading to extensive discussions regarding licensing costs. Therefore, the most crucial factor for switching was the company direction of Oracle.

When using JBoss in standalone mode, installation is quick and simple you can get it running with minimal effort, especially for development or testing. It’s also great that it works on any operating system that supports Java and compatibility isn’t usually an issue. However, things can get more complex when you start configuring domain mode, especially if you’re setting up host controllers, managing server groups, or trying to centralize control across multiple servers. Integrating with other services by setting up LDAP for authentication or configuring secure connections it requires more time and planning. Once preparing it for production use, tuning the JVM, thread pools, logging levels or isolating subsystems requires deeper understanding. Support-wise, JBoss offers a lot of documentation, but beginners might find it a bit hard to follow at first.
The community is active and helpful, especially on Red Hat channels, but solving specific issues sometimes means a bit of experimentation.
if you're planning to use JBoss seriously, make sure you invest time in learning the architecture, automate where possible using command-line scripts and start monitoring from the first implementation day. Those choices can make the difference between a smooth experience and a frustrating one.

We implemented JBoss using our in-house team. Our engineers were already familiar with Java-based middleware and deployment strategies, we didn’t need to rely on an external vendor. That gave us more control over the setup process, especially around automation, performance tuning, and integration with existing services. It also saved us from additional consulting costs and helped us tailor the implementation to fit our environment exactly as needed.

We’ve seen a marked reduction in downtime and a major boost in system stability, resulting in fewer outages. One of the biggest wins has been the cost savings especially compared to Oracle WebLogic thanks to JBoss’s more affordable licensing model, particularly when bundled with Red Hat or OpenShift.

Its scalable design, whether deployed as a standalone system, clustered setup or through modular subsystems, JBoss has allowed us to tailor infrastructure to match demand. Using deployment overlays and scripting, we've sped up rollouts and maintained performance through smart JVM tuning.

Overall, we calculated a payback period of just around 5 months and a few days which speaks volumes and it’s been a strategic move with clear financial benefits.

My advice is to carefully review the licensing options before setting up JBoss. While using the free version WildFly, most companies go for the paid Red Hat JBoss version, which comes with extra features and support. The setup itself isn’t expensive, but getting it right often involves extra costs for team training, automation setup and performance tuning. For could environments loke OpenShift or Kubernetes it is important to make sure your licensing covers that so you don’t run into surprises later.
It’s smart to plan ahead and look beyond the software cost your return on investment will likely come from less downtime, smoother deployments and better scalability.

Before choosing JBoss, I evaluated other options, but the only one that adequately covered all needed aspects from different customers was Oracle WebLogic.

My advice for others looking into using JBoss is to understand the architecture before deploying and to differentiate between standalone and domain mode. Automating early and using command-line based scripts is essential. Monitoring everything, tuning JVM and thread pools, and using deployment overlays for quick fixes to minimize downtime through patches is crucial as well. Careful planning regarding licensing is the most important factor for customers.

It is crucial to invest time into learning the security standards for authentication and encryption in JBoss. This flexibility offers more than legacy JS solutions.

On a scale of 1-10, I rate JBoss an 8 out of 10.