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.
Enterprise Archiect/ IBM & Redhat Business Development at Cancom
Real User
Top 5
2023-12-12T13:54:00Z
Dec 12, 2023
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.
One engineer is required for the deployment and maintenance of JBoss. I would recommend users to go ahead and use JBoss. Overall, I rate JBoss a five out of ten.
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.
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.
Application Server Manager at Centro Nacional de Registros
Real User
Top 10
2022-08-05T14:22:03Z
Aug 5, 2022
First: You must start with Standard Subscription.
It will let you get patches and support at best price.
With 5 years running JBoss, I have never needed open a mayor o critical case support.
Second: Try to implement the domain controller with HA.
Standalone mode is easier and perfect for development and small solutions. But, domain crontroller give you scalebility with central console management and High Avilibility
I rate JBoss seven out of 10. I would recommend Tomcat for a small-scale use case. It's easy to maintain and deploy, and the UA interface is simple. JBoss is more appropriate for large industries. Though it is complex to maintain, JBoss is well balanced and can handle larger loads.
I don't remember the version we're using, however, it'll be the latest version at that time of implementation. These are on an in-house data center. It's pretty easy to implement from the Java perspective, however, equally challenging to integrate with other applications or different databases. I'd rate the solution nine out of ten.
Application Server Manager at Centro Nacional de Registros
Real User
Top 10
2021-12-21T11:47:00Z
Dec 21, 2021
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.
Head of Department at a transportation company with 10,001+ employees
Real User
2021-04-08T11:06:33Z
Apr 8, 2021
My advice is that for anybody who is searching for a lightweight application or web server, JBoss is one of the options that I recommend. We plan to continue using it. I would rate this solution a seven out of ten.
Information Technology Consultant at a computer software company with 11-50 employees
Reseller
2021-03-26T20:56:49Z
Mar 26, 2021
Its recommendation depends on the vision of the organization. We need to have that understanding first before we provide them some sort of solution. It will depend on what they already have in place or what they're planning to do. Customers are moving to the cloud, and there are other alternatives out there, but of course, it will depend on understanding the journey of the customer. I would rate JBoss an eight out of ten, just for how common it is to use Java as a language.
We're just customers. We are currently migrating an application that was developed, on JBoss, and we are taking it to the Cloud. The project was started on JBoss 6.2, however, now that we are mounting it in the Cloud, we're using JBoss EAP 7.3. The client doesn't want to pay more rights to RedHat. Now we're moving JBoss to WildFly, which is really easy. It's just to avoid the licenses. The deployment version is on-premises. The productive version is still on AWS on-premises, on some virtual machines that the company paid for. However, when it comes to the cloud, we are installing it in Google Cloud. We are moving it. We have these deployments in parallel. I could recommend this solution as I have seen that it's stable. There are some things that are still done in an old-fashioned way, however, it's still stable and you can find the connotation for that. You can have the option to use it in the cloud. We are using containers already for tables in the cloud. My advice would be simply to have it really clear why you want to use it. Alternatively, if you are going to have a really heavy application where you need everything together, of course, JBoss is a good option. I would rate the solution at a nine out of ten.
Red Hat JBoss Enterprise Application Platform (EAP), a market-leading, fully certified Java EE platform, gives you a single platform to quickly develop and deploy applications. Use traditional Red Hat JBoss EAP to gain business agility with your existing applications and reduce the costs of proprietary platforms.
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.
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.
I would recommend JBoss to others. Overall, I would rate it as a nine out of ten.
One engineer is required for the deployment and maintenance of JBoss. I would recommend users to go ahead and use JBoss. Overall, I rate JBoss a five out of ten.
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 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.
I would rate the solution a ten out of ten. I would recommend this solution to others.
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.
I rate the solution a seven out of ten.
First:
You must start with Standard Subscription.
It will let you get patches and support at best price.
With 5 years running JBoss, I have never needed open a mayor o critical case support.
Second:
Try to implement the domain controller with HA.
Standalone mode is easier and perfect for development and small solutions. But, domain crontroller give you scalebility with central console management and High Avilibility
I rate JBoss seven out of 10. I would recommend Tomcat for a small-scale use case. It's easy to maintain and deploy, and the UA interface is simple. JBoss is more appropriate for large industries. Though it is complex to maintain, JBoss is well balanced and can handle larger loads.
I don't remember the version we're using, however, it'll be the latest version at that time of implementation. These are on an in-house data center. It's pretty easy to implement from the Java perspective, however, equally challenging to integrate with other applications or different databases. I'd rate the solution nine out of ten.
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.
I would recommend this solution to others. I rate JBoss an eight out of ten.
My advice is that for anybody who is searching for a lightweight application or web server, JBoss is one of the options that I recommend. We plan to continue using it. I would rate this solution a seven out of ten.
Its recommendation depends on the vision of the organization. We need to have that understanding first before we provide them some sort of solution. It will depend on what they already have in place or what they're planning to do. Customers are moving to the cloud, and there are other alternatives out there, but of course, it will depend on understanding the journey of the customer. I would rate JBoss an eight out of ten, just for how common it is to use Java as a language.
We're just customers. We are currently migrating an application that was developed, on JBoss, and we are taking it to the Cloud. The project was started on JBoss 6.2, however, now that we are mounting it in the Cloud, we're using JBoss EAP 7.3. The client doesn't want to pay more rights to RedHat. Now we're moving JBoss to WildFly, which is really easy. It's just to avoid the licenses. The deployment version is on-premises. The productive version is still on AWS on-premises, on some virtual machines that the company paid for. However, when it comes to the cloud, we are installing it in Google Cloud. We are moving it. We have these deployments in parallel. I could recommend this solution as I have seen that it's stable. There are some things that are still done in an old-fashioned way, however, it's still stable and you can find the connotation for that. You can have the option to use it in the cloud. We are using containers already for tables in the cloud. My advice would be simply to have it really clear why you want to use it. Alternatively, if you are going to have a really heavy application where you need everything together, of course, JBoss is a good option. I would rate the solution at a nine out of ten.