JBoss Enterprise Application Platform Reviews

JBoss Enterprise Application Platform is mainly used for hosting and managing Enterprise Java-based applications in a stable and scalable environment.

We have a backend service named Search Service, which is written in Java, and it is deployed using JBoss Enterprise Application Platform. We use it to deploy a multi-modular enterprise application handling internal business workflows and REST APIs, and JBoss Enterprise Application Platform provides us centralized application management, security, and transaction handling.

The main use cases are transaction management, middleware services, microservices, and legacy enterprise applications, and it is very effective for that kind of purpose.

The best feature that stands out is the strong support for Enterprise Java workloads, along with high stability and transaction management. It provides stability for the services to get deployed, and we can easily manage the transactions that happen via the REST APIs, which is great in that regard. It also provides centralized application management, so if an application is deployed and needs to be used through multiple places, centralized application deployment management is possible.

The centralized management clustering capability is very useful for high availability enterprise deployment. This centralized application management is beneficial because the application, the search service we have written in Java, has simplified deployment, and operational control across environments is also easy. It helps our team since it has centralized deployment management, allowing applications to be deployed and updated from a centralized CLI or console, which reduces manual server-by-server management and improves deployment consistency. It also provides easier monitoring and troubleshooting, which is excellent; if an issue occurs, such as the search service failing, we could quickly identify which node or deployment was affected instead of manually checking multiple servers.

This has definitely given us positive feedback; that is why we have been using it for around 1.5 years, and it is still coping with our applications. The impact is that application stability has improved quite a bit, and deployment consistency allows us to deploy, update, restart, and check the logs all at once without checking multiple servers, along with improved operational management for Enterprise Java services.

There can be multiple areas for improvement; JBoss Enterprise Application Platform is stable, but the startup time, modernization of tools, and UI management experience could be enhanced, as it feels heavyweight compared to newer cloud platforms such as AWS. Configuration complexity is present, and for beginners, configuring it can be challenging.

Easier upgrade migration tooling for enterprise applications can also be provided, alongside better dashboards and more modern observability and monitoring integration. More lightweight cloud-native deployment patterns could also be implemented.

I have been working here for the last three years.

JBoss Enterprise Application Platform is quite stable, and because it is backed by Red Hat, continuous support and fixes are ensured.

Our initial setup with Apache Tomcat was relatively less in scalability. We wanted a solution that offered centralized management, faster deployment, and streamlined logging mechanisms, which JBoss Enterprise Application Platform provides, making it very effective for our large applications since everything is managed in one place.

Customer support is very good; I had a conversation with them regarding an issue with deployment. We raised a ticket to the JBoss team, and they responded within about 8 to 9 working hours, providing a perfect solution, as their team is ready for any queries that arise.

Previously, we used Apache Tomcat, which was a lightweight container-based solution that had lower pricing initially. While it was adequate for simple Java applications, challenges arose as applications grew larger, requiring additional tooling and configuration for enterprise transaction management and centralized admission. The previous setup resulted in higher operational complexity and fragmented management, making it difficult to manage multiple application configurations and resulting in inconsistent environments.

For our enterprise-level application integration, it is manageable and straightforward to connect JBoss Enterprise Application Platform with other systems we use.

We have seen a return on investment; it may not be substantial, but we experienced reduced downtime risk, better operational consistency, and enterprise-grade support for production. The reduced deployment and configuration issues and improved operational team time savings—a reduction in deployment effort of about 30 to 40%—contributed to lower downtime and stability improvement.

Pricing-wise, it is very reasonable, with an initial pay-as-you-go structure, meaning the more you use, the higher the cost. Initially, we utilized a subscription-based model for enterprise licensing through Red Hat, and pricing included enterprise support, security patches, certified updates, and long-term maintenance. The initial setup cost was moderate due to the required enterprise planning; clustering, security, and environment configuration took time. However, once standardized, deployment became much more manageable and predictable. Licensing provided reliable enterprise support, stable certified releases, good documentation, and patch management. There were challenges as costs can significantly rise at larger scales, making it more expensive than alternatives such as Apache Tomcat, which was a lightweight container solution. For mission-critical enterprise Java applications, the stability and enterprise support justified the investment.

We did evaluate other options, notably Apache Tomcat. It was lightweight and suitable for smaller Java-based enterprise applications. However, as we grew and required more flexible one-place solutions, we switched to JBoss Enterprise Application Platform, which provided the necessary central management and strong enterprise features that Tomcat lacked.

