Apache Derby Overview
Buyer's Guide
Download the Relational Databases Tools Buyer's Guide including reviews and more. Updated: July 2022
What is Apache Derby?
Apache Derby, an Apache DB subproject, is an open source relational database implemented entirely in Java and available under the Apache License, Version 2.0. Some key advantages include:
- Derby has a small footprint -- about 2.6 megabytes for the base engine and embedded JDBC driver.
- Derby is based on the Java, JDBC, and SQL standards.
- Derby provides an embedded JDBC driver that lets you embed Derby in any Java-based solution.
- Derby also supports the more familiar client/server mode with the Derby Network Client JDBC driver and Derby Network Server.
- Derby is easy to install, deploy, and use.
Apache Derby Customers
Logitech, Splice Machine, CrowdStrike, Lever, Human SolutionsApache Derby Video
Sorry, no reviews are posted about Apache Derby. Be the first to write a review.
It's quick and easy!
If you work for Apache and want to claim this page, contact us.
If you work for Apache and want to claim this page, contact us.
Buyer's Guide
Download our free Relational Databases Tools Report and find out what your peers are saying about Apache, Oracle, Microsoft, and more!
Updated: July 2022
Product Categories
Relational Databases ToolsPopular Comparisons
Oracle Java DB
SQL Server
Oracle Database
Oracle Database In-Memory
Buyer's Guide
Download our free Relational Databases Tools Report and find out what your peers are saying about Apache, Oracle, Microsoft, and more!
Quick Links
- When evaluating Relational Databases, what aspect do you think is the most important to look for?
- Do general purpose or OLTP Oracle databases really perform better on SPARC based servers?
- What is the biggest difference between IBM DB2 and Oracle Database?
- Microsoft sql2017 VS SAP Hana
- What is the best database choice for a long term plan?
- SQL Server 2005 vs. InfoBright - what are the pros and cons of these solutions?
- How does NuoDB compare to MySQL and SQL Server?
- Did you switch from a different solution to MySQL? Can you list a few pros and cons for making the move?
