Red Hat JBoss Enterprise Application Platform (EAP) Reviews

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.

The tool's documentation could be improved to explain its usage and functionalities clearly. Having accessible documentation would save time for leaders like me when juniors seek information about it. The documentation should be self-explanatory and guide users on how to utilize the tool. 

I rate the tool's stability a nine out of ten. 

I can't speak definitively regarding scalability features as I recently switched companies. However, I recommended implementing the Spring framework and JBoss in my previous role. Whenever I move to a new company, I advocate using these solutions. I rate its scalability a seven to eight out of ten. My company has around 150 million active users. 

I've never needed to directly contact tech support because our internal technical support team handled any issues.

The tool's deployment is easy. Our DevOps team primarily handled the deployment process. A team consisting of 40-50 members maintains it. 

The tool is worth its money. 

The tool's open-source nature influenced my decision to use it because it was cost-effective. Our business team handed it over to us, and they were aligned with using it. I recommend it because it offers multiple application routing data handling capabilities. It helped convert the data. 

I rate the overall solution a nine out of ten. If someone wants to start using it, I would tell them that there isn't much competition in the market because the tool is unique and has been established for a long time. It has set the benchmark, and other brands are striving to catch up with your range of services. This is something to be proud of. 

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.

There is not much ability inside of the solution. The world is going beyond different micro and data-type things like Microsoft Office, so we are not seeing much ability within the solution. 

I have been using the solution for 15 years. 

The stability is rated an eight out of ten. 

The scalability is rated an eight out of ten. 

Technical support does not provide good responses to tickets so is rated a five out of ten.

Neutral

The setup is pretty easy so is rated an eight out of ten. 

The solution is cost-efficient compared to other products. Pricing is rated an eight out of ten. 

I rate the solution a seven out of ten. 

Our primary use case is for web applications.

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

The only thing I would change is the logging. The login logs are not very good. The login process could be improved.

I have been using JBoss for about ten years. We use version JBoss EAP 6.

The stability is great.

It is a highly scalable solution. We have about 500 to 1,000 users using the solution. It's very scalable, so we can easily add more users as needed. The users are mostly managers and route managers.

The customer service and support are great. They are very responsive and helpful.

Positive

The initial setup is not complex. It took us about a week to set up.

We did it in-house. We didn't need consultation. The deployment process is simple. We just have to load the application archive. It will deploy to the server, and then it will run. That's it. It's not a difficult task.

We do it in-house, so we don't need any third-party help. Only one person is needed to deploy and maintain the solution. There are no managers or developers required.

JBoss is open-source and free. There is no licensing cost. The solution is free to use.

I would definitely recommend the solution to other people. It's a great product.

I would recommend that they give it a try. It's a great solution, and it's free to use. Overall, I would rate the solution an eight out of ten. 

I use the solution in my company since we have developed an application that runs on the application server, JBoss, and another application server, such as Oracle WebLogic Server or WebSphere. In my company, we developed an application for the bank, and we deployed it under JBoss, WebSphere, or Oracle WebLogic Server.

The most valuable feature of the solution for me stems from the fact that our company can develop applications on JBoss, and we didn't see anything like it compared to WebLogic and WebSphere. The facility to install and handle JBoss is much lighter than the other application servers.

My company had faced some issues where our questions were not answered, and we did not receive proper solutions the way we wanted. The technical support of the product can be improved. Response time for support could be a bit better.

The price of the product is an area of concern where improvements are required. The product could be made cheaper.

I have been using JBoss for eight years. My company has a partnership with Red Hat.

Stability-wise, I rate the solution an eight out of ten.

My company did not face any issues related to scalability. Scalability-wise, I rate the solution a seven out of ten.

My company works with banks of both small and big sizes.

I rate the technical support a seven out of ten.

Neutral

In comparison with the other products I have used in the past, I like JBoss's simplicity, lightness, and cost. Considering what my company used to use both solutions for, JBoss was better than WebLogic.

The product's initial setup phase is easy.

For the product's deployment and maintenance, our company has a system engineer who maintains both our instances associated with JBoss and supports the bank engineers.

The product offers a good return on investment.

I rate the product price as eight on a scale, where one means it is a very cheap solution, and ten points mean that it is a very expensive tool.

In terms of how JBoss supports enterprise Java standards and positively impacts our company's project, I can say that we use it, and we didn't have any issues. In our company, we have been able to do a posting of the application on the other application servers.

My company has not faced issues with the integration of the product with other software tools or infrastructures.

The product fits our company's requirements.

I recommend the product to others.

I rate the tool an eight out of ten.

JBoss is a middleware product. The customers use it to make connections between front-end applications and databases.

Red Hat provides the product and the support. We get good support from the support team. It is one of the benefits.

The product could be cheaper. The solution recently increased the prices.

I have been working with the product for 6 months to a year.

The tool is stable. The customers are buying the product.

The tool is scalable. We can install additional servers. We can extend our cluster horizontally.

The support is fast and reliable. It is very good. If we raise a support ticket, the support team will solve the problem somehow.

The deployment is not that complex. It is easy.

We pay a yearly subscription fee. There are no additional costs associated with the product.

I recommend the tool to others. Overall, I rate the solution an 8 out of 10.

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.

The stability of the solution could improve with Microsoft Windows.

I have been using JBoss for approximately 10 years.

The stability of JBoss. However, if we are using Linux it is more stable than if we are using Microsoft Windows.

JBoss is capable of scaling, and it supports clustering for scalability. However, if clustering is not supported, we would need to use a load balancer to achieve scalability.