If your Java-based application is small and central management is not needed, you can consider other solutions; however, if you want a comprehensive solution in one place, JBoss Enterprise Application Platform should be taken into consideration as it provides everything from logging to deployment and centralized management to authorization and authentication, while supporting various library frameworks.

JBoss Enterprise Application Platform deserves an 8 out of 10 because, strength-wise, it is very stable for enterprise workloads, with strong transaction management and mature Java EE support, making it excellent for large monolithic enterprise applications. However, it does feel heavyweight compared to newer cloud-native platforms; the startup times are slower than alternatives, and some tools feel somewhat outdated.

Security-wise, there are multiple security features in JBoss Enterprise Application Platform. It includes RBAC for role-based access management, allowing different teams to control access levels to deployment, monitoring, and server management. There is also an authentication system for easier centralized identity management. It provides secure management interfaces to reduce exposure of management operations. Additionally, it has security domains and authentication frameworks supporting JAAS and electronic security frameworks, offering flexibility in authentication and authorization configuration. Most importantly, it is backed by Red Hat, a company that prioritizes security with regular security patches and vulnerability fixes.

Reliability-wise, JBoss Enterprise Application Platform can improve a little; however, it provides strong performance for enterprise workloads. For large-scale applications with many transactions and stateful business workflows needing high uptime and stable transaction processing, JBoss Enterprise Application Platform is a good choice. Compared to Tomcat, which is a lightweight servlet container requiring more external integration and having a faster setup and lighter footprint, JBoss Enterprise Application Platform offers stronger enterprise capabilities out of the box, necessary for our applications.

My main use case for JBoss Enterprise Application Platform is Enterprise Java application hosting and management. I use it as my secure runtime environment to host mission critical Jakarta EE, formerly Java, web applications and handle everything from transaction processing to web service orchestration.

One of the features I would like to highlight in JBoss Enterprise Application Platform is Centralized Domain Management and Secure Management CLI. My remote middleware and DevOps team use the secure web console or JBoss CLI to manage server configuration, data sources, and runtime properties from any location. We can easily export or share configuration snapshots allowing our remote engineers to reproduce identical environment configuration instantly for troubleshooting.

Centralized Domain Management and secure CLI in JBoss Enterprise Application Platform has introduced significant improvements in our environment, mainly timely error data. Red Hat provides critical security updates and CVE patches quickly, keeping our runtime well protected against security flaws including unsafe deserialization or request smuggling. It shares its root with WildFly, the upstream community forums, which are incredibly active and helpful for resolving development level queries.

JBoss Enterprise Application Platform has impacted my organization very positively. It eliminated tool sprawl and infrastructure inconsistency. It gave my DevOps and DevSecOps teams a predictable, unified platform to manage, audit, and secure all enterprise Java endpoints in one single place, significantly improving my overall MTTR during production updates.

The management console and XML configuration layout have a somewhat steep learning curve for junior engineers who are accustomed to simpler bare-bones web servers.

I have been using JBoss Enterprise Application Platform for about three years to manage and host my high volume corporate Java middleware environments.

JBoss Enterprise Application Platform is exceptionally stable because it is a hardened, commercially tested downstream product based on the open source WildFly project. It handles heavy enterprise transaction volumes smoothly. Its modular architecture ensures that subsystem failures do not bring down the entire application server instance.

JBoss Enterprise Application Platform's scalability is top-tier. It supports full clustering with Infinispan for distributed caching and state replication. Whether scaling up on bare-metal servers or horizontally scaling in containerized cloud clusters using cloud discovery protocols, it manages user session data seamlessly across all nodes.

Customer support for JBoss Enterprise Application Platform is highly mature. The official documentation, including Red Hat's official documentation, is some of the most thorough in the industry. Red Hat Knowledge Bases provide access to verified solutions. The community synergy shares its root with WildFly, and the upstream community forums are incredibly active and helpful for resolving development level queries.

I previously utilized a mix of open source Apache Tomcat servers and fragmented legacy middleware before JBoss Enterprise Application Platform. I switched because Tomcat lacked built-in enterprise management capabilities such as clustered session replication and unified transaction coordinators out of the box, forcing me to manually maintain complex customized third-party add-ons.

