What needs improvement with JBoss?


Please share with the community what you think needs improvement with JBoss.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
22 Answers

author avatar
Top 10Reseller

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.

author avatar
Top 5LeaderboardReal User

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.

Find out what your peers are saying about Red Hat, Oracle, IBM and others in Application Server. Updated: September 2021.
535,919 professionals have used our research since 2012.