Originally posted by Gregg Bolinger:
I've worked with both. They seem about the same to me. Anyone have a preference and why?
How can there be any question? With that name, it's obvious that the Apache product is superior...
But seriously, I asked a trusted co-worker with serious experience with both; his opinion was that HSQLDB was better for small-footprint applications (e.g. embedded in a cellphone app or small part of a
J2EE app), and Derby was the better choice as a desktop engine for most purposes. He mentioned that the version he worked with (prior to the most recent 10.1.1.0 release) had some small db2-like issues that were non-standard, but he didn't explain what those were.