IT Central Station is now PeerSpot: Here's why

JBoss Room for Improvement

Erick  Garcia Ramirez - PeerSpot reviewer
Software Engineer at Globant

JBoss is too much for what we need. When it was developed, it made sense. I liked having all of these services and all of these applications mounted on vehicles due to the capability. We could have several clusters in one JBoss instance. Nowadays, that solution is kind of too much maybe. We're not using very distinctive capabilities.

If the client decides to keep on JBoss instead of migrating to services, to the different architecture, the next steps would be to take more advantage of the new features, changing the code to a Java 11 style. Of course, they need to modernize the services, and consider migrating to new stuff that is available already for items like REST. Or even the use of stuff like GraphQL.

In general, the support of the ERPC would be really good due to the fact that, so far, I have not seen it. I have not even tried GraphQL, however, having any of these new technologies for exposing services would be really, really good for JBoss, That's what is moving forward in the industry.

View full review »
Erick-Guevara - PeerSpot reviewer
Application Server Manager at Centro Nacional de Registros

Sometimes the console has a glitch. For example, we might send some commands to stop the servers and we get some logs or some errors from the console. After some minutes the services stop yet the console doesn't refresh the status. 

Sometimes I miss the JDBC resources full administration from GlassFish. In GlassFish, you define the pool and if you have three or more domains you can deploy to each domain. However, in JBoss, you have to define each pool in every configuration. Sometimes you have to do extra work to define this JDBC force and that is something that sometimes is very annoying.

View full review »
NS
General Manager Sales at Taashee

We haven't come across any missing features. 

The initial setup is a bit complex. 

I'd like the product to move more towards the cloud.

The frequent updates, and the life cycle, should be a little longer. They keep on changing versions and versions should have a longer life.

Even if the client buys an extended life cycle, they should support the customers who are loyal customers and extend all their possible support to the client when a customer is buying a subscription as well as extended life cycle support. The OEM should want to give additional extended support to the customer because.

View full review »
Buyer's Guide
JBoss
July 2022
Learn what your peers think about JBoss. Get advice and tips from experienced pros sharing their opinions. Updated: July 2022.
620,068 professionals have used our research since 2012.
Harikrishnan  Ramamoorthy - PeerSpot reviewer
Technical Lead at Netlink Software Group America Inc

The documentation could be better. When we have questions, we need to check multiple websites. There isn't one place listing a set of common problems and how to fix them. 

View full review »
BT
Head of Department at a transportation company with 10,001+ employees

The support should be bundled with the Red Hat OS support because as it is now, these are two separate costs. Having the support combined with Red Hat support would be an improvement.

View full review »
GM
Information Technology Consultant at a computer software company with 11-50 employees

It can have automation features. Everybody is focused right now on automation. In terms of saving cost, automation is always the first thing that comes to light.

View full review »
KC
Individual Contributor at a comms service provider with 10,001+ employees

The solution could improve by providing more integration.

View full review »
Buyer's Guide
JBoss
July 2022
Learn what your peers think about JBoss. Get advice and tips from experienced pros sharing their opinions. Updated: July 2022.
620,068 professionals have used our research since 2012.