On Derby...

by Dejan Bosanac

There were a lot of discussions lately about inclusion of Derby (aka JavaDB) in the Sun JDK. First of all, I personally think that it will not really change anything.

I'm sure that developers that wanted embedded database until now were savvy enough to download Derby and include it in the project. One other argument that has been often used is that this will put unnecessary burden on the size of the JDK itself. While this is certainly true, with current Internet speeds extra 2MB size is not something that would worry most of the developers, and of course there are always alternatives to Sun JDK.

But instead of heating up this discussion again, I would like to write down some of my experiences with Derby. The focus will be on Derby as an embedded database since I haven't (and don't plan to) use Derby as a standalone enterprise database server.

2 Comments

Tim O'Brien
2006-07-24 10:18:50
"I'm sure that developer experience will just get better over time."


Not sure, I mean there are a series of projects out there that have been around a while, instead of improving over time they failed to attract too much attention.


I think Derby needs an infusion of developer interest. Otherwise, we'll be stuck with using ij as a tool. (Note, you can always use a tool like DBVisualizer with Derby, I've done that, at least it approximates the level of tools available for other databases).


From my own experience Derby is reliable and fast, but I agree with you assessment that there are a lot of rough points around the project.


Putting it in the JDK? Yuck, no. Please, if anything I think they should remove things from the baseline Java distributions. Why does my server-side JVN need a sound API and Swing? I'd like to see these dudes move toward a buffet-style JVM. That way I think you've see more people bundling just the parts they need.


Thanks for the blog post

Dejan Bosanac
2006-07-25 03:20:55
> I think Derby needs an infusion of developer interest


The only good thing that can arise from putting it in the JDK is that Derby will get more popular and so attract more developer interest. But I'm afraid that's just my hope.


As for thrid-party database tools, I tend to use them (Aqua Data Studio, for example) whenever I can, but when your application is behind firewall and you can't access database from your desktop I'm afraid that ij is the only solution left.


Thanks.