Oracle Java SE is a programming language and gives customers enterprise features that minimize the costs of deployment and maintenance of their Java-based IT environment.
N/A
Qlik Analytics Platform
Score 7.1 out of 10
N/A
The Qlik Analytics Platform (QAP) is a developer platform for building custom analytic applications based on rich frontend and backend APIs. It gives full API access to the Qlik associative engine to build rich data-driven analytic applications, for example when building web applications for extranet and Internet deployment.
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.
Qlik Analytics Platform has helped us track turnaround time as well as sales volumes. We can display metrics in a multitude of ways and can then slice it up in even more ways by adding filters. It is nice that you can filter down the data by essentially "Qliking" anywhere to find insights. Qlik Analytics Platform has been extremely beneficial in reducing manual reports. We are able to automate numerous reports in addition to setting up alerts, through Nprinting, that will notify users when certain metrics are hit. For example, if our turnaround time exceeds a certain number, we can alert business stakeholders so they can take a closer look. We can also send notifications to sales representatives when their territories are underperforming.
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).
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.
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.
Customer support is provided through resellers, and finding the right reseller for your context can be a challenge. However our support from our last two resellers/partners has been largely very good. The online community is strong, though obviously doesn't replace having local technical experts working with the product and managing it.
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.
Qlik is a platform with more scaling ability and functionality compared to PowerBI. PowerBI is the prior step before passing to Qlik, however, Qlik provides more functions and abilities to the business domain unit with better management capabilities for the IT team that set it up. In the end, we implemented Qlik for functionality and scalability.
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.
