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.

The tool might be integrated, but we see performance issues because of overhead.

I have been using Oracle Java DB for a long time.

The technical support has been good and is improving day by day. One mentor once told me that any support is like an onion. As you peel more, you get the core solution. The technical support has to be cost-conscious. Initially, you get somebody who's not experienced and goes by the book. As you go through the problem, you start peeling the onion and come to the core problem.

Positive

I've been using Oracle for a long time. Once, I attended an interview with Amazon. I was getting interviewed, and I thought Oracle was the best. The interviewer gave me facts about how other databases, like NoSQL and MongoDB, perform better in certain use cases. It was an eye-opener for me because I was biased towards Oracle Java DB.

We have been upgrading and moving to new environments. I was involved in the solution's initial setup. Some things in the setup are very smooth sailing. However, some setups become complicated because what they set up doesn't meet your needs. So, some tweaking is necessary in certain instances. Having a good understanding of the tool really helps.

Oracle Java DB is easy to deploy if it's a new setup. Migrating from an old environment to a new environment takes time because you need the old functionality. A first-time deployment of the application is easy. We just did a default setup and started using it. When we have to migrate, there is too much baggage behind that application, especially from the security point of view.

Oracle Java DB is a good product, but we also have to put in extra effort to use it. You get a good return on investment with the solution when it is handled by people who understand the product and when resources are added to it.

Oracle Java DB is a pricey solution.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a seven out of ten.

I think the solution is moving in the right direction because no architecture supports all sorts of processing. A lot of other portions are getting integrated as new needs come in.

With integration, we are seeing improvements in the solution's performance. The application and the business unit demand more processing. Everyone does simple things, but you have to do better and faster processing to be on the niche end.

Oracle Java DB requires maintenance. We conduct a security scan every month. If something is identified, we have to patch it because cybersecurity is critical.

Since the initial setup becomes difficult when done manually, we try to automate it. We have a small team to maintain the solution. We are a consulting company that provides support. We ask for resources for a new setup and then automate it. So, it's a cyclic process.

We are still learning and using general AI. However, generative AI is getting more attention. Java becomes important because some components will run very well from that side when we need that functionality. We haven't done too much. It's just more of being comfortable with it. We are pushing for it from the technologies, but the business needs to see a justification for that. So, it's a work in progress right now.

I would recommend the solution to other users. However, I think everybody should understand what they need and compare tools because other tools might better serve their use case.

Overall, I rate the solution an eight out of ten.

I have a project where I previously deployed using Java while working on my internal project. Now, in my organization, they are using Oracle Java DB for backend purposes, particularly for the backend.

In terms of deployment of Oracle Java DB, it is simple with not much configuration required.

To deploy and configure the variables of Oracle Java DB, it will take up to only 30 minutes.

I can do it all by myself without any help.

Oracle Java DB has a huge community. If we encounter any issues, there is a large community available where we can find solutions easily regarding Oracle Java DB.

We did not use the replication or inbuilt replication from Oracle Java DB. We have separate core functions to replicate the database and migrate the database.

We are not using the inbuilt encryption of Oracle Java DB. We are using encryptions such as AES. We are currently using these to encrypt the sensitive data. We encrypt not only passwords but mostly all the data.

I work with the on-premises version of the product and I am not using the cloud version.

I did not find any difficulties in Oracle Java DB.

Integrating Oracle Java DB feels comfortable with my existing Java skills and applications.

Technical support is very fine in Oracle. That is not an issue.

Previously, I used and provided a review for Netifi or OpenJDK Java.

In terms of deployment of Oracle Java DB, it is simple with not much configuration required.

I can do it all by myself without any help.

Regarding the price of Oracle Java DB, it is affordable and is not an issue.

I can give around 4 to 4.5 regarding metrics on resource consumption for Oracle Java DB. Pricing for Oracle Java DB I can give around 8 to 9. My overall review rating for Oracle Java DB is 9.

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.

Oracle can improve by providing more connection string variations and relay servers on the path to the database. Various ways of connecting would enhance functionality.

I have maintained and used it over several years, although I cannot specify the exact duration.

I have to consider that connections pass through some firewalls. The connection to the database will need to pass through some firewalls, requiring firewall rules for the connection.

The database can grow depending on the server's capacity.

Oracle provides patches regularly, however, I don't have direct contact with them.

Positive

I have used SQLite and other different kinds of databases in the past. SQLite is easier to handle for small databases as it requires less complexity unlike Oracle.

The initial setup for Java DB is relatively easy. It involves setting up the connection string, user, and IP of the database location, and possibly passing through a relay server.

I have no idea regarding the pricing, however, a license is required. One needs the Oracle driver to connect to the database.

I used SQLite, which is simpler as it just requires interrogation on small databases.

It's important to consider several settings and connection strings, as well as firewall rules when connecting to the database. 

I would rate the overall solution nine out of ten.

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.

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.

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.

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.

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. 

I have been using Oracle Java for seven years. 

We have ten users who use this solution. 

We only use a limited scope of Java. The development team primarily uses it. 

I would rate it an eight out of ten. Not a ten because it's difficult to learn.

It's easier for developers but as QA it's difficult to train and deliver. I'd prefer an automation tool that doesn't have as much coding.

We primarily use the solution for our invoicing needs in regards to sales. We also use it for customer information as well.

Running queries is the solution's most valuable feature. Querying the database for reports and sales tallying is very helpful.

There have been no issues in relation to stability. We've never really had do to any recoveries. It is very stable.

I've never tried to scale the solution, so I can't speak to the solution's scalability.

We haven't needed to contact to technical support yet.

When I arrived at the company, the solution was already set up, so I didn't deal with the initial implementation.

We use the on-premises deployment model.

I'd rate the solution ten out of ten.

When we're interacting with the solution, it's usually other third-party software solutions that interact with Oracle DB. As far as our interaction, it's quite limited. We don't do much unless it's real queries. We use SQL, we use Oracle. There isn't much that we would need from the solution. We're getting the job done at the end of the day.