Rapid deployments have streamlined containerized web apps but support response still needs improvement
What is our primary use case?
The main use case for Red Hat JBoss Enterprise Application Platform (EAP) is to deploy web applications, WAR files and JAR files of our developed app, and also to use Red Hat JBoss orchestrator for containerization and everything.
We primarily use Red Hat JBoss Enterprise Application Platform (EAP) for various environments such as dev, SIT, and prod, and we have been using it exclusively for SAP-based front-end while the back-end is Spring Boot, and we were using JBoss particularly for deploying these servers, with a very easy way to deploy the JAR files mainly.
What is most valuable?
The best features Red Hat JBoss Enterprise Application Platform (EAP) offers are its integration into AWS services, which is very helpful in containerization and application of Kubernetes specifically, and its user interface is very easy to use; we can deploy WAR files within stipulated time and also schedule deployments at a particular time, and it is easy to run the pipelines and integrate it with Jenkins.
The most valuable feature for my team is containerization and Jenkins integration because Jenkins integration helps us eradicate code smells and build pipeline reports, and it also supports continuous CI/CD pipelining, while this orchestration aids in a microservice architecture where we will be using different types for it.
Red Hat JBoss Enterprise Application Platform (EAP) has positively impacted my organization by helping in quickly making web Spring Boot applications and Java-based applications, and it is very easy to adapt and learn, plus it is open source with nominal and affordable subscription plans.
What needs improvement?
Red Hat JBoss Enterprise Application Platform (EAP) can be improved by integrating different services related to Azure and AWS, and the open-source application and the EAP orchestrator Kubernetes platform must be more specifically usable for every user.
The support for Red Hat JBoss Enterprise Application Platform (EAP) could also be better than it is now.
For how long have I used the solution?
I have been using Red Hat JBoss Enterprise Application Platform (EAP) for about two and a half years.
What do I think about the stability of the solution?
Red Hat JBoss Enterprise Application Platform (EAP) is stable in my experience.
What do I think about the scalability of the solution?
The scalability of Red Hat JBoss Enterprise Application Platform (EAP) is pretty good, with minimum and maximum machines required being very efficient.
How are customer service and support?
The customer support is pretty good, but they need to be quicker in resolving issues related to Red Hat JBoss.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, we were using IBM's WebSphere Console, WAS console, which is famous, and we switched to Red Hat JBoss Enterprise Application Platform (EAP) because it is open source and is easy to integrate on AWS platforms.
What was our ROI?
Red Hat JBoss Enterprise Application Platform (EAP) has saved a lot of time in rapid deployment of applications, and for an existing migration project which was stipulated for a timeline of six months, it just took around two and a half months, specifically 80 days, achieving the target of completing within three months, along with the payment subscription being very nominal and affordable.
What's my experience with pricing, setup cost, and licensing?
The experience with pricing, setup cost, and licensing was nominal, and with the right guidance, it could have saved a few more bucks.
We can say that if we are charging around 0.75 cents per hour for a virtual machine on AWS, then in the Red Hat JBoss orchestrator, charges have seen significant improvement at around 0.58 cents.
Which other solutions did I evaluate?
We evaluated a few other options, but as JBoss is an EAP service, we were more interested in it being open source.
What other advice do I have?
I would rate Red Hat JBoss Enterprise Application Platform (EAP) around seven to eight.
I would select seven because even though it has its advantages, it does lack some flexibility.
I would advise others looking into using Red Hat JBoss Enterprise Application Platform (EAP) to have a trial period of 90 days to see if it works for them before going for a yearly or three-year subscription, which will significantly reduce the pricing.
I think there is a partner-based relationship with JBoss, but I am not completely aware of it.
I would rate this product a seven overall.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Finds cost-effective and adaptable capabilities but seeks better MLOps integration
What is our primary use case?
I have used Red Hat JBoss Enterprise Application Platform (EAP) in many projects. As a Java developer, I have worked with ATG and we have used the application server Red Hat JBoss Enterprise Application Platform (EAP) extensively for building applications and deployments.
We use Red Hat JBoss Enterprise Application Platform (EAP) in our application development. We have utilized Red Hat JBoss Enterprise Application Platform (EAP) as an application server for deployment purposes. For local running and operating particular applications locally, we have extensively used Red Hat JBoss Enterprise Application Platform (EAP). I have primarily worked as an application developer.
What is most valuable?
When we used Red Hat JBoss Enterprise Application Platform (EAP), it was mostly in monolith applications. It is a very cost-effective, efficient way of deploying and managing Java applications. The main important aspects are the flexibility and scalability of Red Hat JBoss Enterprise Application Platform (EAP). It runs on various platforms, from small devices to large servers, and we can easily scale down and scale up.
The integration with external applications, web servers, or other systems is very straightforward in Red Hat JBoss Enterprise Application Platform (EAP). We have robust security features. Additionally, there are excellent Red Hat JBoss Enterprise Application Platform (EAP) community resources available, which provides documentation for troubleshooting deployment issues.
What needs improvement?
Scaling could be improved, and more features could be added for MLOps deployment and microservices deployment. Integration with various cloud platforms and Jenkins-type features would be beneficial if Red Hat JBoss Enterprise Application Platform (EAP) could implement them. The product would grow significantly because Red Hat JBoss Enterprise Application Platform (EAP) supports Java, which is widely used as a programming language. It is particularly convenient for deployment and clustering purposes.
For how long have I used the solution?
I have used Red Hat JBoss Enterprise Application Platform (EAP) in numerous projects.
How are customer service and support?
I have not personally used the support team, but they maintain a strong community. In any technology, having a community makes things easier. Users can find discussions about common problems, solutions, and documentation within the community.
How would you rate customer service and support?
What's my experience with pricing, setup cost, and licensing?
I am not certain about the pricing details as the client or company handles those aspects. Since it is Red Hat, I believe it must be free.
What other advice do I have?
Red Hat JBoss Enterprise Application Platform (EAP) is one of the excellent application servers that organizations can utilize extensively. It uses open JDK and is part of the Red Hat team's software portfolio, offering very competitive pricing.
It operates on Linux, which is a stronger platform than Windows. The deployment processes are very efficient and fast. The entire package is very effective, especially when using Red Hat JBoss Enterprise Application Platform (EAP) on Mac, which offers numerous scaling options that can be configured easily.
It serves as an excellent application server and can be used with Jenkins. It is particularly efficient when used on Mac for development purposes.
On a scale of 1-10, this solution receives a rating of 7.
Automation aids installation while management consolidation needs improvement
What is our primary use case?
We are currently using Ansible for Jira installations and all the management tasks. We perform some tasks manually, however, Ansible helps in automating some of these processes.
What is most valuable?
I find JBoss to be lightweight and easier to manage compared to WebSphere. It allows for simple modification of applications and provides better clustering capabilities. The setup was straightforward and suitable for enterprise-level needs.
What needs improvement?
I would like to see improved booting of applications altogether on one page to manage all data instances from one location, similar to an AWS console.
Additionally, access and sessions could be improved in the scalable device.
For how long have I used the solution?
I have used the solution for over three years.
What do I think about the stability of the solution?
I would rate the stability around eight out of ten. It is quite stable for our needs.
What do I think about the scalability of the solution?
Scalability is a concern because it is not online, which limits online processes. This aspect can be improved.
How are customer service and support?
Red Hat support is good. We receive support from RDS and Red Hat, and the response time and quality meet our expectations.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
There are no competitors. WebSphere is still there, and we also use it alongside JBoss.
How was the initial setup?
What's my experience with pricing, setup cost, and licensing?
The price is somewhat high for an enterprise, however, it depends on organizational negotiations. Additionally, Red Hat support can be costly.
Which other solutions did I evaluate?
What other advice do I have?
Overall, I would rate the solution around seven out of ten. Despite some concerns, I would still recommend it.
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.
The best for Prod Environment
What do you like best about the product?
The chance to use the CLI to manage subsystems using commands and the possibility to create a controller to manage all hosts.
What do you dislike about the product?
Sometimes is not clear when a change requires a reload
What problems is the product solving and how is that benefiting you?
Using CLI we can script commands to orchestrate a huge amount of application servers
Recommendations to others considering the product:
Always live systems
Redhat JBOSS EAP
What do you like best about the product?
Offers all the components I need to develop an enterprise level business solution
What do you dislike about the product?
Rapid releases that are sometimes difficult to keep up with
What problems is the product solving and how is that benefiting you?
Business processing of credit card sales, payments, applications and auths
RedHat Jboss Enterprise
What do you like best about the product?
Lightweight, flexible architecture
Flexible management, configuration, and administration
Faster deployments
What do you dislike about the product?
Nothing much that i could say that i dislike
What problems is the product solving and how is that benefiting you?
Faster deployements
Easier configurations
Flexible architecture
Recommendations to others considering the product:
Nothing
JBoss is good!
What do you like best about the product?
JBoss is java EE 7 certified and has great features for cloud ready applications like high availibility, clustering, and even distributed caching. This makes it much easier to scale out enterprise wide and feel comfortable knowing JBoss will perform
What do you dislike about the product?
JBoss has gone through quite a bit of updates recently and it does take some time to learn new functionality and the value behind it
What problems is the product solving and how is that benefiting you?
We were looking to reduce our deployment time across virtual environments.
Recommendations to others considering the product:
There are tons of available resources for JBoss so be prepared to spend a good amount of time learning about the api's and migration points
Red Hat Jboss Enterprise
What do you like best about the product?
Almost five years with Red Hat JBoss Middleware(JBM), I used all kinds of Java EE and integration products, JBM stands out for low cost, wide integration with other products, excelent support and has a large community willing to help and share.
What do you dislike about the product?
Maybe a little hard for beginners SysOps and developers.
What problems is the product solving and how is that benefiting you?
Mainly for government elections process based on electronic election system, APIs with REST, web services projects.
Recommendations to others considering the product:
JBoss central has an arsenal of tools, components and plugins for write aplications fastest.
