Oracle Java SE vs. Red Hat JBoss Enterprise Application Platform

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.

Incentivized

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.

Incentivized

• 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.

Incentivized

• 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.

Incentivized

• 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).

Incentivized

• Difficult to replicate configuration outside of a container environment
• Still requires quite a bit of knowledge of the CLI
• Integration with deployment tools requires CLI knowledge

Incentivized

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

Incentivized

Oracle Java SE provides the new features along with timely security patches. New features like Record patterns and pattern matching for switches are very useful. With every new release of Java, it is getting better. Sequenced collections are also an interesting feature added to Java. With all these new features, backward compatibility is also maintained.

Incentivized

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.

Incentivized

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.

Incentivized

Fast response.

Incentivized

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.

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

• 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.

Incentivized

• Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
• Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.

Incentivized