The use cases include online webshops and any organization doing online business can use JBoss.
Red Hat JBoss Enterprise Application Platform with Support by MidVision
MidVision Limited | 8.0.7 on RHEL9Linux/Unix, Red Hat Enterprise Linux 9.6 - 64-bit Amazon Machine Image (AMI)
Reviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
JBoss Enterprise Application Platform
First Impressions with Red Hat JBoss: A Newcomer's Insight
Efficient, Scalable and adaptable
Reliable Excellence: Red Hat JBoss EAP Paves the Way for Seamless Airport Check System Operations
Good for running webshops and online business
What is our primary use case?
What is most valuable?
It is fast. You can quickly migrate applications to JBoss and create things like webshops.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
I would rate the stability a ten out of ten.
What do I think about the scalability of the solution?
I would rate the scalability a ten out of ten. It is very scalable.
How are customer service and support?
We have contacted the technical support team now and then.
How was the initial setup?
The initial setup is straightforward and quick. You can deploy it standalone or with the Red Hat runtime, which bundles JBoss.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
User-friendly and adapts well to changing monitoring requirements
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I used JBoss for a previous project at my company.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
We didn't pay for a license because we used the JBoss community edition, which is free.
What other advice do I have?
I would recommend JBoss to others. Overall, I would rate it as a nine out of ten.
Which deployment model are you using for this solution?
The solution's pricing could be improved, but its support is very good for repairing components
What is our primary use case?
We provide the very basic JBoss setup for the implementation and the setup.
What is most valuable?
The solution's support is very good for repairing components. We just need to raise a case, and the support team will reply.
What needs improvement?
The solution's pricing could be improved because it is not cheap.
For how long have I used the solution?
I have been working with JBoss for a couple of years.
What do I think about the stability of the solution?
I rate JBoss an eight out of ten for stability.
What do I think about the scalability of the solution?
Two to three of our customers are using JBoss.
I rate JBoss an eight out of ten for scalability.
How was the initial setup?
The initial setup could be simple or very complex, depending on the solution.
What about the implementation team?
It takes weeks to deploy JBoss. The solution's deployment includes downloading the installer and then deploying the server.
What's my experience with pricing, setup cost, and licensing?
JBoss is an expensive solution. Customers need to pay for a yearly license for JBoss.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Open-source solution and highly scalable
What is our primary use case?
Our primary use case is for web applications.
What is most valuable?
I like that it's open-source and free. All the features are very good.
What needs improvement?
The only thing I would change is the logging. The login logs are not very good. The login process could be improved.
For how long have I used the solution?
I have been using JBoss for about ten years. We use version JBoss EAP 6.
What do I think about the stability of the solution?
The stability is great.
What do I think about the scalability of the solution?
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.
How are customer service and support?
The customer service and support are great. They are very responsive and helpful.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is not complex. It took us about a week to set up.
What about the implementation team?
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.
What's my experience with pricing, setup cost, and licensing?
JBoss is open-source and free. There is no licensing cost. The solution is free to use.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Robust solution with good scalability
What is our primary use case?
We use the solution for the installation of the hardware and microservices.
What is most valuable?
The solution is robust and provides good support.
What needs improvement?
The solution's documentation could be better.
For how long have I used the solution?
We have been using the solution for around sixteen years.
What do I think about the stability of the solution?
I rate the solution's stability a seven or eight. It needs improvement as we need to do the troubleshooting for some instances.
What do I think about the scalability of the solution?
It is a scalable solution. It supports both vertical and horizontal scaling. I rate its scalability an eight or nine.
How are customer service and support?
The solution's technical support is good. Although, it depends on the type of support contract one has purchased.
How was the initial setup?
The solution's setup process is straightforward for me as I have prior experience using it. I rate the process an eight. It takes a day to complete a basic setup.
What's my experience with pricing, setup cost, and licensing?
It is an open-source solution.
What other advice do I have?
I rate the solution an eight. There are better solutions available, like WebLogic, with high scalability.
Straightforward configuration and easy to install
What is our primary use case?
For our application to deploy, we used to set up different platforms. We are certifying JBoss support as well for the deployment.
What is most valuable?
JBoss's configuration is straightforward and easy. It is easy to edit one standalone dot XML file with all the configurations.
What needs improvement?
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.
For how long have I used the solution?
I have been using JBoss for three to four years.
What do I think about the stability of the solution?
I rate JBoss a seven out of ten for stability.
What do I think about the scalability of the solution?
JBoss is a scalable product and 100 people were using it in our company.
How was the initial setup?
The initial setup of JBoss is easy. However, the clustering part was a little bit complex.
What other advice do I have?
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.