I have seen major operational ROI with JBoss Enterprise Application Platform. By consolidating my fragmented applications and deployments under JBoss domain mode and automating configurations with Ansible, I reduced my administrative overhead by 40%. Additionally, its optimized memory footprint allowed me to double my server density, running more application instances on the same underlying virtual hardware.

Regarding pricing, the procurement experience was very straightforward. I used the AWS Marketplace to deploy official JBoss Enterprise Application Platform Amazon Machine Images on a pay-as-you-go annual contract basis. This allowed me to spin up the pre-configured licensed instance on RHEL immediately while consolidating all licensing costs into my unified AWS cloud infrastructure bill.

I evaluated other options before choosing JBoss Enterprise Application Platform. As I mentioned, I previously used Tomcat and other open source tools before reaching JBoss Enterprise Application Platform.

My primary advice for others looking into using JBoss Enterprise Application Platform is to master the JBoss CLI early on. While the web GUI is excellent for monitoring, using the CLI allows you to write repeatable scripts for configuring data sources, security domains, and system properties. This approach sets a perfect foundation for building GitOps or automated CI/CD infrastructure pipelines down the line.

I want to mention the security of JBoss Enterprise Application Platform. It completely aligns with my corporate security compliance standards. The Elytron security framework is a standout feature. It provides a single unified way to configure both management access and application security, including SSL, RBAC, and LDAP authentication. I would give this product a rating of 9 out of 10.

Our main use cases with JBoss Enterprise Application Platform were that we are an application software developer, developing the channel platform, the internet banking, and the mobile banking for the banks.

The channel platform was hosted on JBoss Enterprise Application Platform.

JBoss Enterprise Application Platform's best features include that it was very simple to install and enabling clustering between two instances was simpler than compared to WebSphere or WebLogic. Clustering became very much easier, and setup was very straightforward.

I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container. The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state. It never happened in JBoss Enterprise Application Platform. Other application servers typically degrade over time, and the application resources can become hung.

The memory utilization and the heap garbage collection that was running was very efficient, so the resource utilization was better. The robust security model of JBoss Enterprise Application Platform contributed positively to our data integrity and compliance in our development processes, and it was very good.

In my opinion, there are areas that could be improved with JBoss Enterprise Application Platform, such as the management console.

I am not certain whether it has all of the enterprise features incorporated such as what IBM WebSphere has, including real-time performance monitoring of your application, monitoring your JVM heap graphs, or even the CPU utilization graphs. I am not certain whether this is present or not.

We thought that if application performance monitoring tools were already part of the management console at runtime, it would be very helpful.

The last time I used JBoss Enterprise Application Platform was version 7.7.4 recently.

I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container.

The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state.

My thoughts on JBoss Enterprise Application Platform's pricing is that from a subscription model perspective, the price was very reasonable compared to other application servers and other commercial products. JBoss Enterprise Application Platform was much better in terms of cost.

I have experience with JBoss Enterprise Application Platform, as we earlier used it, but we moved completely to Tomcat.

I did not use JBoss Enterprise Application Platform with AWS as our main cloud provider, as it is a standalone solution.

We generally put it on premises at the financial institutions.

I am not certain if Red Hat uses AWS as their cloud provider for this product.

We did utilize the JBoss Enterprise Application Platform management console. We were running both in standalone mode as well as the domain mode.

We are more of a modular monolith, so we did not write microservices.

I did not try anything on the cloud, so I am probably not aware of its adaptability between cloud and on-premises deployments.

I do not know much about JBoss Enterprise Application Platform's support or the documentation, as we did not get into that too much.

Our company originally purchased JBoss Enterprise Application Platform through Red Hat partnerships.

The reasons I rate it so highly are that it was simple, lightweight, and the performance was very good. I rate this product a 9 out of 10.

I have an application with JBoss Enterprise Application Platform and a middleware. I used JBoss Enterprise Application Platform for about eight years until 2016. I implemented a ticketing solution and middleware application to connect several databases and several languages, creating an omnichannel experience. I have two kinds of implementations in the commercial area, including ticketing and e-commerce with the same middleware, and I used it for bank financials. One bank in Guayaquil used my middleware.

The best feature for JBoss Enterprise Application Platform for me is high availability, and it is very strong. It is strong because it supports many concurrencies.

I lost one opportunity for licensing to a bank that was implementing on-premises. It was too expensive to license JBoss Enterprise Application Platform for each process. The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000. Because they are a bank, they need local support, not international support. For that reason, it was too expensive for them, and we were discarded and could not implement the solution.

