Oracle Java DB Reviews

We are using the Java side, which is built into the database, and the application is using that portion.

Because it's on the database side, we are able to process all the reporting and processing using Oracle Java DB in the database itself. The database is quite robust in terms of performance from the SQL side. We operate that and the Java side together. Since it's totally integrated, we don't need two different engines to do one portion and something else, which is very helpful.

I have experience connecting to a database with Java by using Java code and interrogating the database.

The valuable features include connecting to the database and retrieving data. Additionally, I can use SQL Developer to check the data and update tables in the database if needed. It allows me to update the databases, records in the tables, or change or delete some records as needed.

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.

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.

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.

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.

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.

Our primary use case for this solution is to automate our website. 

It has a programming language so anything that we require for Selenium is all available there.