Joseph Sangiorgio Computer Science Binghamton University President: Theta Tau Professional Engineering Fraternity

  What is Apache Derby? ◦ Relevant UMLs  What is SQLite? ◦ Relevant UMLs  Why?  Comparison Chart  Implementation Differences  Modern Day Uses  Conclusions/Thanks  Funny Pictures 

 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.SQL  Derby provides an embedded JDBC driver that lets you embed Derby in any Java-based solution.embed  Derby also supports the more familiar client/server mode with the Derby Network Client JDBC driver and Derby Network Server.Derby Network Client JDBC driver and Derby Network Server  Derby is easy to install, deploy, and use. ◦ Source:

Implementation in IBM’s “Cloudscape”: Derby embedded in an application Derby acts as a client/server DBMS within a server framework veloperworks/data/librar y/techarticle/dm- 0408anderson/

Implementation in IBM’s “Cloudscape”: Derby embedded in a Web serverFlexible application architecture veloperworks/data/librar y/techarticle/dm- 0408anderson/

 SQLite is a software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. SQLite is the most widely deployed SQL database engine in the world. The source code for SQLite is in the public domain.self-contained serverlesszero-configurationtransactionalmost widely deployedpublic domain  Zero-configuration - no setup or administration needed. Zero-configuration  A complete database is stored in a single cross-platform disk file.single cross-platform disk file  Supports terabyte-sized databases and gigabyte-sized strings and blobs. (See limits.html.)limits.html  Small code footprint: less than 325KiB fully configured or less than 190KiB with optional features omitted.less than 325KiB  Faster than popular client/server database engines for most common operations. Faster  Simple, easy to use API.API  Self-contained: no external dependencies.Self-contained  Cross-platform: Unix (Linux and Mac OS X), OS/2, and Windows (Win32 and WinCE) are supported out of the box. Easy to port to other systems. tml

Implementation everywhere: om/blog/?cat=12 m/Present/2007/intro2d abo/intro2dabo.html

SQLDerby UsageWidely UsedBudding technology; Limited implementation LanguagesCan be used with different programming languages Java-only Support BaseGoogle-tastic!Examples exist, not as easy to find what you need… PerformanceFast. (HyperSQL)HyperSQLDoesn’t support Multiversion concurrency control Multiversion concurrency control NameBoring AcronymSounds fun!

 There are not that many differences in the code…  They both use the same basic coding pattern, and the same “industry standard” JDBC API  When a client application needs to store or retrieve data in the database, it submits a request through the JDBC API to the Derby engine Connection conn = DriverManager.getConnection("jdbc:derby:greetdb"); Statement stmt = conn.createStatement(); ResultSet rs = stmt.executeQuery("SELECT message FROM greetings"); while (rs.next()) { String greeting = rs.getString(1); System.out.println(greeting); } rs.close(); stmt.close(); conn.close();

 There is an extreme need for database engines nowadays… ◦ Embedded applications ◦ Android ◦ Java Standalones ◦ Middleware SQLiteApache Derby FirefoxCloudscape Skype Adobe Products Opera Solaris All Mobile OS Platforms

 Professor Steflik  Google  CS328  Binghamton University, of course! =D

 I would like to thank everyone in attendance today.  Have a fantastic winter break! 