Apache Derby

From Bauman National Library
This page was last modified on 24 June 2016, at 10:42.
Apache Derby
Developer(s) Cloudscape Inc, IBM, Apache Software Foundation
Repository {{#property:P1324}}
Written in Java
Operating system Java Virtual Machine
Type Relational Database Management System
Website apache.org

Apache Derby - relational DBMS, formerly known as IBM Cloudscape, written in Java, designed to be embedded in Java-based applications and transaction processing in real time.


  • Embedded database engine Derby which supports SQL syntax similarly to IBM DB2.
  • A network server that adds client-server capabilities, which allows clients to connect via TCP / IP, using a standard protocol DRDA. It provides Derby network support of JDBC, ODBC / CLI, Perl and PHP.

Utilities working with database

  • Ij - a tool that allows you to execute SQL-scripts for any JDBC database.
  • Dblook - database schema extraction tool Derby.
  • SysInfo - utility to display the version number and the path to the java-class Derby.


  • Development of Apache Derby began in 1996 by Nat Wyatt and Howard Torf, who were working in the Cloudscape Inc. The first release, called JBMS, was released in 1997, subsequently, the product was renamed in Cloudscape DB, its releases have been published about every six months.
  • In 1999, Cloudscape, Inc was acquired by Informix Software, Inc., and in 2001 all the developments in the field of databases belonging to the Informix Software, including Cloudscape, withdrew to IBM. In turn, the database has been renamed to IBM Cloudscape and continued to produce, being focused primarily on the use of a built-in Java-IBM products and middleware.
  • In August 2004 the source code was submitted to the Apache Software Foundation under the name Derby
  • In July 2005 the Derby project came from the Apache incubator and has been developed as a top level sub-project of the DB Apache.
  • Before going to the Derby from the incubator Sun also joined the project in order to use Derby as a component of their products and, starting with the release of Java 6, in December 2006, Sun began shipping Derby as part of JDK for Java DB name.
  • In March 2007, IBM announced that it refuses to support marketing and Cloudscape product, but will continue to contribute to the Apache Derby project.

Comparison with other embedded SQL databases on the Java

In terms of execution speed, Derby has not shown good results in comparison with other embedded SQL databases, such as H2 database.

Derby does not support MVCC concurrency control, unlike its main competitors HyperSQL and H2.


1. unienc.ru