We have our own team that handles the support. I have not contacted the vendor for support.

We are using the web application server from IBM.

The setup of JBoss was straightforward.

We have a Red Hat professional partner who helps us with the implementation of the solution.

The number of people needed for the implementation depends on the build. If the setup is basic then one person can handle it.

The return on investment from JBoss depends on the specific solutions being used. In our case, based on the solutions we are running, I don't believe we are getting a good ROI. If we were running a large-scale solution such as a channel, then it would make sense. However, if we are using a small free solution, such as a back-office solution, and investing in expensive licenses, it may not be very cost-effective.

Despite the price increase after being acquired by IBM, JBoss still maintains its competitiveness. The package provided is more geared towards cloud-based deployments, whereas our setup is more traditional, which makes it slightly more expensive for us. As most vendors are transitioning towards cloud-centric solutions, companies like ours need to adapt accordingly.

The license from JBoss. There is a CAPX cost and an annual cost.

All the solutions we use are on-premise because we are a bank institution. However, we use some SaaS solutions but they are not connected to the on-premise systems.

I would recommend JBoss to others.

I rate JBoss a nine out of ten.

We use JBoss exclusively for API integration and do not use it for other purposes. Our focus is solely on providing services and configuring ACLs.

Certain works are being done very well with JBoss due to its peer configuration. The various styles of services offered by JBoss are very useful for our company and other companies as it becomes difficult for businesses to afford too many services running on different computers. In short, JBoss is a good product. We use several instances, such as Java instances, and also install numerous services within the solution.

Logging-related issues in JBoss require improvement. Also, another problem in the solution is that once the developer finishes coding, minor changes are often required when deploying Red Hat Fuse. Though the developer already knows these changes, there may be some dependency problems and the need to install JAAS. The other issue in JBoss is related to instances being stuck.

I have been working with the solution for four years.

For our company, JBoss is a stable tool. However, I won't be able to speak for other people.

JBoss is a scalable tool.

Regarding the setup of JBoss, it is a standalone setup, which is straightforward. So, we are not using a domain setup. The solution's deployment was done four years ago. Additionally, the solution's setup is done on Openshift, which is a cloud-based platform.

Since the solution is freeware, our customers don't need to pay any licensing fees. The only element that requires payment is RHEL.

We use Git as a version controller, with the help of which the developers do coding and then commit their changes for a game. We have been using Git for four years.

I recommend JBoss to people who want to start using the solution. It is not a complicated tool to use. We are deploying different services over different instances. So, we reduce the cost over the one server, which we use to provide more than 600 services. Overall, I rate this solution a ten out of ten.

The high availability is great. Implementing it is very easy. Sometimes we only have to copy the installation or the house installation and change some parameters inside the host. After that, we run the instance in the console manager, and from the console manager, we can create new servers. It's very easy to implement a high availability installation. For me, that is the most important feature. 

The solution is stable. 

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.

For the last three or four years I have been working as an Application Server Administrator using JBoss.

The stability of the solution has been good. There are no bugs or glitches and it doesn't crash or freeze. It's very reliable and the performance is good. 

The scalability is not always perfect, however, it's very good. For example, maybe sometimes we only have two instances as we don't know how to balance three instances. We have to know how it's working the load balancer of a session data when we lose one instance or one server, for example. Maybe we need to learn more about that. 

I'd like some better documentation to find information about how it's working the load balancer in the high availability. We know that the load balancer is using the name of each instance and, for example, if we are using numbers on the line of each server, we know that from server one that the configuration is supposed to be to server two, and from the server two to server three, or something like that.

With JBoss right now we don't know. Maybe this is due to the fact that we only have two servers. With these two servers, it's enough for working and giving very good services. While we don't need to know that right now, maybe in the future we have to learn more or will have to search the documentation about how we have to configure our web server balancer or implement that load balancer with Jboss.

Before the new JBoss, we were using WebLogic, however, we changed off of that to Jboss. Recently, for the cost of paying one support for WebLogic, it's the same price to get a new subscription to JBoss. We were using the standard version for WebLogic and that version doesn't give us high availability in the future. That's why we decided to move on to Jboss. It's using a standard subscription and we get high availability with JBoss for the same price as we would pay the support for the WebLogic Standard Edition.

The implementation process is very easy.

For deployment, we only need three people. You don't require a big team.

If one person is used to deploy in the morning and then the other person is deploying in the afternoon. The next person is for learning from these two persons, therefore, basically, it's three people you need, however, maybe you could do it with two.

We pay to license on a yearly basis.

We were spending something like $12,000 in the first year. This year it's something close to $16,000.

We don't have additional fees or anything like that. It's a standard subscription.

We are customers. We only consume this product. We don't distribute it or anything like that.

In the last three years, I've been implementing the JBoss application solution. I try to create a high availability implementation, however, sometimes I try to get all the stocks working. We have some dependence on the developers as sometimes they have to implement some special implementation in each class. Basically, we have a full tolerance and in a special application, we have the full high availability.

I use the on-premise deployment due to the fact that I'm working for a government institution. We have some policies for on-premise user data. If we get a new change in our policies, we are considering moving onto the cloud. That said, for us, the cloud is not cheap as we have a lot of data. Sometimes we have maps and a lot of images and that is very expensive due to the fact that on the cloud you have to pay for each legalized transfer. Sometime soon maybe we will implement a small project. We are not thinking about moving all the infrastructure.

We have something like 1,000 users, however, the most important system has something like 500 users. We have two principal systems. One is for the clients and the other one is for internal use. We have something like 500 users on each server.

I'd rate the solution at an eight out of ten.