Red Hat JBoss Enterprise Application Platform

I use JBoss Enterprise Application Platform  for all our web applications, both internal and external.

JBoss Enterprise Application Platform  works very well. It is very robust. It offers a number of good integration options and many facilities that are advantageous compared to Tomcat .

In my experience, it is more beneficial to embed all that into Kubernetes  today. This approach makes it easier to develop, deploy, and administer applications.

I have worked with JBoss Enterprise Application Platform for many, many years.

To me, the stability issues depend on how the applications are developed on JBoss Enterprise Application Platform. The main point often is how well applications in Java are developed.

I have found no problem with scalability. It can scale up as our business grows.

I have not contacted Red Hat directly, as it is handled by other teams.

Neutral

The initial setup requires expertise. In my use, as part of our already built solution to the cloud, it is embedded and takes just a few minutes to have a JBoss  server running.

Overall, I would rate this tool eight out of ten.

Public Cloud

Other

What do you like best about the product?

Jboss is one of the best application servers available currently and cost effective and secure for all java based applications. User interface is very user friendly and integration with web servers are very easy. Also we can manage almost all tasks from the jboss console.

What do you dislike about the product?

Nothing as such. Sometimes if a JVM heap is high the management console becomes unstable.

What problems is the product solving and how is that benefiting you?

This is providing a secure platform for java based applications deployment.

What do you like best about the product?

One of the best application servers available in the market. Interface is very easy to explore having all related functionality written in all features. One can manage almost all configuration and deployment from the management console. Also applying patch is easy from console itself. Red Hat vendor support is really good. Integration with web server is also easy. Managing SSL configuration also pretty simple.

What do you dislike about the product?

Nothing as such but it would be great if host can be restarted or reconnected from management console itself without getting into CLI and perform restart.

What problems is the product solving and how is that benefiting you?

It is helping us on deploying and hosting our complex applications. It also has features to integrate with external APIs in the domain.xml itself so it's pretty easy manage an application in jboss.

We use JBoss primarily for public institutions involved in customs. Our environment does not use cutting-edge technologies; instead, we continue to utilize JBoss due to our clients' preference for stable, established solutions.

JBoss has been adequate for our needs because our use cases do not demand high performance or advanced capabilities. It has allowed us to maintain a stable service for clients hesitant to adopt newer technologies.

The most valuable aspect of JBoss EAP is its support for clustering and load balancing, which is essential for our applications that serve multiple users simultaneously. This feature helps us manage traffic effectively across different nodes.

Improvement is needed in the synchronization between cluster nodes, especially under network strain. Enhanced stability in cluster management and better error handling during unexpected network changes would be beneficial in future releases.

I started using JBoss EAP in 2016 and have continuously used it to deliver solutions to our clients in the customs area.

I rate it a seven out of ten. Stability is generally good under normal conditions but can be compromised by network issues at the client's end.

JBoss scales adequately for our needs, handling multiple institutions without significant degradation in performance.

I have had limited interaction with JBoss's technical support since we handle most issues internally.

Positive

We previously utilized IBM's products, which were heavier and less agile compared to JBoss. The switch was motivated by JBoss's lightweight nature and ease of deployment.

The initial setup of JBoss was straightforward due to its compatibility with our existing infrastructure.

Implementation was managed in-house, leveraging our technical team's expertise with the platform.

The return on investment has been positive, primarily due to the low overhead and maintenance costs associated with using a solution that meets our clients' conservative upgrade strategies.

While I am not directly involved with the financial aspects, JBoss is known for its reasonable subscription pricing. Potential users should consider whether the cost aligns with their budget and requirements.

Our decision to use JBoss was based primarily on its fit with our existing environment rather than a broad evaluation of alternatives.

JBoss is a commendable choice for organizations that do not require the latest technology but need a reliable and scalable solution. However, be prepared for potential issues in complex network environments.

What do you like best about the product?

Red Hat JBoss uses standard software and hardware. It is relatively easy to implement and understand once you decide that you need to use the software.

What do you dislike about the product?

It is not generally known what the purpose of the software is and what platforms it is available on.

What problems is the product solving and how is that benefiting you?

The software and hardware is being used for a business application.