Apache Derby is an embedded relational database management system, originally developed by IBM and called IBM Cloudscape.
N/A
Oracle TimesTen
Score 7.8 out of 10
N/A
Oracle TimesTen In-Memory Database (TimesTen) delivers real time application performance by changing the assumptions around where data resides at runtime. By managing data in memory, and optimizing data structures and access algorithms, database operations execute achieve gains in responsiveness and throughput. With TimesTen Scaleout, a shared nothing scale-out architecture based on the existing in-memory technology, TimesTen allows databases to scale across hosts, reach hundreds of terabytes in…
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.
TimesTen is well suited for applications using smaller data or smaller data stores and where transaction response times are not as business critical. TimesTen is good for applications already accessing Oracle and need to cache data for quick read/write operations. TimesTen is not appropriate for large data dependent applications or applications requiring fast response times. In these cases, using Oracle database or Exadata is better
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
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.
Sybase does not have an in-memory database until version 15 so TimesTen was ideal for caching data. TimesTen has reliable replication and backing up mechanisms. Oracle takes longer to set up and use for most applications where as TimesTen is a smaller DBMS that is quick and easy to set up and use. TimesTen can connect to Oracle for caching data so using Oracle as a backend makes sense
TimesTen has had a positive impact from a developer's perspective because implementing TimesTen is quick and easy. The benefits of TimesTen can be seen almost instantly. For instance, the application start up time is faster, the data is easy to maintain and the performance is fast for TimesTen clients.
TimesTen has had a positive impact for the business because it can be made accessible to users via a GUI. This gives users transparency to the data at any time.
The negative impact is that once the TimesTen database has grown too large, the application should move to using Oracle database or else it suffers from performance degradation and stability issues.
