Reviews (1-2 of 2)
The product I worked on at IBM supported all the major database vendors, including Derby. Since Derby is free, most development and QA was done with Derby, although not many customers had adopted Derby as their production database vendor.
- Much easier to use and learn than most commercial databases.
- Derby database errors are well documented.
- Most complex queries supported as well as by other database vendors.
- It may not scale as well as some more mature database products.
- Used it primarily from the command line with openjpa and jdbc, and from third-party clients such as Squirrel.
- May benefit by providing more sophisticated tools to optimize query performance.
Read Renato Ermann's full review
[It's] Well suited for development and testing environments.
June 13, 2018
Score 10 out of 10
In the Project I was using Apache Derby, we were shadowing larger databases (MS SQL + Cygnet), and providing some failover for those platforms. Most of the Use case was research-oriented, but it allowed the Risk Modelers to grab a subsection of data from these two data sources, and then combine them inside an apache derby instance. Given its size, it was a good fit.
- Apache Derby is SMALL. Compared to an enterprise scale system such as MSSQL, it's footprint is very tiny, and it works well as a local database.
- The SPEED. I have found that Apache Derby is very fast, given the environment I was developing in.
- Based in JAVA (I know that's an obvious thing to say), but Java allows you to write some elegant Object Oriented structures, thus allowing for fast, Agile test cases against the database.
- Derby is EASY to implement and can be accessed from a console with little difficulty. Making it appropriate for everything from small embedded systems (i.e. just a bash shell and a little bit of supporting libraries) to massive workstations.
- Not as well positioned in the market as the "big dogs" (Oracle, MSSQL)
- Been around awhile, and not a lot of exposure. This I believe is primarily due to it's relation to the Apache Project (which is not bad, but they don't force big, lumbering corporate volume licensing on you), and thus people are a bit gun-shy about NOT throwing money at something
- Java is still "slow" compared to C/C++, thus making Derby a bit slow too
Read this authenticated review
Derby is absolutely the best when it comes to needing a small, embeddable RDBMS in your applications. Certain jobs, like Risk Modeling, are perfect for a database that is small enough to fit into memory with no trouble then store data from various sources, and then allow a user to access those data sets quickly.