Lead Enterprise Architect at a financial services firm with 10,001+ employees
Real User
2022-08-16T13:37:23Z
Aug 16, 2022
The solution could be more user-friendly. It comes with baggage so it should be simple to use. The PLS QL and the queries are efficient, but there isn't a major difference between the normal Java and Oracle Java DP. So, it should be a little more user-friendly and developer friendly. Additionally, handy release notes could be included in the next release because they will indicate the difference between the previous and the latest versions. For example, we couldn't find the use cases when we were doing the research. So whenever a search is done in the new DB, and we research Mongo or Cassandra, we get a lot of use cases from these communities. This solution is lacking because it's a giant, and everyone knows that most enterprise scales DBs are either used by Oracle products or in core banking. However, for Java DB, there should be more use cases, so it's easier for the developers and the users to pick and choose the right platform, application, domain, and how to utilize them.
With respect to the product's consistency, there's a lot of scope that could be introduced in regulator basis. In the next release, I'm looking for an improvement in consistency issues with respect to timeframes. The regulator databases could also be improved. I also think the price fluctuation with the various SQL implementations is something that should be looked into, as well as increasing Node's SQL support into Oracle.
Senior Executive at a computer software company with 11-50 employees
Real User
2021-02-09T14:52:50Z
Feb 9, 2021
It'll be better if Oracle Java supports open source technologies, like Node.js. Many APIs can be developed in applications like Node.js, and it's a lot easier to use a programming language like Node.js because it's totally open-source and available. It also has a lot of APIs that I can download and access from anywhere. You can, of course, use microservices, but I think the marketing around microservices products isn't working, and a lot of folks seem to be using Node.js and Angular as their programming languages for API development. Oracle Java also supports a lot of the microservices concepts, and a lot of the work can be done within that. Java needs to come out with a lot more and let us do more with the UI. This will benefit the future of Java.
Principal Consultant at a marketing services firm with 11-50 employees
Consultant
2020-12-03T23:32:53Z
Dec 3, 2020
There should be a software-defined Oracle DB, as well as a software-defined cloud management platform. The biggest lesson that I have learned from using Oracle products is vendor lock-in.
What is a relational database? A database is an organized collection of structured data that is electronically stored in a computer system.
A relational database is an intuitive database that stores and supplies access to various related data points. A relational database is based on the relational model where data is stored in tables in an intuitive and straightforward way, similar to an Excel spreadsheet. In this management system, tables are used to store complex data, which can be...
The tool might be integrated, but we see performance issues because of overhead.
The solution could be more user-friendly. It comes with baggage so it should be simple to use. The PLS QL and the queries are efficient, but there isn't a major difference between the normal Java and Oracle Java DP. So, it should be a little more user-friendly and developer friendly. Additionally, handy release notes could be included in the next release because they will indicate the difference between the previous and the latest versions. For example, we couldn't find the use cases when we were doing the research. So whenever a search is done in the new DB, and we research Mongo or Cassandra, we get a lot of use cases from these communities. This solution is lacking because it's a giant, and everyone knows that most enterprise scales DBs are either used by Oracle products or in core banking. However, for Java DB, there should be more use cases, so it's easier for the developers and the users to pick and choose the right platform, application, domain, and how to utilize them.
With respect to the product's consistency, there's a lot of scope that could be introduced in regulator basis. In the next release, I'm looking for an improvement in consistency issues with respect to timeframes. The regulator databases could also be improved. I also think the price fluctuation with the various SQL implementations is something that should be looked into, as well as increasing Node's SQL support into Oracle.
The solution should continue to keep updating and improving the Java language.
It'll be better if Oracle Java supports open source technologies, like Node.js. Many APIs can be developed in applications like Node.js, and it's a lot easier to use a programming language like Node.js because it's totally open-source and available. It also has a lot of APIs that I can download and access from anywhere. You can, of course, use microservices, but I think the marketing around microservices products isn't working, and a lot of folks seem to be using Node.js and Angular as their programming languages for API development. Oracle Java also supports a lot of the microservices concepts, and a lot of the work can be done within that. Java needs to come out with a lot more and let us do more with the UI. This will benefit the future of Java.
There should be a software-defined Oracle DB, as well as a software-defined cloud management platform. The biggest lesson that I have learned from using Oracle products is vendor lock-in.
In terms of improvement, I'd like an automation tool that is lower priced. The core prices are very high. We have to train our employees in Java.