Share your experience using Oracle Berkeley DB

I use the solution in my company for my production projects. I have had hands-on experience with Oracle APEX and have done some research about it to figure out if it is suitable for my next project or not. I use Oracle Berkeley DB for normal MVC projects. We get some sort of data from the users, then we put them into the database, and after that, we do the query from there, so it is not a big deal.

The most valuable feature of the solution revolves around something known as paging. Oracle is the best among the other products in the marketplace, especially in terms of stability and performance. The tool's performance is good, and I don't have any problems with it. The reason that we chose Oracle is because we don't want to have those headaches with other products in terms of performance. We use Oracle RAC and Oracle Berkeley DB along with most of the things that are used in production with the DBA of that project. I am the designer and the architect of the applications in my company.

One of the things that I want to see in Oracle Berkeley DB is a driver for reactive programming. I think the tool's official driver for reactive programming, especially for Java, is the thing that Oracle needs to be more agile in, specifically in those areas of programming that other products are currently going into. Other tools have become more innovative in many areas. I know that Oracle has many responsibilities in maintaining the situation with the current projects and so on. I think it would be very cool if Oracle could make improvements to its projects, as it can help me with my current projects. One reason why I don't choose Oracle Berkeley DB is because we want to go for reactive programming, along with Project Reactor from Spring, but we don't have the official driver for it.

I have experience with Oracle Berkeley DB.

The tool's stability is very good because we don't have any complaints about any data loss, and most of such areas are used in EVA DB. I don't have any problem with the product's programming area.

It is a scalable solution. The people involved in production in our company really like the product.

The production team in my company uses the tool.

The product's initial setup phase is not so hard for me to integrate the database and drivers. It is a straightforward process. At my company's programming level, we had no problems with the tool.

There is a need to pay for the licenses and features of the tool. It can help other people use the tool properly.

Giving out some free subscriptions and offering some premium plans for enterprise solutions that Oracle presents to the audience can help other people who want to use it. Being more agile in adapting to the new features that other DBMS tools and NoSQL Database Engines offer to the users can be helpful.

In terms of the tool's replication features, one thing you will have in your marketplace is Oracle RAC. When you use Oracle Berkeley DB as a standalone database, we have some problems in replicating such data.

Actually, at the programming level, I don't have so many problems integrating the databases. At the production level, we actually use the Oracle RAC for our project. Actually, in those areas, I don't have any problem with the tool either.

I rate the tool as an eight or nine out of ten.

The product's interface could be more intuitive and user-friendly.

I've been using Oracle Berkeley DB for about a month now.

I would rate the stability around five or six. It has been stable. 

I rate the product scalability around eight, although I haven't extensively tested it.

I used MySQL before Oracle Berkeley DB.

It took around 15-30 minutes to deploy Oracle Berkeley DB. 

I rate the initial setup process a seven, as the user interface was a bit confusing during the setup process.

I rate the product's pricing a five out of ten. 

The product meets all the essential business requirements. I rate it a six out of ten.