I used JBoss Enterprise Application Platform for about eight years until 2016.

I do not have any problems with this deployment.

Because the bank needed local support rather than international support, it was too expensive for them, and we were discarded.

I offered implementing the same services in Microsoft IIS, but they needed several months to develop the new solution, and they did not have time for that developer.

JBoss Enterprise Application Platform is easy to implement.

The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000.

I offered implementing the same services in Microsoft IIS, but they needed several months to develop the new solution, and they did not have time for that developer.

I use JBoss Enterprise Application Platform management both through the management interface and through command line. I use JBoss Enterprise Application Platform for deployment in Microsoft servers, and in Linux and Oracle Linux. I am trying it in my own cloud and have deployed JBoss Enterprise Application Platform on Oracle Cloud to implement it in the cloud, which is very good. My overall rating for this solution is ten out of ten.

For JBoss Enterprise Application Platform, we use it to deploy applications. It provides clusters and all the functionality associated with them. We can also achieve high availability and scalability for the application.

In financial and banking, we mostly use JBoss Enterprise Application Platform. It is widely used for core banking systems, including internet and mobile banking platforms, as well as peer-to-peer transaction services. Most high-volume transaction applications benefit from its ability to handle complex business logic with JBoss Enterprise Application Platform messaging services, making it ideal for applications requiring guaranteed message delivery and distributed transactions.

In JBoss Enterprise Application Platform, we can use horizontal auto-scaling for environments hosted on platforms like OpenShift. JBoss Enterprise Application Platform 8 allows applications to automatically scale up or down based on seasonal workloads. This lowers infrastructure costs while maintaining optimal responsiveness during traffic spikes. For modern security standards, you can upgrade legacy applications.

Modernizing Java applications on JBoss Enterprise Application Platform drastically improves enterprise scalability, deployment speed, and security. Upgrading to a modern JBoss Enterprise Application Platform environment optimizes platform performance by leveraging Jakarta EE specifications, reducing memory footprints, and streamlining containerized cloud deployments.

JBoss Enterprise Application Platform's best features are that it provides specialized support for complex authentication scenarios, including desktop-based SSO with Active Directory or Kerberos, and browser-based SSO using SAML.

In addition to the out-of-the-box functionality, JBoss Enterprise Application Platform supports additional use cases for SSO, including SAML for browser-based SSO and desktop-based SSO. I worked on a few legacy projects built on JBoss Enterprise Application Platform, and my experience with it was horrible, which was probably mostly due to the quality of the projects. I can say that applications with JSP servlets using web frameworks such as Struts, JavaServer Faces, and Cocoon can be deployed on JBoss Enterprise Application Platform.

Some changes could be added to improve the platform. We can utilize bootable JARs to package and deploy applications quickly. This streamlines continuous integration and continuous delivery (CI/CD) pipelines, minimizes environment drift, and allows for much faster startup times in cloud and container setups.

For environments hosted on platforms like OpenShift, JBoss Enterprise Application Platform 8 allows applications to automatically scale up or down based on seasonal workloads. This lowers infrastructure costs while maintaining optimal responsiveness during traffic spikes.

JBoss Enterprise Application Platform offers high-performance clustering and caching. By taking advantage of JBoss Enterprise Application Platform clustering, you can implement in-memory caching for frequently accessed data. This reduces the database load and speeds up transaction response times.

You can update legacy Java authentication to navigate OpenID Connect.

I have been using JBoss Enterprise Application Platform for the last three years, and it has been very good.

It is the most stable application platform I have ever seen for Linux.

Modernizing Java applications on JBoss Enterprise Application Platform drastically improves enterprise scalability, deployment speed, and security. Upgrading to a modern JBoss Enterprise Application Platform environment optimizes platform performance by leveraging Jakarta EE specifications, reducing memory footprints, and streamlining containerized cloud deployments.

JBoss Enterprise Application Platform provides good support. Whenever we face issues, we reach out to JBoss Enterprise Application Platform support, and we receive faster support from the team.

I previously used Oracle. Oracle required licensing, but JBoss Enterprise Application Platform is open-source, so for that reason, we switched to JBoss Enterprise Application Platform.

