JBoss Reviews

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. 

We used JBoss as our application server on the recommendation of the lead developer. JBoss's compatibility with Java EE, modularity, and support for clustering met the diverse needs of our applications. The management console and developer-friendly features simplify configuration and maintenance. JBoss provided a reliable and efficient runtime environment for our Java-based applications.

The most valuable thing about JBoss is how easy it is to install and manage it on-premise, making the process simple. The application setup is neat and easy to follow. Although we used to manually check log files, integrating a monitoring tool later on improved efficiency. Overall, JBoss is user-friendly and adapts well to changing monitoring requirements.

The version of JBoss we used, which was quite old (version 4), lacked a user-friendly web console or portal for easy server management. It would be beneficial to have a console for configuration to simplify the administrator's tasks. In terms of monitoring, the old version was somewhat limited in flexibility, lacking the ability to easily adjust configurations.

I used JBoss for a previous project at my company.

JBoss stability depends on the administrator's familiarity with adjusting Java's memory settings. If you're not familiar with it, the application might not be very stable. But once you understand how to allocate the necessary memory, JBoss runs reliably.

JBoss is scalable. It supports configuring both load-balanced and clustered architectures, enabling scalability for the applications it hosts. Approximately 5,000 people used it at our company.

It takes less than an hour to deploy JBoss. Deploying it was a bit manual. We downloaded JAR files from the JBoss community edition website, ran a script on Linux, and manually copied and configured the Java application using the provided templates. It worked, but the process could have been smoother, especially compared to modern containerized deployment methods. Three lead engineers were responsible for setting up and maintaining the application servers.

We didn't pay for a license because we used the JBoss community edition, which is free.

I would recommend JBoss to others. Overall, I would rate it as a nine 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.

We use JBoss mainly for application deployments and application servers.

JBoss is not as reliable and stable as WebLogic.

I have been using JBoss for four years.

Once installed and deployed, the solution is stable and works fine in the production environment.

When we need to scale, we install different instances of JBoss. We don't rely on clustering or specific features in JBoss.

WebLogic is a more reliable and stable tool than JBoss.

The pricing of JBoss is more reasonable than that of WebLogic.

Customers use JBoss instead of WebLogic. Although WebLogic is more feature-rich, its licensing is very high compared to JBoss. I am satisfied with JBoss's management and monitoring capabilities. I would recommend JBoss to other users.

Overall, I rate the solution 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.

For our application to deploy, we used to set up different platforms. We are certifying JBoss support as well for the deployment.

JBoss's configuration is straightforward and easy. It is easy to edit one standalone dot XML file with all the configurations.

The solution sometimes crashed and had some compatibility issues with the DevOps JAR file.

JBoss's next release should include a one-click solution for clustering or straightforward installation.

I have been using JBoss for three to four years.

I rate JBoss a seven out of ten for stability.

JBoss is a scalable product and 100 people were using it in our company.

The initial setup of JBoss is easy. However, the clustering part was a little bit complex.

I recommend people to use JBoss because it is easy to set up and install.

Overall, I rate JBoss an eight to nine out of ten.

The use cases include online webshops and any organization doing online business can use JBoss.

It is fast. You can quickly migrate applications to JBoss and create things like webshops.

I have experience with this product. I've worked with JBoss before but without Red Hat. But now, it comes with Red Hat's JBoss.

I would rate the stability a ten out of ten. 

I would rate the scalability a ten out of ten. It is very scalable. 

We have contacted the technical support team now and then. 

The initial setup is straightforward and quick. You can deploy it standalone or with the Red Hat runtime, which bundles JBoss.

Licensing costs are always debatable. While there are free, open-source alternatives like Java EE and WildFly, they lack the support and reliability of a paid, certified product like JBoss. 

With JBoss, you get the peace of mind of premium support and avoid potential issues in production environments. 

So, for production environments, I recommend certified products with support. For testing, free, open-source options are fine.

Overall, I would rate the solution a ten out of ten.