JBoss Reviews

We are currently using Ansible for Jira installations and all the management tasks. We perform some tasks manually, however, Ansible helps in automating some of these processes.

I find JBoss to be lightweight and easier to manage compared to WebSphere. It allows for simple modification of applications and provides better clustering capabilities. The setup was straightforward and suitable for enterprise-level needs.

Our product is agnostic, so we have been using JBoss as our default app server. We have been using it for over ten years.

JBoss is more flexible and keeps up with modern technologies, supporting newer versions of different libraries. This is crucial as the lifecycle of these technologies is short, and staying up to date is essential to avoid issues.

In my previous company, we relied on third-party APIs from a vendor. Recently, we were tasked with bringing those APIs in-house, reducing dependence on external vendors. We employed a JBoss server to facilitate the transition of these APIs into our existing system.

The tool's most beneficial feature is its scalability. People with limited technical knowledge can quickly grasp its functions with a brief introduction. The tool's ease of use makes it a plug-and-play solution, reducing the effort required to train users on its usage.

We integrated one of the largest payment service providers using JBoss. Specifically, we integrated Visa, a well-known credit and debit card provider, into our system using JBoss. As the project's lead software engineer, I executed this integration.

I use it for Java server applications.

I work on an output management system. There are products that use JBoss as the Java server. It's a product from another vendor called the 'M' series. They use JBoss as the server behind it.

Our company uses the solution for enterprise clients in the banking and finance industries. 

We use different versions of the open source solution depending on client needs. 

The solution has flexibility and stability.

Our primary use case is for web applications.

I like that it's open-source and free. All the features are very good.

The product is basically middleware. What we have is several applications running on JBoss. Basically, it is very old and there we have those services exposed. Our target is to move them to ERPC, or something more modern, like REST or ESPC, or a combination of both.

What we currently have here, still, is SOAP services, which is a very old middleware. They also are using it for scheduling some items such as some recurrent procedures. They have a queue manager as well.

I've only been with this client in the last six months, however, the middleware has been the backbone for them for several years. The organization depends on it. The business depends on it.

I use JBoss for our websites and multiple products.

The greatest benefit of JBoss is that it was procured by IBM, thereby offering exceptional support for our banking operations.