Oracle Java DB Reviews

Oracle Java DB is one of the databases we use, and we use quite a few databases. It's either Oracle or Microsoft SQL Database or MySQL. We've been doing it for many years, but all our clients work on different databases. They use non-transactional and non-relational databases. One of our clients also uses MongoDB.

Oracle Java DB isn't used much as many of our clients use Microsoft SQL Server Database. We have a client in the healthcare space that is using it, and we use this for storing all the information of this space.

It's very clever. Oracle Java is one of the first object-oriented languages that we've had. A lot of the data and the languages are in Python. I think the concept is the same. But Oracle Java is very object-oriented. I think Java was one of the first to come out with object-orientation. I used Java to develop the APIs, and it's recommended, and we use it.

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.

We have been using Oracle Java DB for many years.

Oracle Java DB is very stable. 

It's scalable, but it depends on how you deploy it. As long as you're not using monolithic applications, it's scalable.

Technical support has been very clear and convenient, and we can always reach out to them.

The initial setup is easy, and the deployment time is really nothing.

Quite a few clients would look at Python or Node.js. If you take Python as an example, it also supports machine learning.

This is a fairly stable language, and it's been in the market for several years. In fact, it's been around since about 1995, when the concept of object orientation started. People should use it because it's clever.

On a scale from one to ten, I would give Oracle Java DB a nine.

Our primary use case for this solution is for applications within the bank that are minor applications and web applications developed in house.

The solution's capability to handle large data sets, large volumes and indexing are the most valuable features. Additionally, since we deal with large volume data sets the security and transparent data encryption are embedded. So we don't need to worry about security tools.

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.

The solution is stable.

We haven't used this solution on a large scale, because we do not have many users. Between 50 to 200 users currently use it in our organization.

I don't have any experience with customer service and support.

I cannot comment on the deployment process as I was not very involved in projects.

I rate this solution a six out of ten. The solution is good, but it can be improved by making it user-friendly and improving its scalability.

My primary use case for this solution is for storing application data.

With this solution, we are able to write queries more efficiently and the management of data has become better and easier.

The feature I have found most valuable is the memory management algorithms, which are much more efficient than the open-source.

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 product is 99.99% stable.

This solution is easily scalable - we can easily scale the number of servers we can deploy the application on.

The technical support for this product is good, with no issues.

I have previously used several other solutions, including MySQL, Oracle, and Node DB.

The initial deployment didn't take much time and only required one person.

Our ROI has been a 600% growth in stock price, one of the biggest increase rates for any of the global top 50 companies.

The product's pricing is very friendly, with no extra costs after the licensing fees.

I would always suggest going with this product if the add-ons available through Oracle are required. I would rate this solution as nine out of ten.

I use Oracle Java DB for creating Java stored procedures in Oracle databases as the means of communication with other types of databases. I would take information from those other databases and bring it into the current Oracle database. The solution can operate on-premise or on the cloud.

The additional value of having Java inside the Oracle database is all the security that is applied to an Oracle database will be enforced on Java's stored procedures as well.

Every Oracle session uses its own Java virtual machine. These sessions are independent, highly concurrent, and very reliable because of this.

The Java store procedure needs to work with the data residing in the same Oracle database which makes the access to the data lightning-fast because everything is within the same memory.

The solution should continue to keep updating and improving the Java language.

I have used Oracle Java DB within the last 12 months.

The stability is very good. Java is a computer language, and you can write stored procedures using this language. Stability is awesome because it is all supported by Oracle database and Oracle relational database management system. It watches very carefully all the processes that are running, it is very stable and very secure.

Oracle Java DB is installed with the Oracle database software and I do not know whether it is possible to install the Oracle database without this option.

I rate Oracle Java DB a ten out of ten.

We are a system integrator and Oracle Java DB is one of the products that we implement for our clients. The primary use cases are concurrency, patching, and automation.

The most valuable feature is automation.

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.

This company has been using Oracle Java DB for the past 20 years.

This is a stable product.

This is not a highly-scalable solution.

I don't have to do the implementation myself. I would say that it is complex, although it is straightforward if you have the right support.

The implementation strategy follows the SOAR methodology from Oracle.

Using this product will lead to a reduction in operational costs.

I would rate this solution a six out of ten.