We need an embedded, zero administration simple database for this project. Here I have outlined the differences and similarities between SQLite and Java DB/Apache Derby.

SQLite & Derby	SQLite	Derby
-Operate directly from disk -Embeddable SQL database engine -Java bindings -ACID compliant (will survive a program crash or power failure). -Similar query operation speed/performance	-Stores data in single cross platform disk file -Bindings for Java + several other languages -Portable, but requires multiple binaries -Understands a subset of SQL92 language -Code footprint < 250KB -Allows multiple simultaneous readers and a single writer.	-Spreads its data across multiple disk files -Portable but requires JVM; usable by JVM languages -Understands all of SQL92 and most of SQL99 -Code footprint ~2000KB. -Allows only a single process to have the database open at a time in its embedded mode. -Offers a full client/server mode -Potential for unpredictable speed penalty with use on different VM (even on same hardware/os)

Conclusion: Clearly, there is not much of a trade off for either database. We will utilize SQLite since since it stores its data in a single cross platform disk file, has a smaller code footprint and has a Java Binding API.