Apache Derby vs. SQLite

Derby is absolutely the best when it comes to needing a small, embeddable RDBMS in your applications. Certain jobs, like Risk Modeling, are perfect for a database that is small enough to fit into memory with no trouble then store data from various sources, and then allow a user to access those data sets quickly.

Incentivized

The portability and ease of use has us doing local development, and then shipping the database to production for implementation. This compact deliverable object is great. Until multiple developers need to access it at a time. It is a caveat, but we create a database per integration as it is easier to manage. Using a SQLite database to manage more than one integration or task is not something we would recommend.

Incentivized

• Embedded SQL-capable database client and server
• Good performance for a file-based database
• Zero cost open source solution

Incentivized

• Our products are using SQLite in embedded Linux and in Windows software.
• It is truly a stable cross-platform database.
• The fact that it is a zero-configuration database engine, it is particularly a nice advantage when you work in the embedded world.
• Being a single database file, it provides ease for those who need to quickly transfer data to someone else, or quickly browse data.

Incentivized

• Not as well positioned in the market as the "big dogs" (Oracle, MSSQL)
• Been around awhile, and not a lot of exposure. This I believe is primarily due to it's relation to the Apache Project (which is not bad, but they don't force big, lumbering corporate volume licensing on you), and thus people are a bit gun-shy about NOT throwing money at something
• Java is still "slow" compared to C/C++, thus making Derby a bit slow too

Incentivized

• Although it is excellent at what it does, you should be really careful and plan accordingly if you know that your database is going to scale at a huge level because it is not suitable of databases which are of Enterprise level and demands top-notch security and protection.
• If your project involves multiple people working on the same database simultaneously, then that becomes a big problem, because it only allows single write at one time. You really need to be forward thinking in a manner to predict if this database will cater to all the needs of your project.
• The most common difficulty with this is the lack of some of the basic functionality which is present in the other premier databases like Joints, Stored Procedure calls, Security and permission grants. If you do require all those things then you are better off not using this software.
• Lastly, if you are using this in an Andriod App development cycle then also your options are limited because it does not integrate with PostgreSQL and MYSQL.

Incentivized

I have had a wonderful experience with SQLite because in my every project I use SQLite in the development phase because it's really fast, doesn't crash and very easy to maintain as well. It saves a lot on physical memory and dedicated server usage. It has all the basic functionality you would need to get the job done and that too at no cost at all. What more could you ask for !!!

Incentivized

I haven't needed support yet.

Incentivized

SQLite is another open-source zero-cost file-based SQL-capable database solution and is a good alternative to Apache Derby, especially for non-Java-based solutions. We chose Apache Derby as it is Java-based, and so is the solution we embedded it in. However, SQLite has a similar feature set and is widely used in the industry to serve the same purposes for native solutions such as C or C++-based products.

Incentivized

SQLite has CRUD queries and manipulates external files. Cross-platform support includes iOS, Android, Mac OS X, and Windows. Compared to other databases, it is fast and straightforward to implement. Even if an application crashes, there is no effect on the database or the data it contains. The user interface is best for input and output. It's best for developing skills and project deliverables.

Incentivized

• Saved money on database licensing.

Incentivized

• No licensing fees has a net increase on ROI
• The active community has kept support costs low, further increasing ROI
• The wide range of supported platforms and high level of compatibility has increased ROI by reducing time spent porting the database model to any platform specific solutions.

Incentivized