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.
Red Hat JBoss Enterprise Application Platform with Support by MidVision
MidVision LimitedReviews 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.
Helps to bring APIs in-house and reduce the dependency on vendors
What is our primary use case?
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
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?
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.
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.