|Original author(s)||Cloudscape Inc (Later IBM)|
|Developer(s)||Apache Software Foundation|
10.12.1.1/ October 11, 2015
|Type||Relational Database Management System|
|License||Apache License 2.0|
Apache Derby (previously distributed as IBM Cloudscape) is a relational database management system (RDBMS) developed by the Apache Software Foundation that can be embedded in Java programs and used for online transaction processing. It has a 2.6 MB disk-space footprint.
Derby embedded database engine
Derby Network Server
The Derby network server increases the reach of the Derby database engine by providing traditional client server functionality. The network server allows clients to connect over TCP/IP using the standard DRDA protocol. The network server allows the Derby engine to support networked JDBC, ODBC/CLI, Perl and PHP.
Embedded Network Server
An embedded database can be configured to act as a hybrid server/embedded RDBMS; to also accept TCP/IP connections from other clients in addition to clients in the same JVM.
- ij: a tool that allows SQL scripts to be executed against any JDBC database.
- dblook: Schema extraction tool for a Derby database.
- sysinfo: Utility to display version numbers and class path.
Apache Derby originated at Cloudscape Inc, an Oakland, California, start-up founded in 1996 by Nat Wyatt and Howard Torf to develop Java database technology. The first release of the database engine, then called JBMS, was in 1997. Subsequently the product was renamed Cloudscape and releases were made about every six months.
In 1999 Informix Software, Inc., acquired Cloudscape, Inc. In 2001 IBM acquired the database assets of Informix Software, including Cloudscape. The database engine was re-branded to IBM Cloudscape and releases continued, mainly focusing on embedded use with IBM's Java products and middleware.
In August 2004 IBM contributed the code to the Apache Software Foundation as Derby, an incubator project sponsored by the Apache DB project. In July 2005 the Derby project graduated from the Apache incubator and is now being developed as a sub-project of the DB Top Level Project at Apache. Prior to Derby's graduation from incubation, Sun joined the Derby project with an intent to use Derby as a component in their own products, and with the release of Java 6 in December 2006, Sun started packaging Derby in the JDK branded as Java DB.
In March 2007 IBM announced that they would withdraw marketing and support for the Cloudscape product, but would continue to contribute to the Apache Derby project.
Currently (December 2013) Derby comes with Java 7 and has been branded as "JavaDB" but is exactly the same bit-for-bit as Derby is. For developers wanting to use Java 6, they can still download Derby as before, but for developers requiring JRE 7 or later, Derby is included in the Java API.
- "Apache Derby". Apache.org.
- Java DB - FAQs: "Is Java DB a fork of Apache Derby?"
- see Embedded Server Example in http://db.apache.org/derby/docs/10.4/adminguide/
- "Why IBM is open sourcing Cloudscape as Derby". IBM.
- "Apache Derby graduates with Sun onboard". CNET news.com.
- "Changes in Cloudscape Availability and Support". IBM.
- Zikopoulos, Paul C.; Baklarz, George; Scott, Dan (November 6, 2005). "Apache Derby—Off to the Races: Includes Details of IBM Cloudscape" (First ed.). IBM Press: 600. ISBN 0-13-185525-5. Archived from the original on February 15, 2009.
- Official website
- IBM Cloudscape Site
- Internals of Derby, An Open Source Pure Java Relational Database Engine deployable in an embedded OSGi environment
- Oracle Java DB Site
- Why IBM is open sourcing Cloudscape as Derby, IBM developerWorks site
- Apache Derby SMP scalability
- Apache Derby performance results in the JPA Benchmark
- Compliance matrix with SQL 2003
- Configure and Install Derby Database
- Derby Database connection using netbeans with screenshots