IBM has announced plans to release its Java-based SQL database
engine "CloudScape" as an open source tool named "Derby".  This
page offers a comparison of Derby and SQLite.

*Zero-Administration*

Both SQLite and Derby offer zero-administration, embeddable SQL database engines
that store all data in a single cross-platform disk file.

*Host Language Support*

SQLite is written in ANSI-C.  It supports bindings to dozens of language,
including Java.  Derby is only available to applications written in Java.

*SQL Language Support*

Derby supports all of SQL92.  SQLite only supports a subset of SQL92,
though the supported subset is very large.

*Executable Size*

The footprint of SQLite is less than 250KB.  The footprint for Derby
is about 2000KB or about 8 time larger.

*Concurrency*

SQLite allows multiple simultaneous readers and a single writer.
Mutiple processes can have the database open simultaneously.  Derby
only lets a single process open the database at one time.

*Crash-Resistance*

An SQLite database will survive a program crash or even a power failure.
With Derby, if you pull the power plug at the wrong instant, you risk
corrupting the database.  (Someone please verify this.)

*Database File Size*

No data is currently available on the relative sizes of the database files
for SQLite and Derby.

*Speed*

No data is currently available on the relative speed of SQLite and 
Derby database engines.