Apache Derby

What do you like best?

This is a Relational database management system. It is a database system implemented fully in java. It is very easy to install, deploy, and use. I would say it is well suited for beginners who want to learn DBMS as it is easy to configure and use. It has a very small setup to install. It is available with a command-line tool called "ij tool" to access databases and fire various SQL queries. Apache derby is good to use for java applications.

What do you dislike?

Apache derby has quite fewer features than any other database system. It is not suitable for large scale enterprise applications. Some of the SQL statements which are available in MySQL are not there in apache derby. As it is made in java so it is comparatively slower than C/C++ database systems. It is less popular in the developers' community.

Recommendations to others considering the product:

If your software application is not a highly distributed enterprise application and highly scaled then you can use this database system. It is a good database system for business software of shops, stores, and malls for maintaining details about customers, products, payments, etc.

What problems are you solving with the product? What benefits have you realized?

Apache derby has good support for JDBC. It has an inbuilt driver for java database connectivity. So I basically use this for my java applications to access data from the database of apache derby. I feel that for the common less scalable products it is a very good choice. As it's set up size is also very less. I am using it for the company's website to store the student data and login information,