by grendel
I've been using Derby (it was once called Cloudscape) for years now in various projects. It has yet to let me down. No corruption, it's very robust, backups work fine. Performance has never been an issue, but I can't say I've really pushed Derby to its limits.
Our latest project uses Hibernate to integrate with Derby - no issues there. We also use SQuirreL SQL with Derby - that works nicely too.
2 of 2 users found the following review helpful. Was this review helpful to you? Yes | No
by blooby
We use derby in our search engine project which is in beta stage.
Having tried alternatives (mysql , postgre , oralce ) derby provieded us
unmatched performence over large datasets our current dataset is around 30GB
for each server we read more than a million rows at a time and insert around
300 records per second we are confident that
derby will not let us down along the way. we are planning to hit over 100GB mark for
2 of 2 users found the following review helpful. Was this review helpful to you? Yes | No
by papercut
The sign of a good embedded database system is not who’s running it, but rather who doesn’t know they’re running it! The ideal database is one that sits there in the background, working hard, and never raising a peep nor complaining. That’s Apache Derby!
We’ve been using Apache Derby as the default database for our print management application, PaperCut NG ( http://www.papercut.biz/ ), for 2 years now. Our software has been
1 of 1 users found the following review helpful. Was this review helpful to you? Yes | No
by jfalgout
Derby is an excellent embedded database when working with Java. I've worked on a project for over a year now that is using Derby in an embedded fashion. We use Derby embedded within a data profiling product. The purpose of the product is to help business users understand the nature of their data and also to audit data.
Derby is used as the container of data and the generated metrics. A Derby database is created for every execution and is
I'm a relatively inexperienced programmer (< 2 years in Java), with absolutely no prior experience with database work at all. But derby has allowed me to easily get my feet wet in the database world without any major hassles.
I love the fact that it's written in java. Since I only have a Linux box to develop on, but must deploy for a Windows environment, simply being able to package derby.jar with my build and knowing that it will work is very handy.
Plus, OpenOffice and Netbeans both support it, which is handy.
by dveres
I'm currently using derby for a distributed client architecture. I've tested with 3~5 million records that need to be keep in sync through all the clients. Derby has worked beautifully, selects, inserts all very fast. And I've even seen several searches with the same indexes run faster on Derby than Oracle. I eagerly await the continued development of Derby. I would like to see cursor statements similar to Oracle.
1 of 3 users found the following review helpful. Was this review helpful to you? Yes | No
by Alex Snaps
We've been using Apache Derby embedded into rich clients we've been delivering to various customers. It is undeniable that it strength reside in being able to power any Java application, being it rich client, web application or others completely hidden from the user / installer.
It has been deployed together with a JPA implementation, fully enabling object oriented programming principles to developers. We've used it to distribute the
1 of 3 users found the following review helpful. Was this review helpful to you? Yes | No