JBoss Reviews

JBoss plays a crucial role for many and yields positive financial results, particularly when leveraged for large-scale projects. Some teams, however, find the investment less favorable when dealing with smaller back-office operations due to high licensing costs. Many consider it a valuable tool that supports cost-effective automation allowing quick application deployment and reduced ownership expenses.

JBoss offers a cost-effective enterprise solution with flexible licensing, making it cheaper than competitors like Oracle WebLogic and IBM WebSphere. While JBoss is open-source and free, enterprises often pay for annual subscriptions that can range from $12,000 to $16,000. The subscription model is praised for including technical support and not binding to a specific server. Although some perceive it as expensive, many value its affordability, maintenance ease, and cloud deployment capabilities.

• "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."
• "The pricing of JBoss is more reasonable than that of WebLogic."
• "JBoss is an expensive solution."

Organizations primarily utilize JBoss as middleware for managing applications and servers, especially in banking and finance sectors. It serves as an application server, web server, and for API integration. Common uses include deploying web applications, handling business processes, and enhancing peer-to-peer transactions. JBoss offers compatibility with Java EE and clustering support, making it suitable for Java-based applications and enterprise needs. JBoss also facilitates automation with tools like Ansible and supports various deployment environments.

JBoss customer service and support receive mixed feedback. Many users have not utilized customer service directly, relying on strong community resources and documentation instead. When contacted, Red Hat support provides satisfactory assistance, though some find email-only communication slow. Support quality may vary based on purchased contracts, with some rating it high for responsiveness and reliability, while others find responses less effective. Many users rely on internal support teams and have not required external assistance.

JBoss's initial setup is often considered straightforward and easy by many, though some find it complex due to integration needs. Setup duration varies; some complete it in a few hours, while others take longer, depending on clustering or deployment approaches. With experience, complexity decreases in subsequent setups. The process benefits from a knowledgeable team but can be maintained by a smaller group. Compared to Tomcat, JBoss may require more steps, yet many agree it's manageable and rates highly for simplicity.

JBoss is scalable, supporting both vertical and horizontal scaling. Users report no significant issues, though better documentation could improve load balancing understanding. Some organizations experience occasional scalability challenges, but JBoss fits organizations of all sizes. Many rate its scalability highly, noting support for clustering and flexibility in server configurations. JBoss accommodates numerous users efficiently, with reported uses in varied business environments, from small teams to large enterprises. It supports scalability with flexibility in infrastructure needs.

JBoss stability is viewed positively with ratings commonly ranging from seven to ten. Users note its reliability under heavy loads, especially when properly configured on Linux. It runs dependably once deployed, though administrators suggest understanding Java memory settings for optimal operation. Challenges appear mostly in development and UAT rather than in production. Some users observe issues primarily due to older code or poor deployment practices. Migration to cloud services like AWS and GCP aims to modernize and maintain its stability.