Modernizing Java applications on JBoss Enterprise Application Platform, Red Hat, and JBoss Enterprise Application Platform or WildFly drastically improves enterprise scalability, deployment speed, and security. Upgrading to a modern JBoss Enterprise Application Platform environment optimizes performance by leveraging Jakarta EE specifications, reducing memory footprints, and streamlining containerized cloud deployments.

Based on my experience, I rate JBoss Enterprise Application Platform 10 out of 10 because it is easy to deploy and user-friendly for newcomers and new employees.

I would rate it 9 out of 10.

I can suggest to newcomers and new employees to use JBoss Enterprise Application Platform for career growth. It is a very stable and useful product for your career. My overall review rating for this product is 9 out of 10.

Neutral

I deploy the application as .war or .ear, which is part of Java Enterprise.

I use it for resources for the server, and I coordinate with the developer for deployment of the web application.

In my job, I am an administrator because I lead the team for development in Java.

I use the JBoss Enterprise Application Platform 7 EAP, and I appreciate the pool connection for the database the most.

The memory usage and memory RAM could be improved. JBoss Enterprise Application Platform could improve the use of memory on a server.

Sometimes, I observe the memory usage at 100% for the server, and this issue could be improved.

I have used JBoss Enterprise Application Platform for about five years, and I know how to start the system.

Regarding scalability capabilities, I am uncertain.

I am unaware of their pricing. I normally use Tomcat, then I use JBoss Enterprise Application Platform 7, but I do not use WildFly.

The deployment and initial setup is easy. It is easier than the previous version.

A qualification for the version would be number seven.

We host our JEE applications in the product. We also host web applications.

The solution is quite stable. We are satisfied with it.

It's hard to find out the root cause of errors.

I have been using the solution for 15 to 20 years.

I rate the tool’s stability an eight out of ten.

The tool is scalable. We have an installation using the JBoss cluster. I think it works pretty fine. Different customers have different numbers of users. The biggest installation has several 1000 users, but not at the same time.

The support is very good. When we have a question, the reaction time is good.

We have used WildFly before. We didn't have any support for that.

The initial setup is quite straightforward if we are a little bit into the tool. The time taken for deployment depends on what we have to do when we do the deployment. Changing the application is quite simple. Usually, we have to change XML files, update scripts on the database, and shut it down to make the changes.

It also depends on where the application runs and if we do the operations for ourselves or the customers. The deployment and maintenance are mostly done by one or two developers and operations personnel.

I am a developer. If I were to start a software project now, I wouldn’t start it on JBoss. I know that there are approaches to split it up and make it more lightweight. Overall, I rate the product a nine out of ten. Occasionally, we ask Red Hat’s support team some questions. The responses are good, and they help us. Overall, I rate the tool a nine out of ten.

We use the product to deploy our applications. This is the default server that we use is DevOps.

It's convenient and barebone. It's easier to troubleshoot and debug if you run into an issue. The logs are in the transcript, and we can easily resolve the issue by troubleshooting. 

A graphic user interface can be added. 

I have been using JBoss for three to four years. 

The solution is highly stable. 

Presently, twenty to thirty people are using the solution. 

The initial setup is very easy. The company provides a lot of documentation to the customers which is very convenient. 

It is an open source solution. 

Our company decided to go with JBoss because it's a default server that comes out of the box with the Dominos application. I rate the overall solution a nine out of ten. 

My job is to analyze which particular application platform is suitable for the type of application. JBoss is one of the solutions I recommend. I'm a senior infrastructure architect.

This current solution is quite stable and the whole frame is quite easy to handle in terms of hosting the application, especially the applications that use only the web containers. We've introduced the clustering solution for our customers, which is a high availability solution and we haven't had any complaints. 

I'd like to see some sort of functional requirement that can convert technical requirements in the JBoss platform. 

I've been using this solution for close to six years. 

The initial setup is relatively simple. Our engineering team implement the solution and it's easy for them to understand. The applications are critical by nature. To date, we've implemented for around 30 different applications and if I try to consolidate the user base, there are somewhere around 200 users.

JBoss is totally subscription-based and it's less costly for us. As a solution architect, I would say licensing is key. The cost involved in implementing the solution is a key factor now that most companies are looking to cut costs. WebSphere is really costly and less flexible. I think the JBoss subscription is quite competitive. Most people understand that the EAP kind of solution will save a lot of money in terms of licensing. 

We've never had any complaints with customers who have implemented this product. 

I rate this product an eight out of 10.