Well, you haven't googled hard enough. There are plenty of qed entries. See the product maker at
http://www.quadcap.com/home.html
Since I have no experience with QED, I can only give some differences I noticed.
- QED is a single file db
- QED is useable for Java applications only (at least that is what I could find)
- QED is locally installed at the PC and has no server and no db administration
QED's pure Java engine provides very high performance, since database accesses can be performed locally, without the necessity of a network round trip for every operation. Conventional JDBC drivers, no matter how fast the back-end database, incur network overhead -- frequently the bottleneck in a database application. A configurable in-memory cache also helps boost performance by reducing disk operations.
QED is designed for applications which need full database functionality without administrative overhead of a typical database. Because of its small memory/disk footprint, QED can be embedded in end-user applications for which a database would otherwise not be practical.
In my opinion, QED is a good solution with small websites that run on their own and have no need to communicate or exchange data to other websites.
Ronald :cool: