JBoss and Tomcat are both prominent in the application server category, each catering to different enterprise needs. JBoss seems to have the upper hand with its enterprise features, vendor support, and integration capabilities.
Features: JBoss offers advanced J2EE features including queues and topics, failover, and high availability. It is suitable for enterprises due to its good scalability and stability. Additionally, JBoss benefits from vendor support and a seamless integration with Java applications. Tomcat, on the other hand, is lightweight and open-source, ideal for web projects with low budgets. Known for its simplicity, it provides easy configuration and stability, supported by a large community and comprehensive documentation.
Room for Improvement: JBoss could improve its runtime diagnostics, disaster recovery features, and support integration with Red Hat OS, along with modernization towards cloud features and better log management. Tomcat would benefit from enhanced scalability under heavy traffic, simpler clustering, improved security features, and an easier logging and configuration process for better usability.
Ease of Deployment and Customer Service: JBoss is mainly deployed on-premises with some hybrid cloud usage; user satisfaction with technical support varies by contract type. Tomcat operates in a mix of on-premises and cloud environments, relying heavily on community support with limited direct technical support interaction. JBoss leans on Red Hat's support, whereas Tomcat users utilize open-source community resources.
Pricing and ROI: JBoss provides flexible licensing, appealing as a cost-effective alternative to proprietary solutions like WebLogic, but requires a paid subscription for support. ROI perceptions are mixed, particularly in smaller deployments. Tomcat is free and open-source, attractive for budget-conscious projects. However, commercial environments may face costs for Java licenses. The ROI perception remains generally positive due to its no-cost model, although some organizations opt for paid alternatives for additional features.
This flexibility translates to a lower total cost of ownership.
We receive support from RDS and Red Hat, and the response time and quality meet our expectations.
They are proactive in looking into the tickets we create in case we have unresolved queries.
It is quite stable for our needs.
Making it lighter and more modular would probably be beneficial.
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.
Tomcat needs a more robust logging error details feature; the current logging feature is available, but it should be more user-friendly.
JBoss is the cheaper option out of the three when compared to WebSphere and WebLogic.
The price is somewhat high for an enterprise, however, it depends on organizational negotiations.
It allows for simple modification of applications and provides better clustering capabilities.
JBoss is more flexible and keeps up with modern technologies, supporting newer versions of different libraries.
The advantages of Tomcat include its flexibility; we can increase the heap memory and the size of sessions as per our custom needs.
Tomcat is a reliable and efficient web server, popular for hosting and running Java-based applications. It is praised for its scalability, compatibility with different operating systems and development frameworks, and its ability to handle heavy workloads.
Users appreciate Tomcat's ease of use, robust performance, reliable server functionality, seamless integration with various platforms, extensive documentation, and strong community support.
We monitor all Application Server reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
