Hi All, To refresh us all, we discussed earlier on this list about mysql alternatives [1] and the conclusion was to go with embedded database for default configuration and provide documentation on how to change the database to mysql at deployment time. Derby was discussed as a viable option, but before we jump into implementation I want to solicit feedback from every one. I do not have any recent first-hand experience with any of them, so my vote will be +1 to who ever convinces me that they are convinced about one over other :)
The three most popular in-memory databases Derby, H2, HSQLDB all have license compatibilities. db40 is GPL. Java DB seems to be based on Derby and ALV2 but could not figure out why we should use Java DB and why not just the Derby. In any case, do folks have any practical experiences and preferences over any option? Just note that Airavata has more scalability and reliability requirements over performance. Cheers, Suresh [1] - http://markmail.org/thread/3bzlnwr75mylh7mu
