Derby has graduated from incubation. This means that whatever codebase that it has been thoroughly tested and fully-transformed as an open source rdbms.
Derby is a pure Java embedded RDBMS engine. Derby's heritage spans from proprietary days as Cloudscape. , standards-based relational database engine.
Derby, as an embedded db engines aims to be an straight-forward JDBC-based solution for data management. Like its other open source competitors like HSQLDB, near zero-maintenance is their goal of the end-users.
Event if the real purpose of Derby is an embedded db engine, it also comes with a client-server flavor. One thing that greatly attracted my attention is Derby's support for XA transactions. XA compliance is a great leap from the days of client-server days to the N-tier distributed applications that are popular these days. Also, a great feature would be the Java language-based procedure and functions. A great deviation from commercial DBs which have their own procedural language extensions to SQL. By having Java-based procedures and functions, learning curve won't be so steep for developers.
I am a user of HSQLDB. Now that Derby has been released, I might as well try this out and see the pros and cons and its comparison with an equilly popular HSQLDB.
Subscribe to:
Post Comments (Atom)
2 comments:
Aside from anything else in a Derby vs HSQLDB comparison it must be remembered that HSQLDB has *no* transactional isolation. In marketing terms, it supports "read uncommitted isolation" -- and that is all. Derby, on the other hand, supports the standard four, and you can choose what you want based on needs and performance characteristics you require =)
thanks brian. having said that, I am really compelled to give it a try and boot out hypersonic as I go along.
Post a Comment