- Empowers users with enterprise-class features: An offshoot of Daffodil DB, One$DB is architecturally strong and retains all the Daffodil DB's enterprise-class features, which are missing from Derby's current feature-lineup. One$DB support features, such as full-text search, encryption support, backup & restore, and row sets & XA-resources.
-
Makes applications run faster by transferring business logic to the database
layer: This is achieved by the use of Persistent Stored Modules (PSM), which combines
database language and procedural programming language. PSM extends SQL by adding constructs found
in procedural languages, resulting in a structural language that is more powerful than SQL.
Support for PSM in Procedures, Functions, and Triggers coupled with support for Cursors is an important requirement for business logic handling. While One$DB has all these features, Derby does not support PSM. -
Makes applications more secure: Ensuring the security of data within a database is
of paramount importance. One$DB employs security features such as Grant, Revoke and Role; none of
which are supported by Derby.
From a user perspective, the implications are rather simple: Using One$DB will ensure (to a greater extent than Derby ) the stability and security of data. -
Reduces waiting time for concurrent users via MVCCOne$DB reduces the waiting time
for concurrent users and maintains data consistency by using MVCC (Multi Version Concurrency
Control); which allows many 'Reads' to happen in parallel with 'Write' operations while ensuring
that the data is clean and transactionally consistent. You can read more on MVCC
here.
MVCC is also an optimized way to support advanced transaction isolation levels such as 'Repeatable Read' and 'Transaction Serializable'. Derby does not make use of MVCC. -
Makes use of single file data storage: Using a single file for data storage is
common practice in RDBMS's. The ability to store data in a single file is especially important when
considering embedded databases.
While One$DB supports single data file storage, Derby makes use of multiple files for storage. This means that Derby users have to cope with the spread of data across unnecessary multiple files. -
Provides for database migration to and from One$DB: The One$DB migration tool
gives developers the option to migrate existing applications running on other databases to One$DB.
The tool also facilitates migration from One$DB to any other database supporting JDBC.
From a users perspective, this means that One$DB is a zero-liability database. We not only provide you with an entry into the One$DB environment, but also an exit as and when you want. -
Enables efficient data retrieval: In One$DB, the use of queries involving
'intersect' and 'except' operators, 'natural join', 'cross join', and 'full outer join' makes for
highly efficient data retrieval. It also supports functions in 'group by' clause, which adds
flexibility to the entire process of data retrieval and reporting.
Conversely, in the case of Derby, additional code would need to be written to make available the above. This will be a very tedious and time-consuming process. -
Access to architecture / design document and test cases: Users and developers can
access the One$DB architecture / design document here . This 200-page document has been made
available in a bid to be as transparent as possible. In addition, users / developers are also
provided access to sample test cases, so that appropriate testing on One$DB can be done.
In contrast to the above, the Derby community does not have access to architecture / design documents and test cases. -
Provides the comfort of company backing: One$DB is a project totally backed by a
professional company (Daffodil Software Ltd.). On the other hand, Derby is a project donated to the
Apache Software Foundation with no company backing as such.
This means that the future of Derby is uncertain as it is totally in the hands of the community, while the future of One$DB is the hands of the community as well as Daffodil Software Ltd. -
Provides the user with a clear licensing and support policy: A clear (LGPL)
licensing policy that enables free commercial deployment has been put in place for One$DB whereas
certain licensing issues are still ambiguous in case of Derby.
Moreover, building on the point of company backing, One$DB comes with a clear and simple support policy. Support for all products by Daffodil Software come under the One$Support program. In contrast to this, Derby does not have a support program for users and developers.
We hope that this section has been useful in giving a flavor of what One$DB is all about, and how it compares (favorably) with Derby. Please feel free to drop us a line at: support@daffodildb.com, in case of any questions or comments regarding the same.
DISCLAIMER: The above document has been made on the basis of information available on various websites including Derby's official web page on ASF. The views expressed in this section and the information made available are purely those of Daffodil Software Ltd. All trademarks and trade names are the property of their respective owners.
