Likelihood to Recommend Oracle Java SE is well suited to long-running applications (e.g. servers). Java Swing (UI toolkit) is now rather outdated, lacking support for modern UI features. JavaFX, the potential replacement for Swing, has now been separated out of Java core. Ideally, there would be a path to migrate a large application incrementally from Swing to JavaFX, but due to different threading models and other aspects, it is difficult. At this point, it is probably better to use an embedded web browser (e.g. JxBrowser) to provide a modern UI in HTML/Javascript and keep just the business logic in Java.
Read full review JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
Read full review Pros Plenty support built into the tool and IDE like Maven, Ant, Eclipse, IntelliJ. Strong object-orientation language and clear project structure. Wrapper underlines hardware and memory management so the developers can focus on business and implementation. It offers a huge library and framework support from third-parties and the community. Read full review MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments. Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc. Supports deployment in on-premise, virtual and hybrid cloud environments. Read full review Cons Commercial Licensing in 2019. Oracle will charge commercial organizations using Java SE for upgrading to the latest bug fixes and updates. Organizations will now need to either limit their implementation of Java SE or may need to drop it altogether. Slow Performance. Due to the all of the abstraction of the JVM, Java SE programs take much more resources to compile and run compared to Python. Poor UI appearance on all of the major GUI libraries (Swing, SWT, etc.). Through Android Studio, it is easy to get a native look/feel for Java apps, but when it comes to desktops, the UI is far from acceptable (does not mimic the native OS's look/feel at all). Read full review Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks. JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc. Read full review Likelihood to Renew We are planning to migrate away from Jboss to
Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop
Read full review Usability The language is fluent and has good support from a number of open source and commercial IDEs. Language features are added every 6 months, although long-term service releases are only available every 3 years. It would be nice if some of the older APIs were depreciated with more pressure to move to the new replacement APIs (e.g. File vs. Path), but transitions to new features are generally well implemented.
Read full review JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.
Read full review Performance Usually, Red Hat JBoss Enterprise Application Platform is good at performance and well suited for high traffic Java EE-based applications, but we have faced hard times performance tuning it for our specific needs. The product would be nicer if they would add a performance diagnostic and recommendations feature to it.
Read full review Support Rating Java is such a mature product at this point that there is little support from the vendor that is needed. Various sources on the internet, and especially StackOverflow, provide a wealth of knowledge and advice. Areas that may benefit from support is when dealing with complex multithreading issues and security libraries.
Read full review Fast response.
Read full review Alternatives Considered Chose to go with Java instead of Python or C++ due to the expertise on the ground with the technology, for its ease of integration with our heterogeneous setup of production servers, and for the third party library support which we've found was able to address some challenging aspects of our business problem.
Read full review We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.
Read full review Return on Investment The different versions make it harder to work with other companies where some use newer versions while some use older versions, costing time to make them compatible. Licenses are getting to be costly, forcing us to consider OpenJDK as an alternative. New features take time to learn. When someone starts using them, everyone has to take time to learn. Read full review Improved delivery timelines due to easy out of the box setup. It is a cheap subscription-based/open-source Java EE-based application server. This reduces the overall cost of delivery. Read full review ScreenShots