On 12 July 2011 01:46, Suresh Marru <[email protected]> wrote: > 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.
The only practical experience I have of Derby is as the default database for Apache Wookie. As far as I am aware it has not been tested at scale in this project, certainly I have not done so. However, it is I that did the migration from MySQL to Derby and I found it an easy process with no surprises around the corner. In general I would recommend using an Apache project over another third party project. Mainly because it's easier to be heard if we need to engage with the project community. Over the coming years Airavata contributors are almost certain to find themselves at the same events as Derby contributors. Furthermore, even though merit does not transfer from one ASF project to the next, it does send a strong signal that you are a real open source contributor and thus are likely to attract attention to your communications with the project (not that Wookie has needed to engage with the Derby community in its use). Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
