Cloudscape Gains Momentum
A reader writes: "There's been a lot of bits written recently about the growth of Open Source databases; as well as IBM's patent gift, as their release of the Java database Cloudscape. There's a contest running on SourceForge.net around Cloudscape; download and run with it." SF.net is part of OSTG, like Slashdot.
wouldn't it be quicker to print your data on paper and sort it by hand ?
A Java database?
Isn't that a little bit like writing a Fast Fourier Transform in LISP?
There are lots of things that Java is perfectly suited for. Databases are not one of those things.
Karma: Excellent Birds (mostly as a result of listening to Laurie Anderson)
Wasn't Cloudscape donated to the Apache project, where it changed its name to Derby? Don't IBM think that offering a download of "Cloudscape" is going to confuse developers?
Karma: It's all a bunch of tree-huggin' hippy crap!
The submitter mispelt 'cynical ploy' as 'patent gift', wake up editors.
As it happens I've already written a review of cloudscape; the google cache of it is here.
Brief summary: get the Apache version; reasonably full SQL92 syntax; performance OK; a bit lacking on security.
I'm old enough to remember when discussions on Slashdot were well informed.
Lets see how many open source projects we can get going at one time to compete against one another with absolutely no standardization! YESSSS!
But seriously -- this is getting out of hand. If every single company, individual, etc. starts an open source project what does that accomplish? Nothing. It brings about 100 different alternatives to the market most of which would never be viable in a commercial environment.
News flash: devote time and effort to succesful projects that extend the reach of the open source community. Another open source database project is just well... another project.
Best thing about cloudscape is small embedded databases for java programs rather than making calls to a huge mysql database. You may say that java is slow but anyone using cloudscape for more than 20,000 entries may not be thinking that through. Cloudscape will also be useful for java programmers to program a database using java.
Embedding a database in an application can be very useful, such as in a desktop GUI where you cannot rely on network communication or maybe don't want to bother with a client/server environment.
I'd certainly consider Java/Cloudscape for a desktop db-backed application over anything built in Access.
As always, fit the tool to the job, not the job to the tool.
You bastards! Thanks for cutting my chances of winning an iPod down 100x.
How about using SQLite. It's a C library (native C++, does that mean C is ok?) which provides a self-contained database engine. No need to run a DBMS.
You might wanna check out SQLite, which is in the public domain. It matches all of your requirements, and then some, I think.
GPL made simple: What was my stuff is now our stuff. If you improve our stuff, please keep it our stuff.
Java VM's can out-perform cpp over n cycles, where n is sufficient to overcome Java start times (seconds)
:/
Yes, and a well-supplied tortoise can out-distance a rocket over n years, where n is much longer than the rocket's burn time
I think you might be misunderstanding what JNI is. Each Java runtime provides its own implementation to the native underlying system libraries. Java does not communicate through JNI for I/O of any kind.
/ concepts/index.html
JNI itself is a generic abstraction layer to the underlying operating system. It provides a mechanism whereby dynamic libraries not directly supported by the runtime engine can still be accessed by a Java application.
Threading, sockets and GUI are implemented via the native system libraries. AWT used to be very slow (as opposed to just being merely slow today) due to its own multi-layed abstraction. But at no time was JNI the conduit for these systems.
Further reading: http://java.sun.com/docs/books/tutorial/native1.1
Ryosen
One man's "Troll, +1" is another man's "Insightful, +1".
Beeing in the incubator does not yet mean it is a full blown ASF project - but that the ASF is in the process of ensuring that there is a healthy community around it, that all the legal paperwork, trademakrs, grants, copyrights and other interlectual rights are sorted out, that commiter license agreements are on file for each developer, etc, etc..
Once that is all in place (and getting a healthy long term community is hardest - the rest is just endless grunt work and digging through code and legal paperwork dotting i's and crossing t's) it'll leave the incubator and be a full blown process.
Feel invited to join and make this happen ;-)
Dw.