I use it for Java server applications.
Red Hat JBoss Enterprise Application Platform with Support by MidVision
MidVision LimitedExternal reviews
41 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Fast, reliable, and well-established
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
It's good. You choose JBoss when you need a Java server. The benefit is that it's fast, reliable, and well-established.
It was the choice of the customer, and they have no issues so far. It's a very well established product.
What needs improvement?
The price could be improved. Customers don't want to buy the license easily. It's nice that there is Wildfly, which is basically the same as JBoss, just without the price.
For how long have I used the solution?
I have experience with JBoss because we just had it in a project.
What do I think about the stability of the solution?
The stability is good. I would rate it a nine out of ten.
What do I think about the scalability of the solution?
The end users are around 300 for this application. It is used on a daily basis.
Which solution did I use previously and why did I switch?
In general, I would prefer Wildfly. If I want a free version, I would go for WildFly.
And the support is also a factor. If you can do it on your own, you take Wildfly. If you need support, you can take JBoss.
What's my experience with pricing, setup cost, and licensing?
It might be yearly. I am not sure.
Which other solutions did I evaluate?
In the past we evaluated IBM WebSphere, Oracle, and Tomcat. WebSphere system is a pain. Oracle is way overpriced, though. That's my opinion.
JBoss's performance is on par with its competitors.
What other advice do I have?
Overall, I would rate the solution an eight out of ten. If other users need support, I would recommend JBoss. If they don't, they should just go with WildFly.
JBoss is a state-of-the-art Java server with a difficult support package. If you want to do a Java application, JBoss is usually a very good choice.
Offers simplicity along with cost-effectiveness
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using JBoss for eight years. My company has a partnership with Red Hat.
What do I think about the stability of the solution?
Stability-wise, I rate the solution an eight out of ten.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I rate the technical support a seven out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
The product offers a good return on investment.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Reasonably priced and used for application deployments and application servers
What is most valuable?
We use JBoss mainly for application deployments and application servers.
What needs improvement?
JBoss is not as reliable and stable as WebLogic.
For how long have I used the solution?
I have been using JBoss for four years.
What do I think about the stability of the solution?
Once installed and deployed, the solution is stable and works fine in the production environment.
What do I think about the scalability of the solution?
When we need to scale, we install different instances of JBoss. We don't rely on clustering or specific features in JBoss.
Which solution did I use previously and why did I switch?
WebLogic is a more reliable and stable tool than JBoss.
What's my experience with pricing, setup cost, and licensing?
The pricing of JBoss is more reasonable than that of WebLogic.
What other advice do I have?
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.
Enables organizations to connect front-end applications and databases and provides fast and reliable support
What is our primary use case?
JBoss is a middleware product. The customers use it to make connections between front-end applications and databases.
What is most valuable?
Red Hat provides the product and the support. We get good support from the support team. It is one of the benefits.
What needs improvement?
The product could be cheaper. The solution recently increased the prices.
For how long have I used the solution?
I have been working with the product for 6 months to a year.
What do I think about the stability of the solution?
The tool is stable. The customers are buying the product.
What do I think about the scalability of the solution?
The tool is scalable. We can install additional servers. We can extend our cluster horizontally.
How are customer service and support?
The support is fast and reliable. It is very good. If we raise a support ticket, the support team will solve the problem somehow.
How was the initial setup?
The deployment is not that complex. It is easy.
What's my experience with pricing, setup cost, and licensing?
We pay a yearly subscription fee. There are no additional costs associated with the product.
What other advice do I have?
I recommend the tool to others. Overall, I rate the solution an 8 out of 10.
Helps to bring APIs in-house and reduce the dependency on vendors
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
What do I think about the stability of the solution?
I rate the tool's stability a nine out of ten.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I've never needed to directly contact tech support because our internal technical support team handled any issues.
How was the initial setup?
The tool's deployment is easy. Our DevOps team primarily handled the deployment process. A team consisting of 40-50 members maintains it.
What was our ROI?
The tool is worth its money.
What other advice do I have?
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.
JBoss Enterprise Application Platform
What do you like best about the product?
Red Hat JBoss uses standard software and hardware. It is relatively easy to implement and understand once you decide that you need to use the software.
What do you dislike about the product?
It is not generally known what the purpose of the software is and what platforms it is available on.
What problems is the product solving and how is that benefiting you?
The software and hardware is being used for a business application.
First Impressions with Red Hat JBoss: A Newcomer's Insight
What do you like best about the product?
I appreciate the robust features and seamless integration capabilities of Red Hat JBoss EAP, ensuring a reliable foundation for enterprise applications.
What do you dislike about the product?
While Red Hat JBoss EAP offers strong functionalities, there might be a learning curve for beginners. Improved documentation could make the onboarding process smoother.
What problems is the product solving and how is that benefiting you?
Red Hat JBoss EAP addresses challenges in deploying and managing enterprise Java applications, providing a scalable and reliable platform. This benefits organizations by ensuring better performance, enhanced security, and simplified application development and deployment processes. The platform's robust features contribute to a more efficient and streamlined application environment.
Efficient, Scalable and adaptable
What do you like best about the product?
JBoss EAP can set up several web applications at once and is simple to install and configure and easy deployment saves time. It has smart load balancing based on HTTPD and can high availability clustering. It supports hybrid that is cloud and on prem server which facilitates integration.
What do you dislike about the product?
JBoss's limitations when it comes to processing applications.xml files, we had to combine linux bash commands with jboss-cli in order to automate some application.
What problems is the product solving and how is that benefiting you?
We primarly employ JBoss EAP to deploy Java web applications across several company websites. The site administration team and Java developers use it most often when it comes to heavier deployments.
Reliable Excellence: Red Hat JBoss EAP Paves the Way for Seamless Airport Check System Operations
What do you like best about the product?
Red Hat JBoss EAP has been the backbone of our mission-critical Airport Check System, and its performance has been nothing short of exceptional. The platform's robust architecture and seamless scalability have ensured uninterrupted service for our vital operations. Throughout its deployment, we've experienced zero issues, showcasing the platform's reliability and resilience in handling the demanding requirements of our AI-powered systems. JBoss EAP's stability and efficiency have played a crucial role in maintaining the smooth functioning of our airport operations, earning our utmost confidence and satisfaction.
What do you dislike about the product?
Nothing significant issues we have faced in past 7 years because of JBoss.
What problems is the product solving and how is that benefiting you?
Hosting the robust Java-based application with easy administration and the most amazing logging features.
Good for running webshops and online business
What is our primary use case?
The use cases include online webshops and any organization doing online business can use JBoss.
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.
showing 11 - 20